Dd Apm

作者 datadog-labs5b40c73824ec无许可证177 个星标收录于 2026年10月8日更新于 2026年10月8日仓库今天更新

APM - install, onboard, instrument, enable, set up, configure, traces, services, dependencies, performance analysis, Data Streams Monitoring (DSM), queue lag, pipeline latency. Use for any request involving Datadog APM setup, instrumentation (SSI, ddtrace, agent install), or analysis.

AI 生成的概览

指导 Datadog APM 的安装、插桩、服务重映射与数据流监控,并提供追踪与服务分析。

功能
该技能将 Datadog APM 请求路由到相应的子技能,涵盖 Kubernetes 或 Linux 主机插桩、服务重命名或数据流监控。它还记录了列出服务、查看服务地图、搜索追踪以及查询关键 APM 指标和 SLO 的命令。其中包含故障排查指导和常用查询模式。
适用场景
适用于涉及 Datadog APM 安装、接入或插桩的请求,包括 SSI、ddtrace 和代理设置。也适用于服务重命名、队列或管道延迟监控,以及追踪或服务性能分析。
运行要求
需要安装并认证 Datadog Labs Pup,并具备 Datadog 环境访问权限。该技能仅为说明文档,不附带脚本。

Datadog APM

Distributed tracing, service maps, and performance analysis.

Routing — Read This First

Match the user's request to one of the entries below. Each entry has the same shape: triggers → which sub-skill to load → the anti-pattern to avoid. If a request seems to fit more than one entry, see "Overlap disambiguation". If nothing matches, see "None of the above" at the end.


Kubernetes APM install / instrument / onboard — trigger when the user mentions Kubernetes, K8s, EKS, GKE, AKS, kind, minikube, K3s, helm, DatadogAgent CR, kubectl, SSI on a cluster, pod injection, or init containers.

Immediately read .claude/skills/dd-apm/k8s-ssi/agent-install/SKILL.md now, then .claude/skills/dd-apm/k8s-ssi/enable-ssi/SKILL.md, then .claude/skills/dd-apm/k8s-ssi/verify-ssi/SKILL.md — do not proceed from memory.

Common wrong approaches that LOOK like they work but silently fail:

  • helm install datadog datadog/datadog — the standard chart does NOT support SSI via DatadogAgent CR.
  • Adding ddtrace imports or ddtrace-run to the app — SSI auto-instruments WITHOUT any code changes.
  • admission.datadoghq.com/enabled annotations — that's admission controller config injection, not SSI init container injection.

Linux APM install / instrument / onboard — trigger when the user mentions a single host, VM, EC2 instance, bare-metal, RHEL/Ubuntu/Debian, systemd, or no orchestrator.

Immediately read .claude/skills/dd-apm/linux-ssi/agent-install/SKILL.md now, then .claude/skills/dd-apm/linux-ssi/enable-ssi/SKILL.md, then .claude/skills/dd-apm/linux-ssi/verify-ssi/SKILL.md — do not proceed from memory.

Do NOT install the agent via plain apt-get install datadog-agent (or yum equivalent) and assume SSI follows — host auto-instrumentation requires the install script with the SSI flags, which the sub-skill walks through.


Service rename / service remapping — trigger when the user mentions renaming a service, collapsing multiple service names, stripping suffixes/prefixes, or cleaning up inferred services.

Immediately read .claude/skills/dd-apm/service-remapping/SKILL.md now — do not proceed from memory.

Do NOT change tags.datadoghq.com/service labels or DD_SERVICE env vars to rename a service in Datadog. That requires a rollout and only affects new data. Use a service remapping rule — it rewrites the name at ingestion time with no deployment change.


Data Streams Monitoring (DSM) / queue and pipeline monitoring: trigger when the user mentions data streams, DSM, consumer or queue lag, pipeline latency, end-to-end latency across queues, or monitoring Kafka / RabbitMQ / SQS / SNS / Kinesis / Pub/Sub flows between services.

Immediately read .claude/skills/dd-apm/enable-dsm/SKILL.md now. Do not proceed from memory.

Do NOT install a separate DSM agent, package, or library. DSM runs in the Datadog SDK that APM already injected and is enabled with one setting per service. Do NOT enable it without first telling the user it is included with APM Pro and Enterprise and billed separately on base APM.


Overlap disambiguation

When a request could plausibly fit more than one entry above, use these tiebreakers:

HintRoute to
Cluster orchestrator mentioned (EKS/GKE/AKS/kind/K3s/minikube) — even if "just one node"k8s-ssi
Single host, VM, or EC2 with no orchestratorlinux-ssi
"Several services that should be one"service-remapping — the sub-skill picks the rule type based on whether the duplicates are real instrumented services or inferred entities (DBs, queues, external APIs)
"My service shows under the wrong name"First check DD_SERVICE on the deploy. If correct and the name is still wrong → service-remapping.
"Monitor Kafka" / "monitor my queues"Ask whether they mean broker/cluster health (Kafka Console, an Agent check: https://docs.datadoghq.com/data_streams/kafka/setup/) or message flow between their services (enable-dsm)
"Reduce APM volume / cost / noise"No sub-skill yet. Ask whether the user means sampling (fewer ingested traces) or retention filters (less indexed data) before suggesting commands.

None of the above

If the request doesn't match any entry above, continue reading the trace-search, service analysis, and metrics content below. If even that doesn't fit, ask the user to clarify — do not invent a workflow.


Requirements

Datadog Labs Pup should be installed. See Setup Pup if not.

Command Execution Order (Token-Efficient)

For scoped commands, use this order:

  1. Check context first (prior outputs, conversation, saved values).
  2. If a required value is missing, run a discovery command first.
  3. If still ambiguous, ask the user to confirm.
  4. Then run the target command.
  5. Avoid speculative commands likely to fail.

Quick Start

bash
pup auth login# Confirm env tag with the user first (do not assume production/prod/prd).pup apm services list --env <env> --from 1h --to nowpup traces search --query "service:api-gateway" --from 1h

Services

List Services

bash
pup apm services list --env <env> --from 1h --to nowpup apm services stats --env <env> --from 1h --to now

Service Stats

bash
pup apm services stats --env <env> --from 1h --to now

Service Map

bash
# View dependenciespup apm flow-map --query "service:api-gateway&from=$(($(date +%s)-3600))000&to=$(date +%s)000" --env <env> --limit 10

Traces

Search Traces

bash
# By servicepup traces search --query "service:api-gateway" --from 1h
# Errors onlypup traces search --query "service:api-gateway status:error" --from 1h
# Slow traces (>1s)pup traces search --query "service:api-gateway @duration:>1000ms" --from 1h
# With specific tagpup traces search --query "service:api-gateway @http.url:/api/users" --from 1h

Trace Detail

bash
# No direct get command for a single trace ID.# Use traces search with a narrow query and time window.pup traces search --query "trace_id:<trace_id>" --from 1h

Key Metrics

MetricWhat It Measures
trace.http.request.hitsRequest count
trace.http.request.durationLatency
trace.http.request.errorsError count
trace.http.request.apdexUser satisfaction

Service Level Objectives

Link APM to SLOs:

bash
pup slos create --file slo.json

Common Queries

GoalQuery
Slowest endpointsavg:trace.http.request.duration{*} by {resource_name}
Error ratesum:trace.http.request.errors{*} / sum:trace.http.request.hits{*}
Throughputsum:trace.http.request.hits{*}.as_rate()

Troubleshooting

ProblemFix
No tracesCheck ddtrace installed, DD_TRACE_ENABLED=true
Missing serviceVerify DD_SERVICE env var
Traces not linkedCheck trace headers propagated
High cardinalityDon't tag with user_id/request_id

References/Docs

来源与署名

来源:datadog-labs/agent-skills位于dd-apm提交5b40c73

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架