Skip to content

Update agent-filtering-for-dogstatsd-custom-metrics.md with remote config + RBAC details #32104

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Update agent-filtering-for-dogstatsd-custom-metrics.md with remote config + RBAC details #32104

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0a92a8f
Update agent-filtering-for-dogstatsd-custom-metrics.md with remote co…
olivielpeau Oct 9, 2025
b7ffd3e
Apply suggestions from code review
olivielpeau Oct 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 22 additions & 3 deletions content/en/metrics/guide/agent-filtering-for-dogstatsd-custom-metrics.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,9 +30,23 @@

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.

Creating and updating filtering policies requires the [`metric_tags_write`][1] RBAC permission. All users can view filtering policies.

## Prerequisites

- Upgrade to Datadog Agent v7.67.0 or higher (v7.70.0 or higher is recommended).
- Ensure that your RBAC permissions include [`org_management`][2] and that [Remote Configuration][3] is enabled for your organization.
- Ensure that your RBAC permissions include [`api_keys_write`][4] and that the [Remote Configuration capability is enabled on the API keys][5] used by your Agents. After enabling Remote Configuration on an API key, an Agent restart is required for Remote Configuration enablement to take effect.
Comment on lines +38 to +39
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Ensure that your RBAC permissions include [`org_management`][2] and that [Remote Configuration][3] is enabled for your organization.
- Ensure that your RBAC permissions include [`api_keys_write`][4] and that the [Remote Configuration capability is enabled on the API keys][5] used by your Agents. After enabling Remote Configuration on an API key, an Agent restart is required for Remote Configuration enablement to take effect.
- Ensure that your RBAC permissions include [`org_management`][2] and [`api_keys_write`][4].
- Enable [Remote Configuration][3] for your organization.
- Enable the Remote Configuration capability on the API keys][5] used by your Agents. After enabling Remote Configuration on an API key, an Agent restart is required for Remote Configuration enablement to take effect.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What I mean to communicate with this structure is that, respectively:

  • the org_management permission is only needed to validate that Remote Configuration is enabled for the org (and if not, to enable it)
  • the api_keys_write permission is only needed to validate that the API keys have Remote Configuration enabled (and if not, enable it on them)

but that these permissions are not needed to use the feature, they're only needed during the initial setup.

I'm under the impression that your proposed changes would make this less clear. But I'm also open to suggestions on how to make this more explicit/clear. WDYT?


{{<img src="agent/remote_config/RC_Key_updated.png" alt="API Key properties with Remote Configuration capability Enable button." width="90%" style="center">}}

## Create a metric filtering policy

You can create a metric filtering policy from the [Metrics Settings page][1] or the [Metrics Summary page][2].
You can create a metric filtering policy from the [Metrics Settings page][6] or the [Metrics Summary page][7].

Metric filtering policies are applied to all Agents v7.67.0+ with Remote Configuration enabled. Older Agent versions, or Agents with Remote Configuration disabled, do not apply filtering policies.

Policy updates are deployed to Agents in 1–2 minutes.

Check failure on line 49 in content/en/metrics/guide/agent-filtering-for-dogstatsd-custom-metrics.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.endash 

Avoid en dashes ('–'). For hyphenated words, use a hyphen ('-'). For parenthesis, use an em dash ('—').

### From the Metrics Settings page

Expand Down Expand Up @@ -184,5 +198,10 @@

{{< partial name="whats-next/whats-next.html" >}}

[1]: https://app.datadoghq.com/metric/settings/policies
[2]: https://app.datadoghq.com/metric/summary
[1]: /account_management/rbac/permissions/#metrics
[2]: /account_management/rbac/permissions/#access-management
[3]: https://app.datadoghq.com/organization-settings/remote-config
[4]: /account_management/rbac/permissions#api-and-application-keys
[5]: https://app.datadoghq.com/organization-settings/api-keys
[6]: https://app.datadoghq.com/metric/summary
[7]: https://app.datadoghq.com/metric/settings/policies
Loading