Skip to content

feat: Adding initial integration assets for Datadog DogStatsD manifest, metadata, README, dashboard, and supporting asset files.#23634

Draft
carlosroman wants to merge 1 commit intomasterfrom
carlosroman/AGTMETRICS-340-dogstatsd-metrics
Draft

feat: Adding initial integration assets for Datadog DogStatsD manifest, metadata, README, dashboard, and supporting asset files.#23634
carlosroman wants to merge 1 commit intomasterfrom
carlosroman/AGTMETRICS-340-dogstatsd-metrics

Conversation

@carlosroman
Copy link
Copy Markdown
Contributor

Metrics are sourced from the client-side telemetry emitted by the official DogStatsD client libraries (Go, Python, Ruby, Java, PHP, .NET).

What does this PR do?

Motivation

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
  • If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

…t, metadata, README, dashboard, and supporting asset files.

Metrics are sourced from the client-side telemetry emitted by the
official DogStatsD client libraries (Go, Python, Ruby, Java, PHP, .NET).
@carlosroman carlosroman force-pushed the carlosroman/AGTMETRICS-340-dogstatsd-metrics branch from 2121796 to 54b3ae7 Compare May 8, 2026 09:00
@dd-octo-sts
Copy link
Copy Markdown
Contributor

dd-octo-sts Bot commented May 8, 2026

Validation Report

Validation Description Status
metadata Validate metadata.csv metric definitions
readmes Validate README files have required sections

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

Passed validations (18)
Validation Description Status
agent-reqs Verify check versions match the Agent requirements file
ci Validate CI configuration and Codecov 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
models Validate configuration data models match spec.yaml
openmetrics Validate OpenMetrics integrations disable the metric limit
package Validate Python package metadata and naming
saved-views Validate saved view JSON file structure and fields
version Validate version consistency between package and changelog

View full run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant