Dash0 Raises $110M Series B at $1B Valuation

Last updated: August 7, 2026

Web Event Attributes

Attributes that Dash0 can add to web events or the associated resources.

Attributes:

KeyStabilityTypeDescriptionExample Values
dash0.auth.token StablestringLast 7 digits of the authentication token used to submit the telemetry to Dash0. [1]abc1234
dash0.resource.hash StablestringHash over all resource attributes of the incoming telemetry payload. [2]9283745019283745019
dash0.resource.id StablestringUnique identifier for the resource in Dash0. [3]12958705279560104980
dash0.resource.name StablestringHuman-readable name for the resource. [4]my-service-pod-abc123; checkout-service
dash0.resource.type StablestringClassification of the resource kind. [5]k8s.pod; k8s.deployment; host; container; aws.lambda; gcp.cloud.run; vercel.project; browser
otel.event.name StablestringIdentifies the class / type of event. [6]browser.mouse.click; device.app.lifecycle
otel.scope.name StablestringThe name of the instrumentation scope - (InstrumentationScope.Name in OTLP).io.opentelemetry.contrib.mongodb
otel.scope.version StablestringThe version of the instrumentation scope - (InstrumentationScope.Version in OTLP).1.0.0

[1] dash0.auth.token: Set at ingestion time by the Dash0 backend. Useful for identifying which token was used when multiple authentication tokens are in use.

[2] dash0.resource.hash: Computed at ingestion time by hashing all resource attributes in a deterministic (sorted) order. It is the most fine-grained resource identifier: each unique set of resource attributes produces a different hash.

See resource equality for how dash0.resource.hash relates to dash0.resource.id.

[3] dash0.resource.id: Computed at ingestion time by applying resource equality rules. Two telemetry items with the same dash0.resource.id are considered to originate from the same logical resource, even if their full attribute sets differ.

[4] dash0.resource.name: Derived at ingestion time from resource attributes using a precedence hierarchy (e.g., Kubernetes pod name, container name, service name). Can be overridden by setting the attribute before telemetry reaches Dash0.

See identify resources by name and type.

[5] dash0.resource.type: Assigned at ingestion time based on the presence of technology-specific resource attributes. For example, the presence of k8s.pod.uid results in type k8s.pod.

See identify resources by name and type.

[6] otel.event.name: This attribute SHOULD be used by non-OTLP exporters when destination does not support EventName or equivalent field. This attribute MAY be used by applications using existing logging libraries so that it can be used to set the EventName field by Collector or SDK components.