Skip to content

Document AWS metric name filtering#38023

Open
Sergio-Na wants to merge 1 commit into
masterfrom
sergio.najm/07-07-added_docs_for_aws_integration_metric_name_filtering
Open

Document AWS metric name filtering#38023
Sergio-Na wants to merge 1 commit into
masterfrom
sergio.najm/07-07-added_docs_for_aws_integration_metric_name_filtering

Conversation

@Sergio-Na

@Sergio-Na Sergio-Na commented Jul 8, 2026

Copy link
Copy Markdown

What does this PR do? What is the motivation?

Adds docs for AWS metric name filters in the setup page and FAQ.

@github-actions github-actions Bot added the Guide Content impacting a guide label Jul 8, 2026

Copy link
Copy Markdown
Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@Sergio-Na Sergio-Na changed the title added docs for aws integration metric name filtering Document AWS metric name filters Jul 8, 2026
@Sergio-Na Sergio-Na changed the title Document AWS metric name filters Document AWS metric name filtering Jul 8, 2026
@Sergio-Na Sergio-Na marked this pull request as ready for review July 8, 2026 00:11
@Sergio-Na Sergio-Na requested a review from a team as a code owner July 8, 2026 00:11

@RaphaelAllier RaphaelAllier left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Curious what the docs team has to say on wording too


#### Required metrics

Metric name filters cannot remove `aws.ec2.cpuutilization` or `aws.lambda.invocations`. Datadog always collects these metrics because they are used for billing.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I would rephrase that but I don't know how. I'm not sure we should expose how billing is computed in our public docs

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

I agree but Matt thought it would be a good idea. I was thinking something more along the lines of

Metric name filters cannot remove aws.ec2.cpuutilization or aws.lambda.invocations. Datadog always collects these foundational/critical metrics.

Something along these lines. I'll wait for the docs folks to chime in.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I recommend removing the subheader and making this an alert. I added my suggestion below. If customers need to know about billing, we can add it back in.

@estherk15 estherk15 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Left a few suggestion, let me know if you have any questions!


### Filter metrics by metric name

Use the {{< ui >}}Metric Collection{{< /ui >}} tab on the [AWS integration page][8] to filter the CloudWatch metrics that Datadog collects from each namespace. Expand a namespace in the CloudWatch metric collection table and choose an **Include** or **Exclude** filter:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
Use the {{< ui >}}Metric Collection{{< /ui >}} tab on the [AWS integration page][8] to filter the CloudWatch metrics that Datadog collects from each namespace. Expand a namespace in the CloudWatch metric collection table and choose an **Include** or **Exclude** filter:
Use the {{< ui >}}Metric Collection{{< /ui >}} tab on the [AWS integration page][8] to filter CloudWatch metrics by namespace. Expand a namespace in the CloudWatch metric collection table and choose an **Include** or **Exclude** filter:


#### Required metrics

Metric name filters cannot remove `aws.ec2.cpuutilization` or `aws.lambda.invocations`. Datadog always collects these metrics because they are used for billing.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I recommend removing the subheader and making this an alert. I added my suggestion below. If customers need to know about billing, we can add it back in.

[10]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage_lens.html
[11]: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/monitor_estimated_charges_with_cloudwatch.html#turning_on_billing_metrics
[12]: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-cloudwatch-new.html
[13]: /integrations/guide/monitor-your-aws-billing-details/

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
[13]: /integrations/guide/monitor-your-aws-billing-details/
[14]: /getting_started/integrations/aws/#filter-metrics-by-metric-name


Metric name filters support lowercase letters, numbers, `.`, `_`, and `*`. The AWS integration previews matching metrics before you save. Metric name filters apply per namespace; namespace filters still control whether the namespace itself is collected.

Metric name filters cannot remove `aws.ec2.cpuutilization` or `aws.lambda.invocations`. Datadog always collects these metrics because they are used for billing.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Recommend keeping this section brief and link out to the docs as the source of truth. It's less maintenance and lowers the risk of have diverging information.

Suggested change
Metric name filters cannot remove `aws.ec2.cpuutilization` or `aws.lambda.invocations`. Datadog always collects these metrics because they are used for billing.
Yes. On the [AWS integration page][1], open the **Metric Collection** tab, expand a CloudWatch namespace, and add metric name filters. Use **Include** to collect only matching Datadog metric names for that namespace, or **Exclude** to collect everything except matching metric names.
For more information on syntax and required metrics, see [Getting Started with AWS][14].

@Sergio-Na Sergio-Na force-pushed the sergio.najm/07-07-added_docs_for_aws_integration_metric_name_filtering branch from 3ea6e2e to 35ab495 Compare July 8, 2026 20:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Guide Content impacting a guide

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants