CloudWatch metrics, scraped by Dash0 and filtered by your AWS tags
A second way to get CloudWatch metrics into Dash0: Dash0 scrapes them for you, alongside Metric Streams, so you can pick the trade-offs that fit. Scraping skips redundant dimension sets and makes your AWS tags filterable across every signal.
You now have a second way to get CloudWatch metrics into Dash0. Next to Metric Streams, which push metrics through Amazon Data Firehose, Dash0 can now scrape CloudWatch metrics from your AWS account on a regular interval. Both paths produce metrics with the same OpenTelemetry names, so you can choose the one whose trade-offs fit each use case.
| Scraping | Metric Streams | |
|---|---|---|
| Infrastructure you run | None. Dash0 uses the integration's read-only IAM role. | A metric stream and a Firehose delivery stream per region |
| Latency | Every 5 minutes, with at least 2 minutes of delay | Near real time |
| Dimension sets | The most specific set per metric | Every set CloudWatch publishes |
| Selection | Namespaces, metrics, resource tags and regions | Namespaces and metric names |
Scraping vs. Metric Streams compares the two paths in detail, including AWS costs, and explains how to switch from one to the other without duplicate data.

With scraping:
- Nothing to deploy: connect your account, and Dash0 assumes a read-only role in it.
- Less redundant data: Dash0 queries only the most specific dimension set for each metric and skips the restated totals. That cuts time series on your AWS bill and in Dash0.
- Scrape by tag: in the Metrics tab, use AWS resource tags to choose what to scrape, per namespace or for the whole integration.
- Filter by tag everywhere: the same tags are attached to your resources, so you can filter metrics, logs and traces by them.
- Familiar names: scraped metrics use the same OpenTelemetry names as Metric Streams.


To get started with scraping, set up the AWS integration and turn on the namespaces you need in the Metrics tab.