Resource Equality

Resource equality is Dash0's solution for identifying when different telemetry sources describe the same logical infrastructure component, despite having different resource attributes. It's a set of 30+ platform-specific rules that Dash0 applies at ingestion time to automatically merge resource fragmentation into unified resource views.

Resource equality is specific to Dash0—it's not a built-in OpenTelemetry mechanism. While OpenTelemetry defines resource attributes as metadata describing the observed system, it doesn't specify how observability backends should handle cases where different telemetry sources use different attributes for the same system. Dash0 solves this with equality rules based on OpenTelemetry semantic conventions, matching resources by stable identifiers like k8s.pod.uidCopy for Kubernetes pods or faas.instanceCopy for AWS Lambda invocations.

When two resources match any equality rule, Dash0 assigns them the same dash0.resource.idCopy, enabling you to query spans, logs, and metrics together even when they come from different telemetry sources with different attribute sets. This happens automatically without configuration—you don't need to modify instrumentation or align attributes across different telemetry collectors. The result is a unified view of each infrastructure component that makes troubleshooting faster and monitoring more accurate.

Further Reading

For practical examples and detailed rules:

• About Resources: Overview of resources in OpenTelemetry and Dash0
• Why Resource Equality?: Real-world fragmentation scenarios and how Dash0 resolves them
• Resource Fragmentation: The problem that resource equality solves
• References: Complete reference for equality, naming, and typing rules across all platforms