Dash0 acquires Polar Signals

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.

ScrapingMetric Streams
Infrastructure you runNone. Dash0 uses the integration's read-only IAM role.A metric stream and a Firehose delivery stream per region
LatencyEvery 5 minutes, with at least 2 minutes of delayNear real time
Dimension setsThe most specific set per metricEvery set CloudWatch publishes
SelectionNamespaces, metrics, resource tags and regionsNamespaces 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.

AWS integration Metrics tab with Global filters and the EC2 namespace expanded to choose which metrics to collect

With scraping:

Filter picker listing values of the AWS tag dash0.cloud.tags.Name with the number of matching resources
EC2 namespace scoped by the condition dash0.cloud.tags.Name = demo-0-node

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