Add Dynamo integration

[piochelepiotr]

Summary

• Adds a new Datadog Agent check for NVIDIA Dynamo, an open-source distributed LLM inference-serving framework
• Scrapes OpenMetrics endpoints from both the HTTP frontend (:8000/metrics) and backend workers (vLLM/SGLang/TensorRT-LLM system status server), covering request throughput, latency, and KV cache efficiency metrics
• Includes full manifest, metadata, service checks, dataflows, README, and test suite (fixtures, unit tests, e2e docker-compose environment with Caddy-served metrics)

Test plan

• ddev test dynamo -- -k unit — 3/3 unit tests pass
• ddev validate all dynamo — 21/21 validations pass
• Manually verified end-to-end via ddev env start dynamo py3.13 --dev — live agent container correctly discovers and submits ~99-130 metrics per check run across frontend and worker instances, with dynamo.openmetrics.health service check reporting OK
• CI e2e job (Dynamo in test-all.yml) — to be confirmed once this PR's pipeline runs

🤖 Generated with Claude Code

[dd-octo-sts]

Validation Report

Validation	Description	Status
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	❌

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

Passed validations (20)

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 and naming	✅
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

[datadog-datadog-us1-prod]

   

⚠️ Warnings

🚦 5 Pipeline jobs failed

Check PR | run / Check PR changelog     

🔧 Fix in code. This looks caused by changes in this PR.

Your changelog entry has the wrong PR number.

PR | test / check     

See error

Job did not run: blocked by a failed job in an earlier pipeline stage.

PR | test / test (linux, ubuntu-22.04, dynamo, Dynamo (py3.13), py3.13) / Dynamo (py3.13)-py3.13     

See error

Command '[docker exec dd_dynamo_py3.13 agent check dynamo --json --check-rate]' returned non-zero exit status 255. Error: no valid check found after multiple retries.

View all 5 failed jobs.

📋 Copy prompt for your agent

CI on my pull request is failing. Help me find and fix the root cause of each failing job below — they were flagged as caused by changes in this PR, so focus on the diff. For each job, explain the failure and propose a fix.

Branch: add-dynamo-integration

Check PR | run / Check PR changelog
Commit: bcac7a4b5692905924053c5e0f12c26a05f2ea7e
Error (code / build):
Your changelog entry has the wrong PR number.
CI job: https://github.com/DataDog/integrations-core/actions/runs/31841298619/job/94898552295

🧪 1 Test failed in 1 job

PR | run  

test_check_dynamo_e2e from test_e2e.py  

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-check-apikey.sh: executing... 
[cont-init.d] 01-check-apikey.sh: exited 0.
[cont-init.d] 50-ci.sh: executing... 
[cont-init.d] 50-ci.sh: exited 0.
[cont-init.d] 50-ecs-managed.sh: executing... 
...

ℹ️ Info

No other issues found (see more)

❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 95.24%
• Overall Coverage: 89.60% (+1.10%)

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 13f48d2 | Docs | Datadog PR Page | Give us feedback!}

[cit-pr-commenter-54b7da]

evalya-impact-summary

evalya impact analysis

Impact analysis: 0 selected, 0 skipped (of 0 test tasks)
Publish tasks:   1 (always emitted)
Diff (33 files):
  .github/workflows/config/labeler.yml
  .github/workflows/test-all.yml
  code-coverage.datadog.yml
  dynamo/CHANGELOG.md
  dynamo/README.md
  dynamo/assets/configuration/spec.yaml
  dynamo/assets/dataflows.yaml
  dynamo/assets/service_checks.json
  dynamo/changelog.d/1.added
  dynamo/datadog_checks/dynamo/__about__.py
  dynamo/datadog_checks/dynamo/__init__.py
  dynamo/datadog_checks/dynamo/check.py
  dynamo/datadog_checks/dynamo/config_models/__init__.py
  dynamo/datadog_checks/dynamo/config_models/defaults.py
  dynamo/datadog_checks/dynamo/config_models/instance.py
  dynamo/datadog_checks/dynamo/config_models/shared.py
  dynamo/datadog_checks/dynamo/config_models/validators.py
  dynamo/datadog_checks/dynamo/data/conf.yaml.example
  dynamo/datadog_checks/dynamo/metrics.py
  dynamo/hatch.toml
  ... and 13 more

Debug a specific task: evalya plan impact --path <path> --task <task>

Learn more about CI impact filtering