15 docs tagged with "agents_integrations"

The Cloudwatch agent will run in your EC2 instances to collect metrics and send them to nOps.

The Cloudwatch agent will run in your EC2 instances to collect metrics and send them to nOps.

The Cloudwatch agent will run in your EC2 instances to collect metrics and send them to nOps.

If you have previously installed the container-insights (nops-k8s-agent) and want to migrate to the unified installation of agents, please refer to this migration guide.

nOps allows you to send alerts directly to Slack.

Overview

EventBridge Integration makes it easier for nOps to automate workflows in the client’s environment.

Introduction

Integrate Jira with nOps in just a few clicks using OAuth 2.0.

If you're migrating from a previous installation of the Container Insights Kubernetes agent (originally installed using a bash script), the new installation method involves updating the CloudFormation Stack. This update creates a Lambda function that manages the creation and update of the IAM Roles for Service Accounts (IRSA) required by the agent to push metrics to the S3 Bucket associated with your AWS account. Additionally, you'll need to run a cleanup script to remove the old Helm release and delete any unused namespaces from the previous installation.

The nOps Kubernetes Agent stack is a helm chart that contains agent components that both gather metrics data in your Kubernetes cluster and enable nOps automated optimization of Karpenter and Container Rightsizing.

---

You can use AWS Secrets Manager integration with External Secrets Operator to create/sync the API Keys secret in your EKS cluster.

You can use AWS Secrets Manager integration with External Secrets Operator to create/sync the API Keys secret in your EKS cluster.

Configuring Webhook Integrations for 3rd party apps