[jszwedko]

What does this PR do?

Adds a datadog_agent integration that monitors the Datadog Agent through its OpenMetrics telemetry endpoint (/telemetry), and marks the expvar-based Agent Metrics integration as deprecated in favor of it.

By default it collects the telemetry analogous to what go_expvar.d/agent_stats.yaml.example collected (forwarder, DogStatsD, aggregator, scheduler, Logs Agent), using the names from the Agent's openmetrics.d/agent_stats.yaml.example under the datadog.agent namespace. Counters are submitted with native OpenMetrics V2 types (<name>.count). tag_by_endpoint defaults to false because the forwarder telemetry has its own endpoint label (the intake endpoint), which would be ambiguous next to the scraped URL.

The README includes a "Migrating from Agent Metrics" section that maps each old metric to its replacement and covers the behavior changes (counters as .count, combined metrics distinguished by tags, Go runtime metrics opt-in).

The new integration uses the datadog-agent-openmetrics app_id. app_ids can't be reused, so agent_metrics keeps datadog-agent.

Motivation

DataDog/datadog-agent#55721 deprecated collecting the Agent's internal telemetry via expvars in favor of the OpenMetrics endpoint, which has typed metrics, richer tags, and more metrics. That PR only added an example openmetrics.d config. This gives users a first-class integration to migrate to.

Some of the default metrics (aggregator flush stats, scheduler.queues.size, etc.) were added to the telemetry endpoint by that PR, so they require Agent 7.86+. Shipping a datadog_agent.d/conf.yaml.example with the Agent is a follow-up in datadog-agent.

Tests: a unit test runs the check against a fixture captured from a real Agent's /telemetry (plus samples for families that only appear under load) and asserts every documented metric is collected and nothing else is. The E2E test scrapes the E2E Agent container's own telemetry on a free port, so it doesn't reach an Agent installed on the host.

Checklist before requesting review

• I self-reviewed the full diff, and this description matches the final change
• Tests cover the change, or this description explains why none are needed
• Automated review comments, including Codex review, were addressed or answered
• I, the human author, understand this change, can explain it to reviewers, and believe it meets the repository standards

🤖 Generated with Claude Code

[dd-octo-sts]

✅ Dispatcher tests: passed

Dispatcher beta: informational only
Existing CI remains the merge signal.

  2/2 jobs

✅ 2 passed · nothing failed

Batches · ✅ batch-01 2/2

_{Dispatcher finished on 3d27d19 — GitHub Run · Dispatcher Logs.}

[cit-pr-commenter-54b7da]

evalya-impact-summary

Evalya CI impact

Impact analysis: 0 selected, 0 skipped (of 0 test tasks)
Publish tasks:   4 (always emitted)
Changed files:   29

Full impact report
Learn more about CI impact filtering

[datadog-prod-us1-5]

   

❌ Errors

Your PR has failed checks. Please review the issues below and take necessary action before merging.

🚦 1 Pipeline job failed

Validate repository | Run Validations / Validate

View more details · View in GitHub Actions

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 93.18%
• Overall Coverage: 90.69% (+1.08%)

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 9be1bdc | Docs | View more details | Give us feedback!}

[dd-octo-sts]

Disk usage change

Commit 9be1bdc compared against cd6ae55.

Uncompressed

linux-aarch64	linux-x86_64	macos-aarch64	macos-x86_64	windows-x86_64
🔺 +39.87 KiB	🔺 +39.87 KiB	🔺 +39.87 KiB	🔺 +39.87 KiB	🔺 +39.87 KiB

Details

Name	Version	Type	linux-aarch64	linux-x86_64	macos-aarch64	macos-x86_64	windows-x86_64
datadog_agent (NEW)	0.0.1	Integration	🔺 +39.87 KiB	🔺 +39.87 KiB	🔺 +39.87 KiB	🔺 +39.87 KiB	🔺 +39.87 KiB

Compressed

linux-aarch64	linux-x86_64	macos-aarch64	macos-x86_64	windows-x86_64
🔺 +11.63 KiB	🔺 +11.63 KiB	🔺 +11.63 KiB	🔺 +11.63 KiB	🔺 +11.63 KiB

Details

Name	Version	Type	linux-aarch64	linux-x86_64	macos-aarch64	macos-x86_64	windows-x86_64
datadog_agent (NEW)	0.0.1	Integration	🔺 +11.63 KiB	🔺 +11.63 KiB	🔺 +11.63 KiB	🔺 +11.63 KiB	🔺 +11.63 KiB

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	🔄 Running since 2026-10-26T18:04:23.132440Z	986bb1f	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[jszwedko]

Left some feedback from Docs and approved the PR.

@drichards-87 thanks! I applied all of the suggestions in a6c12a7.

Review from drichards-87 is dismissed. Related teams and files:

• documentation
  • datadog_agent/manifest.json

[steveny91]

Looks good. I have one question, do we expect users to migrate existing to this integration? The change from the counter that the old integration used to collect might behave differently here with a different name with the .count affix. Would that be of concern?

Review from steveny91 is dismissed. Related teams and files:

• agent-integrations
  • datadog_agent/README.md

[jszwedko]

Looks good. I have one question, do we expect users to migrate existing to this integration? The change from the counter that the old integration used to collect might behave differently here with a different name with the .count affix. Would that be of concern?

@steveny91 We are primarily targeting new users that are starting to collect telemetry for the Datadog Agent but hopefully some existing users migrate too (there are no plans to remove the old integration though). Your question prompted me to consider where we should have a small blurb for customers migrating so I pushed that up as f5dcf50.

Review from drichards-87 is dismissed. Related teams and files:

• documentation
  • datadog_agent/README.md

[jszwedko]

Thanks @drichards-87 ! I applied the suggested updates in 9be1bdc

[dd-octo-sts]

Validation Report

Validation	Description	Status
pr-description	Validate the pull request checklist and visible description length To fix: Tick every item in .github/PULL_REQUEST_TEMPLATE.md and keep the description under 3,000 visible characters.	❌

Run ddev validate all changed --fix to attempt to auto-fix supported validations.

Passed validations (21)

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and code coverage settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata, naming, and wheel contents	✅
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run