Document OpenMetrics metric-limit Agent telemetry - #38477
Draft
nubtron wants to merge 1 commit into
Draft
Conversation
Contributor
Preview links (active after the
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Documents the untagged
openmetrics.max_returned_metrics_reachedmetric in the Agent Data Security telemetry collection table.The metric counts OpenMetrics check runs that exceed the configured
max_returned_metricslimit, which is currently a silent metric-drop condition. It is produced by DataDog/integrations-core#24588 and allowlisted into the built-inchecksAgent Telemetry profile by DataDog/datadog-agent#53794.The metric is intentionally untagged, and this change touches only
content/en/data_security/agent.md.Onboarding governance: an ASUP issue will be created separately and linked here.
Do not merge until both code changes are merged and the first Agent release containing the complete path is GA. RC payload inspection and
ddcoatquery validation are still pending.Merge readiness
For Datadog employees:
AI assistance
AI-assisted research and initial draft; the metric name and semantics were verified against the implementation PRs and manually reviewed.
Additional notes
The row is placed in the Checks subsection of the Telemetry collection table, directly below
checks.execution_time. The documented name matches the profile entry added in DataDog/datadog-agent#53794.