Dash0 acquires Polar Signals

Last updated:

Use AWS Resource Tags in Dash0

Dash0 adds the AWS tags of your resources to their telemetry, so you can filter metrics, logs, and traces by tag.

Dash0 reads the tags of your AWS resources and adds them to the resources' telemetry. Filter and group by the same tags you already use in AWS, such as team, environment, or cost-center, across metrics, logs, and traces.

How Dash0 Collects Tags

The AWS integration discovers your resources with AWS Resource Explorer in the integration's regions and reads each resource's tags. Discovery runs every minute and covers:

  • Lambda functions: Always.
  • Resources of collected namespaces: The resource types behind every CloudWatch namespace you collect metrics for. See Collect AWS CloudWatch Metrics.

Resources outside this scope get no tags from the integration.

Tag Attributes

Each AWS tag becomes a resource attribute with the prefix dash0.cloud.tags., followed by the tag key exactly as written in AWS:

AWS tagDash0 attribute
team = paymentsdash0.cloud.tags.team = payments
Environment = productiondash0.cloud.tags.Environment = production
aws:cloudformation:stack-name = checkoutdash0.cloud.tags.aws:cloudformation:stack-name = checkout

AWS-managed tags, such as the aws:cloudformation:* tags CloudFormation sets, appear the same way.

Which Telemetry Carries the Tags

Dash0 writes the tags onto all telemetry that belongs to the tagged resource, not only onto the resource Dash0 discovered. For example, the traces of an instrumented Lambda function carry the function's tags, just like its CloudWatch metrics.

Tags apply only to telemetry in the dataset the AWS integration writes to. Telemetry for the same resource in another dataset does not get the tags.

When Tag Changes Appear

Dash0 always uses the newest tag set it discovered for a resource:

  • New or changed tag: Appears after the next discovery run picks up the change from AWS Resource Explorer.
  • Removed tag: Disappears from the resource's telemetry the same way.

Filter by a Tag

Tag attributes work like any other resource attribute:

  • Explorers: In the Trace Explorer, Log Explorer, or Metric Explorer, add a filter on a dash0.cloud.tags.<tag-key> key, for example dash0.cloud.tags.team is payments. See Filtering.
  • Query Builder: Quote the attribute key in PromQL, because it contains dots:
promql
sum by ("dash0.cloud.tags.team") (
  increase({otel_metric_name = "dash0.spans", "dash0.cloud.tags.environment" = "production"}[5m])
)

To control which resources the CloudWatch metrics scrape collects based on their tags, see Filter AWS Metrics by Resource Tags.

Further Reading