-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[DOCS-12213] Add API section #32156
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.
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
base: master
Are you sure you want to change the base?
[DOCS-12213] Add API section #32156
Conversation
Preview links (active after the
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Left a couple of comments
## Manage metric filtering policies through the API | ||
|
||
<div class="alert alert-danger">These endpoints are subject to change while Agent-side filtering for DogStatsD custom metrics is in Preview.</div> | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Worth mentioning that all endpoints require a valid API key and a valid application key (with metric_tags_write
scope), and link to the Getting Started section of our API docs: https://docs.datadoghq.com/api/latest/?tab=java#getting-started
|
||
### Create a filtered metric policy | ||
|
||
**POST** `{{< region-param key="dd_api" code="true" >}}/api/unstable/remote_config/products/metric_control/filtered_metrics/policies` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On the preview page, this URL (and all others) have a bit of a weird formatting visually. Maybe due to the variable here?
Sorry I filed the request for this doc update a bit too soon, and there's some eng work remaining before these API endpoints can be documented. I updated DOCS-12213 accordingly. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Look good! Let me know if you need a re-review.
What does this PR do? What is the motivation?
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