Docs11702/agent metrics filtering #30892
Merged
Conversation
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
github-actions
bot
added
Images
✅ Documentation Team ReviewThe documentation team has approved this pull request. Thank you for your contribution! |
Preview links (active after the
|
olivielpeau
reviewed
Aug 5, 2025
content/en/metrics/guide/agent-filtering-for-dogstatsd-custom-metrics.md
Outdated
Show resolved
Hide resolved
content/en/metrics/guide/agent-filtering-for-dogstatsd-custom-metrics.md
Outdated
Show resolved
Hide resolved
content/en/metrics/guide/agent-filtering-for-dogstatsd-custom-metrics.md
Outdated
Show resolved
Hide resolved
content/en/metrics/guide/agent-filtering-for-dogstatsd-custom-metrics.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Olivier Vielpeau <[email protected]>
hestonhoffman
approved these changes
Aug 6, 2025
content/en/metrics/guide/agent-filtering-for-dogstatsd-custom-metrics.md
Outdated
Show resolved
Hide resolved
content/en/metrics/guide/agent-filtering-for-dogstatsd-custom-metrics.md
Outdated
Show resolved
Hide resolved
olivielpeau
reviewed
Aug 7, 2025
|
|
||
| Agent-side filtering enables you to filter out unused or unwanted DogStatsD custom metrics directly at the Datadog Agent, before sending them to Datadog. This can significantly reduce both indexed and ingested custom metric volume. | ||
|
|
||
| Filtering is performed at the Agent level but centrally managed through the Datadog UI, giving teams full visibility and control. You can create, update, and manage filtering policies in Datadog, streamlining metric governance while maintaining transparency. |
There was a problem hiding this comment.
We'll want to capture the following pre-requisites to use the feature:
- Remote Configuration needs to be enabled for the API key(s) used by the customer's Agents (instructions at https://docs.datadoghq.com/remote_configuration/#enable-remote-configuration)
- Agents need to be at version 7.67.0 or above
A bit more details about how the metric filtering policies are deployed to Agents would be useful as well(probably later in this doc?):
- Target and scope: Policies are applied to all of the Agents v7.67.0+ using an API key with Remote Configuration enabled. Older Agent versions, or Agents with Remote Configuration disabled, do not apply policies.
- Rollout speed: Policy updates are deployed to these Agents in about 1min (up to 5 minutes)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Add a new private guide for custom metrics filtering
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes