Links

Datadog

If Datadog is your primary source of monitoring data for your AWS account or Kubernetes cluster, read on to learn how to connect your account to Sedai.
S‌edai ingests monitoring data to understand cloud infrastructure, learn resource behavior, and inform its decision engine.
You can sync your Datadog account when you connect an AWS account or Kubernetes cluster to Sedai for the first time, or add it to an existing account/cluster within Sedai at any time from the Settings > Integrations page.
If you connect multiple AWS accounts or Kubernetes clusters to Sedai, you will need to add Datadog to each from their respective integration page.
You will need the following information to connect Datadog to Sedai:
Once you have provided the information, select Test connection.
‌If you’re not sure where to find your API and application key, please reference Datadog’s docs:

Advanced Setup

Tags

Sedai leverages tags to accurately infer metrics and map them to your infrastructure. This allows it to correlate metrics to corresponding resources it discovers within the connected account/cluster.
By default, Sedai pre-populates standard tag values based on industry best practices for naming conventions. However, if you configured custom tags, you will need to provide the exact tag value used for the following topology elements.
Connect AWS Account
Connect Kubernetes Cluster
Topology
Default Tag Key
Cluster
clustername
Load Balancer
load_balancer_name, targetgroup
Container
container_name
Instance
host, task_arn
Topology
Default Tag Value
Cluster
​
Namespace
kube_namespace, namespace
Load Balancer
load_balancer_name
Application
application_id
Container
container_name
Pod
pod_name
If you're not sure how tag values have been configured within your account, you can view your unique metrics with the following APIs:
APM Metrics
https://api.datadoghq.com/api/v2/metrics/trace.http.request.duration/all-tags
CPU Metrics (ECS only)
https://api.datadoghq.com/api/v2/metrics/ecs.fargate.cpu.usage/all-tags
To learn more about configuring custom tags, we recommend checking out Datadog's docs:

Instance ID Pattern

If your instance IDs do not follow standard Kubernetes patterns, you will need to define the unique identifier or prefix used. Supported patterns include:
${instanceID}
${instanceName}
${appID}
${appName}
${regionID}
$}loadBalancerId}
${kubeNamespace}
${kubeClusterName}
Last modified 2mo ago