dash0hq/agent-skills

"email": "support@dash0.com"   },   "homepage": "https://github.com/dash0hq/agent-skills",

},   "homepage": "https://github.com/dash0hq/agent-skills",   "repository": "https://github.com/dash0hq/agent-skills",

"homepage": "https://github.com/dash0hq/agent-skills",

"repository": "https://github.com/dash0hq/agent-skills",

**Get your credentials:** - **OTLP Endpoint**: In Dash0: [Settings → Organization → Endpoints → OTLP via HTTP](https://app.dash0.com/goto/settings/endpoints?endpoint_type=otlp_http) or [Settings → Organization → Endpoints → OTLP via gRPC](h

- **OTLP Endpoint**: In Dash0: [Settings → Organization → Endpoints → OTLP via HTTP](https://app.dash0.com/goto/settings/endpoints?endpoint_type=otlp_http) or [Settings → Organization → Endpoints → OTLP via gRPC](https://app.dash0.com/goto/

- **Auth Token**: In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

[Credential-related source omitted]

Replace the placeholders with values from your Dash0 account: - `<OTLP_ENDPOINT>`: copy the gRPC endpoint from [Settings → Endpoints → OTLP via gRPC](https://app.dash0.com/goto/settings/endpoints?endpoint_type=otlp_grpc) (e.g., `ingress.eu-

- `<OTLP_ENDPOINT>`: copy the gRPC endpoint from [Settings → Endpoints → OTLP via gRPC](https://app.dash0.com/goto/settings/endpoints?endpoint_type=otlp_grpc) (e.g., `ingress.eu-west-1.aws.dash0.com:4317`).

[Credential-related source omitted]

[Credential-related source omitted]

- [OpenTelemetry Collector docs](https://opentelemetry.io/docs/collector/)

- [Dash0 Integration Hub](https://www.dash0.com/hub/integrations)

- [Dash0 Guides](https://www.dash0.com/guides?category=opentelemetry)

[Credential-related source omitted]

- [OpenTelemetry Collector documentation](https://opentelemetry.io/docs/collector/)

- [Collector configuration](https://opentelemetry.io/docs/collector/configuration/)

- [Collector contrib components](https://github.com/open-telemetry/opentelemetry-collector-contrib)

- [Dash0 Integration Hub](https://www.dash0.com/hub/integrations)

The [OpenTelemetry Collector contrib distribution](https://github.com/open-telemetry/opentelemetry-collector-contrib) bundles 200+ components.

The [OpenTelemetry Collector Builder](https://github.com/open-telemetry/opentelemetry-collector/tree/main/cmd/builder) (`ocb`) generates a Collector binary from a manifest file that lists the desired components and their versions.

Note: It is possible, and will become increasingly common, to have "off-tree" components that do not reside in the [Collector Core](https://github.com/open-telemetry/opentelemetry-collector) and [Collector Contrib](https://github.com/open-t

**Note:** Enable batching on the exporter with `sending_queue: { batch: {} }` instead of adding the `batchprocessor`; see [exporter queues](https://github.com/open-telemetry/opentelemetry-collector/blob/main/exporter/exporterhelper/README.m

- [OpenTelemetry Collector Builder (OCB)](https://github.com/open-telemetry/opentelemetry-collector/tree/main/cmd/builder)

- [Building a custom Collector](https://opentelemetry.io/docs/collector/custom-collector/)

- [Contrib components list](https://github.com/open-telemetry/opentelemetry-collector-contrib)

- [OpenTelemetry Operator](./deployment/opentelemetry-operator.md) - [Dash0 Kubernetes Operator](./deployment/dash0-operator.md) - [Collector deployment](https://opentelemetry.io/docs/collector/deployment/)

- [Dash0 Kubernetes Operator](./deployment/dash0-operator.md) - [Collector deployment](https://opentelemetry.io/docs/collector/deployment/) - [Collector on Kubernetes](https://opentelemetry.io/docs/collector/deployment/kubernetes/)

- [Collector deployment](https://opentelemetry.io/docs/collector/deployment/)

- [Collector on Kubernetes](https://opentelemetry.io/docs/collector/deployment/kubernetes/)

- [Kubernetes attributes best practices](https://www.dash0.com/guides/opentelemetry-kubernetes-attributes-best-practices)

The [OpenTelemetry Collector Helm chart](https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-collector) deploys the Collector as a DaemonSet, Deployment, or StatefulSet with a single `helm install` com

helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm-charts

[Credential-related source omitted]

[Credential-related source omitted]

Check that business attributes set in application code (e.g., `order.id`) appear on spans, and that `CLIENT` spans are children of `SERVER` spans (not root spans). 6. **Dash0 dataset header is set.**    If the organization uses multiple [da

6. **Dash0 dataset header is set.**    If the organization uses multiple [datasets](https://www.dash0.com/documentation/dash0/key-concepts/datasets), verify the `Dash0-Dataset` header in the Helm values.    The debug exporter shows telemetr

If the organization uses multiple [datasets](https://www.dash0.com/documentation/dash0/key-concepts/datasets), verify the `Dash0-Dataset` header in the Helm values.

If the Dash0 organization uses multiple [datasets](https://www.dash0.com/documentation/dash0/key-concepts/datasets), add the `Dash0-Dataset` header to the OTLP exporter to route telemetry to the correct dataset.

[Credential-related source omitted]

- [OpenTelemetry Collector Helm chart](https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-collector)

- [Helm chart values](https://github.com/open-telemetry/opentelemetry-helm-charts/blob/main/charts/opentelemetry-collector/values.yaml)

The [Dash0 Kubernetes Operator](https://github.com/dash0hq/dash0-operator) automates OpenTelemetry instrumentation, Collector deployment, and telemetry export to Dash0 or any OTLP-compatible backend.

helm repo add dash0-operator https://dash0hq.github.io/dash0-operator

Replace the placeholders: - `<OTLP_ENDPOINT>`: copy the gRPC endpoint from [Settings → Endpoints → OTLP via gRPC](https://app.dash0.com/goto/settings/endpoints?endpoint_type=otlp_grpc) (e.g., `ingress.eu-west-1.aws.dash0.com:4317`).

- `<OTLP_ENDPOINT>`: copy the gRPC endpoint from [Settings → Endpoints → OTLP via gRPC](https://app.dash0.com/goto/settings/endpoints?endpoint_type=otlp_grpc) (e.g., `ingress.eu-west-1.aws.dash0.com:4317`).

- `<API_ENDPOINT>`: copy the API endpoint from [Settings → Endpoints → API](https://app.dash0.com/goto/settings/endpoints?endpoint_type=api_http).

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

Check that business attributes set in application code (e.g., `order.id`) appear on spans, and that `CLIENT` spans are children of `SERVER` spans (not root spans). 5. **Telemetry lands in the correct dataset.**    If the organization uses m

5. **Telemetry lands in the correct dataset.**    If the organization uses multiple [datasets](https://www.dash0.com/documentation/dash0/key-concepts/datasets), verify that telemetry appears in the expected dataset.    See [Dash0 dataset ro

If the organization uses multiple [datasets](https://www.dash0.com/documentation/dash0/key-concepts/datasets), verify that telemetry appears in the expected dataset.

If the Dash0 organization uses multiple [datasets](https://www.dash0.com/documentation/dash0/key-concepts/datasets), set the `dataset` field on the Dash0 export in `Dash0OperatorConfiguration`.

source:     chart: dash0-operator     repoURL: https://dash0hq.github.io/dash0-operator

chart: dash0-operator     repoURL: https://dash0hq.github.io/dash0-operator     targetRevision: "..."

repoURL: https://dash0hq.github.io/dash0-operator

- [Dash0 Kubernetes Operator](https://github.com/dash0hq/dash0-operator)

- [Dash0 Integration Hub](https://www.dash0.com/hub/integrations)

The [OpenTelemetry Operator](https://github.com/open-telemetry/opentelemetry-operator) is a Kubernetes operator that manages Collector instances and auto-instrumentation injection via custom resources.

The operator requires [cert-manager](https://cert-manager.io/) for webhook TLS certificates.

# Install cert-manager (if not already present) kubectl apply -f https://github.com/cert-manager/cert-manager/releases/latest/download/cert-manager.yaml

kubectl apply -f https://github.com/cert-manager/cert-manager/releases/latest/download/cert-manager.yaml

# Install the operator kubectl apply -f https://github.com/open-telemetry/opentelemetry-operator/releases/latest/download/opentelemetry-operator.yaml

kubectl apply -f https://github.com/open-telemetry/opentelemetry-operator/releases/latest/download/opentelemetry-operator.yaml

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

spec:   exporter:     endpoint: http://otel-agent.otel.svc.cluster.local:4317

exporter:     endpoint: http://otel-agent.otel.svc.cluster.local:4317   propagators:

endpoint: http://otel-agent.otel.svc.cluster.local:4317

[Credential-related source omitted]

Check that business attributes set in application code (e.g., `order.id`) appear on spans, and that `CLIENT` spans are children of `SERVER` spans (not root spans). 6. **Dash0 dataset header is set.**    If the organization uses multiple [da

6. **Dash0 dataset header is set.**    If the organization uses multiple [datasets](https://www.dash0.com/documentation/dash0/key-concepts/datasets), verify the `Dash0-Dataset` header in the `OpenTelemetryCollector` CR.    The debug exporte

If the organization uses multiple [datasets](https://www.dash0.com/documentation/dash0/key-concepts/datasets), verify the `Dash0-Dataset` header in the `OpenTelemetryCollector` CR.

If the Dash0 organization uses multiple [datasets](https://www.dash0.com/documentation/dash0/key-concepts/datasets), add the `Dash0-Dataset` header to the OTLP exporter in the `OpenTelemetryCollector` CR.

[Credential-related source omitted]

- [OpenTelemetry Operator](https://github.com/open-telemetry/opentelemetry-operator)

- [Operator API reference](https://github.com/open-telemetry/opentelemetry-operator/blob/main/docs/api.md)

- [Auto-instrumentation](https://opentelemetry.io/docs/kubernetes/operator/automatic/)

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

restart: unless-stopped     healthcheck:       test: ["CMD", "curl", "-f", "http://localhost:13133/"]

healthcheck:       test: ["CMD", "curl", "-f", "http://localhost:13133/"]       interval: 10s

test: ["CMD", "curl", "-f", "http://localhost:13133/"]

[Credential-related source omitted]

Check that business attributes set in application code (e.g., `order.id`) appear on spans, and that `CLIENT` spans are children of `SERVER` spans (not root spans). 6. **Dash0 dataset header is set.**    If the organization uses multiple [da

6. **Dash0 dataset header is set.**    If the organization uses multiple [datasets](https://www.dash0.com/documentation/dash0/key-concepts/datasets), verify the `Dash0-Dataset` header in the ConfigMap.    The debug exporter shows telemetry 

If the organization uses multiple [datasets](https://www.dash0.com/documentation/dash0/key-concepts/datasets), verify the `Dash0-Dataset` header in the ConfigMap.

If the Dash0 organization uses multiple [datasets](https://www.dash0.com/documentation/dash0/key-concepts/datasets), add the `Dash0-Dataset` header to the OTLP exporter in the Collector configuration.

[Credential-related source omitted]

- [OpenTelemetry Operator](./opentelemetry-operator.md) - [Dash0 Kubernetes Operator](./dash0-operator.md) - [Collector deployment](https://opentelemetry.io/docs/collector/deployment/)

- [Dash0 Kubernetes Operator](./dash0-operator.md) - [Collector deployment](https://opentelemetry.io/docs/collector/deployment/) - [Collector on Kubernetes](https://opentelemetry.io/docs/collector/deployment/kubernetes/)

- [Collector deployment](https://opentelemetry.io/docs/collector/deployment/)

- [Collector on Kubernetes](https://opentelemetry.io/docs/collector/deployment/kubernetes/)

- [Kubernetes attributes best practices](https://www.dash0.com/guides/opentelemetry-kubernetes-attributes-best-practices)

1. **OTLP Endpoint**: In Dash0: [Settings → Organization → Endpoints](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUnJItM_GYAM2WK7cqmgdlbcDE0yjHlRZfr7KuDJj2W-yoPf-AmN

2. **Auth Token**: In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

Use `file_storage` with the [file storage extension](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/storage/filestorage) to persist the queue to disk.

Create a dedicated auth token with `Ingesting` permissions only. The Collector needs to send telemetry, not query or manage the organization. In Dash0, create the token at [Settings → Auth Tokens → Create Token](https://app.dash0.com/settin

The Collector needs to send telemetry, not query or manage the organization. In Dash0, create the token at [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens) and select the `Ingesting` scope. See [auth token

In Dash0, create the token at [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens) and select the `Ingesting` scope.

See [auth tokens](https://www.dash0.com/documentation/dash0/key-concepts/auth-tokens) for details on available permission scopes.

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

- [OTLP/gRPC exporter](https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/otlpexporter)

- [OTLP/HTTP exporter](https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/otlphttpexporter)

- [Debug exporter](https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/debugexporter)

- [File storage extension](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/storage/filestorage)

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

- [Collector configuration](https://opentelemetry.io/docs/collector/configuration/)

- [Connectors](https://opentelemetry.io/docs/collector/connectors/)

- [Signal to metrics connector](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/connector/signaltometricsconnector)

- [Health check extension](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/healthcheckextension)

[Credential-related source omitted]

metric:         - 'name == "http.server.duration" and instrumentation_scope.name == "@opentelemetry/instrumentation-http"'         - 'name == "http.client.duration" and instrumentation_scope.name == "@opentelemetry/instrumentation-http"'

- 'name == "http.client.duration" and instrumentation_scope.name == "@opentelemetry/instrumentation-http"'

- [Memory limiter processor](https://github.com/open-telemetry/opentelemetry-collector/tree/main/processor/memorylimiterprocessor)

- [File storage extension](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/storage/filestorage)

- [Why the batch processor is going away](https://www.dash0.com/blog/why-the-opentelemetry-batch-processor-is-going-away-eventually)

- [Filter processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/filterprocessor)

- [Resource detection processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/resourcedetectionprocessor)

- [Kubernetes attributes processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/k8sattributesprocessor)

- [Resource processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/resourceprocessor)

- [Kubernetes attributes best practices](https://www.dash0.com/guides/opentelemetry-kubernetes-attributes-best-practices)

- [OTLP receiver](https://github.com/open-telemetry/opentelemetry-collector/tree/main/receiver/otlpreceiver)

- [Prometheus receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/prometheusreceiver)

- [Filelog receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/filelogreceiver)

- [Hostmetrics receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/hostmetricsreceiver)

The [HTTP metric semantic conventions](https://opentelemetry.io/docs/specs/semconv/http/http-metrics/) and [RPC metric semantic conventions](https://opentelemetry.io/docs/specs/semconv/rpc/rpc-metrics/) define four duration histograms.

|-------------|--------|-----------| | `http.server.request.duration` | HTTP server spans | `kind == SPAN_KIND_SERVER` and `http.request.method` present | | `http.client.request.duration` | HTTP client spans | `kind == SPAN_KIND_CLIENT` and

| `http.server.request.duration` | HTTP server spans | `kind == SPAN_KIND_SERVER` and `http.request.method` present | | `http.client.request.duration` | HTTP client spans | `kind == SPAN_KIND_CLIENT` and `http.request.method` present | | `r

| `http.client.request.duration` | HTTP client spans | `kind == SPAN_KIND_CLIENT` and `http.request.method` present |

signal_to_metrics:     spans:       # HTTP server duration — https://opentelemetry.io/docs/specs/semconv/http/http-metrics/

spans:       # HTTP server duration — https://opentelemetry.io/docs/specs/semconv/http/http-metrics/       - name: http.server.request.duration

# HTTP server duration — https://opentelemetry.io/docs/specs/semconv/http/http-metrics/       - name: http.server.request.duration         description: "Duration of HTTP server requests."

# HTTP client duration — https://opentelemetry.io/docs/specs/semconv/http/http-metrics/       - name: http.client.request.duration         description: "Duration of HTTP client requests."

- name: http.client.request.duration         description: "Duration of HTTP client requests."         unit: s

signal_to_metrics:     spans:       # RPC server duration — https://opentelemetry.io/docs/specs/semconv/rpc/rpc-metrics/

spans:       # RPC server duration — https://opentelemetry.io/docs/specs/semconv/rpc/rpc-metrics/       - name: rpc.server.call.duration

# RPC server duration — https://opentelemetry.io/docs/specs/semconv/rpc/rpc-metrics/

# RPC client duration — https://opentelemetry.io/docs/specs/semconv/rpc/rpc-metrics/

- name: http.client.request.duration         description: "Duration of HTTP client requests."

- [Signal to metrics connector](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/connector/signaltometricsconnector)

- [Span metrics connector](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/connector/spanmetricsconnector)

- [HTTP metric semantic conventions](https://opentelemetry.io/docs/specs/semconv/http/http-metrics/)

- [RPC metric semantic conventions](https://opentelemetry.io/docs/specs/semconv/rpc/rpc-metrics/)

| Requirement | Approach | Collector component | |-------------|----------|---------------------| | Reduce trace volume by a fixed percentage | Head sampling | [`probabilisticsamplerprocessor`](https://github.com/open-telemetry/opentelemetr

| Requirement | Approach | Collector component | |-------------|----------|---------------------| | Reduce trace volume by a fixed percentage | Head sampling | [`probabilisticsamplerprocessor`](https://github.com/open-telemetry/opentelemetr

|-------------|----------|---------------------| | Reduce trace volume by a fixed percentage | Head sampling | [`probabilisticsamplerprocessor`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/probabili

|-------------|----------|---------------------| | Reduce trace volume by a fixed percentage | Head sampling | [`probabilisticsamplerprocessor`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/probabili

| Reduce trace volume by a fixed percentage | Head sampling | [`probabilisticsamplerprocessor`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/probabilisticsamplerprocessor) |

| Reduce trace volume by a fixed percentage | Head sampling | [`probabilisticsamplerprocessor`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/probabilisticsamplerprocessor) |

| Keep all errors, slow traces, and a baseline of normal traces | Tail sampling | [`tailsamplingprocessor`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/tailsamplingprocessor) |

| Keep all errors, slow traces, and a baseline of normal traces | Tail sampling | [`tailsamplingprocessor`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/tailsamplingprocessor) |

| Route all spans of a trace to the same Collector instance | Trace-aware load balancing | [`loadbalancingexporter`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/loadbalancingexporter) |

| Route all spans of a trace to the same Collector instance | Trace-aware load balancing | [`loadbalancingexporter`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/loadbalancingexporter) |

| Generate accurate RED metrics from all traces before sampling | [Metric materialization](./red-metrics.md) | [`signaltometricsconnector`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/connector/signaltometric

| Generate accurate RED metrics from all traces before sampling | [Metric materialization](./red-metrics.md) | [`signaltometricsconnector`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/connector/signaltometric

[Credential-related source omitted]

[Credential-related source omitted]

The `loadbalancingexporter` uses DNS to discover gateway instances. Create a [headless Service](https://kubernetes.io/docs/concepts/services-networking/headless-services/) (with `clusterIP: None`) for the gateway so that DNS returns individ

The `loadbalancingexporter` uses DNS to discover gateway instances. Create a [headless Service](https://kubernetes.io/docs/concepts/services-networking/headless-services/) (with `clusterIP: None`) for the gateway so that DNS returns individ

Create a [headless Service](https://kubernetes.io/docs/concepts/services-networking/headless-services/) (with `clusterIP: None`) for the gateway so that DNS returns individual pod IPs rather than a virtual IP.

Create a [headless Service](https://kubernetes.io/docs/concepts/services-networking/headless-services/) (with `clusterIP: None`) for the gateway so that DNS returns individual pod IPs rather than a virtual IP.

[Credential-related source omitted]

[Credential-related source omitted]

- [Probabilistic sampler processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/probabilisticsamplerprocessor)

- [Probabilistic sampler processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/probabilisticsamplerprocessor)

- [Tail sampling processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/tailsamplingprocessor)

- [Tail sampling processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/tailsamplingprocessor)

- [Load balancing exporter](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/loadbalancingexporter)

- [Load balancing exporter](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/loadbalancingexporter)

**Get your credentials:** - **OTLP Endpoint**: In Dash0: [Settings → Organization → Endpoints](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUnJItM_GYAM2WK7cqmgdlbcDE0

- **OTLP Endpoint**: In Dash0: [Settings → Organization → Endpoints](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUnJItM_GYAM2WK7cqmgdlbcDE0yjHlRZfr7KuDJj2W-yoPf-AmNV

- **Auth Token**: In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

[Credential-related source omitted]

[Credential-related source omitted]

- [OpenTelemetry Docs](https://opentelemetry.io/docs/)

- [Dash0 Integration Hub](https://www.dash0.com/hub/integrations)

- [Dash0 Guides](https://www.dash0.com/guides?category=opentelemetry)

- [OpenTelemetry Documentation](https://opentelemetry.io/docs/)

- [Semantic Conventions](https://opentelemetry.io/docs/specs/semconv/)

- [Dash0 Integration Hub](https://www.dash0.com/hub/integrations)

- [Semantic Conventions: Database Spans](https://opentelemetry.io/docs/specs/semconv/database/database-spans/)

- [Attribute Registry: `db.query.parameter`](https://opentelemetry.io/docs/specs/semconv/registry/attributes/db/#db-query-parameter)

- [Logs](https://opentelemetry.io/docs/concepts/signals/logs/)

- [Semantic Conventions](https://opentelemetry.io/docs/specs/semconv/)

- [Trace Context in non-OTLP Log Formats](https://opentelemetry.io/docs/specs/otel/compatibility/logging_trace_context/)

Before creating a custom metric, check the [semantic conventions for metrics](https://opentelemetry.io/docs/specs/semconv/general/metrics/).

|--------|----------------------------------|-----------------| | HTTP server | `instrumentation-http`, `AspNetCore`, `otelhttp` | `http.server.request.duration`, `http.server.active_requests` | | HTTP client | `instrumentation-http`, `Http

| HTTP server | `instrumentation-http`, `AspNetCore`, `otelhttp` | `http.server.request.duration`, `http.server.active_requests` | | HTTP client | `instrumentation-http`, `HttpClient` | `http.client.request.duration` | | Database client | `

| HTTP client | `instrumentation-http`, `HttpClient` | `http.client.request.duration` |

Refer to the [semantic conventions metric reference](https://opentelemetry.io/docs/specs/semconv/general/metrics/) and the documentation of each instrumentation library for the full list.

Do not create custom metrics in semantic convention namespaces that already exist in the [Attribute Registry](https://opentelemetry.io/docs/specs/semconv/registry/attributes/).

- **Semconv first.**   Before creating a metric, search the [semantic convention metric definitions](https://opentelemetry.io/docs/specs/semconv/) for your domain (HTTP, database, messaging, runtime, etc.).

Before creating a metric, search the [semantic convention metric definitions](https://opentelemetry.io/docs/specs/semconv/) for your domain (HTTP, database, messaging, runtime, etc.).

Always specify a unit using [UCUM](https://ucum.org/) notation.

for (const rm of resourceMetrics) {

for (const rm of exporter.getMetrics()) {

- [Metrics](https://opentelemetry.io/docs/concepts/signals/metrics/)

- [Semantic Conventions for Metrics](https://opentelemetry.io/docs/specs/semconv/general/metrics/)

- [UCUM](https://ucum.org/) — unified code for units of measure

[Credential-related source omitted]

[Credential-related source omitted]

Use the [Dash0 Kubernetes Operator](https://github.com/dash0hq/dash0-operator) to automate instrumentation and resource attribute injection for all workloads in a cluster.

- [Kubernetes attributes best practices](https://www.dash0.com/guides/opentelemetry-kubernetes-attributes-best-practices)

- [Kubernetes semantic conventions](https://opentelemetry.io/docs/specs/semconv/resource/k8s/)

- [Kubernetes downward API](https://kubernetes.io/docs/concepts/workloads/pods/downward-api/)

Generate a random [RFC 4122](https://www.rfc-editor.org/rfc/rfc4122) UUID v4 at process startup.

1. **Existing configuration** — look for `OTEL_EXPORTER_OTLP_ENDPOINT` in `.env`, `.env.local`, `.env.production`, `docker-compose.yml`, Kubernetes manifests (ConfigMaps, Secrets), or Helm values files. 2. **Collector sidecar or DaemonSet**

2. **Collector sidecar or DaemonSet** — if the project deploys an OpenTelemetry Collector as a sidecar or DaemonSet, the SDK endpoint is `http://localhost:4317` (gRPC) or `http://localhost:4318` (HTTP).

[Credential-related source omitted]

[Credential-related source omitted]

In Dash0, create auth tokens at [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens).

Revoke tokens immediately if they are compromised or no longer needed. See [auth tokens](https://www.dash0.com/documentation/dash0/key-concepts/auth-tokens) for full details.

See [auth tokens](https://www.dash0.com/documentation/dash0/key-concepts/auth-tokens) for full details.

[Credential-related source omitted]

- [`service.instance.id` semantic conventions](https://opentelemetry.io/docs/specs/semconv/registry/attributes/service/#service-instance-id)

- [Resource semantic conventions](https://opentelemetry.io/docs/specs/semconv/resource/)

- [OTel SDK configuration](https://opentelemetry.io/docs/languages/sdk-configuration/general/)

- [Service attributes best practices](https://www.dash0.com/guides/opentelemetry-service-attributes-best-practices)

1. **OTLP Endpoint**: Your observability platform's HTTP endpoint    - In Dash0: [Settings → Organization → Endpoints → "OTLP via HTTP"](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNE

- In Dash0: [Settings → Organization → Endpoints → "OTLP via HTTP"](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUnJItM_GYAM2WK7cqmgdlbcDE0yjHlRZfr7KuDJj2W-yoPf-AmNVJ

- Format: `https://<region>.your-platform.com` 2. **Auth Token**: API token for telemetry ingestion    - In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

- In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

[Credential-related source omitted]

- [GitHub Repository](https://github.com/dash0hq/dash0-sdk-web)

[Credential-related source omitted]

- [OpenTelemetry JS Documentation](https://opentelemetry.io/docs/languages/js/getting-started/browser/)

OTEL_DOTNET_VERSION=$(curl -sf "https://api.github.com/repos/open-telemetry/opentelemetry-dotnet-instrumentation/releases/latest" \

| grep '"tag_name"' | cut -d'"' -f4) [ -z "$OTEL_DOTNET_VERSION" ] && { echo "Failed to resolve OTel .NET version" >&2; exit 1; } curl -L -O "https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/releases/download/${OTEL_DO

[ -z "$OTEL_DOTNET_VERSION" ] && { echo "Failed to resolve OTel .NET version" >&2; exit 1; } curl -L -O "https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/releases/download/${OTEL_DOTNET_VERSION}/otel-dotnet-auto-instal

curl -L -O "https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/releases/download/${OTEL_DOTNET_VERSION}/otel-dotnet-auto-install.sh"

**Note**: This script is not supported on Apple Silicon. For Windows, use the [PowerShell guide](https://opentelemetry.io/docs/zero-code/dotnet/getting-started/).

For Windows, use the [PowerShell guide](https://opentelemetry.io/docs/zero-code/dotnet/getting-started/).

| `OTEL_LOGS_EXPORTER` | No | `none` | Set to `otlp` to export logs | | `OTEL_TRACES_SAMPLER` | Yes | `parentbased_always_on` | **Set to `always_on`** — the default lets callers switch off tracing, see [sampling](../spans.md#sampling) | | `

| `OTEL_TRACES_SAMPLER` | Yes | `parentbased_always_on` | **Set to `always_on`** — the default lets callers switch off tracing, see [sampling](../spans.md#sampling) | | `OTEL_EXPORTER_OTLP_ENDPOINT` | Yes | `http://localhost:4318` | OTLP co

| `OTEL_EXPORTER_OTLP_ENDPOINT` | Yes | `http://localhost:4318` | OTLP collector endpoint |

1. **OTLP Endpoint**: Your observability platform's OTLP endpoint    - In Dash0: [Settings → Organization → Endpoints](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUn

- In Dash0: [Settings → Organization → Endpoints](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUnJItM_GYAM2WK7cqmgdlbcDE0yjHlRZfr7KuDJj2W-yoPf-AmNVJ2I%3D)

- Format: `https://<region>.your-platform.com` 2. **Auth Token**: API token for telemetry ingestion    - In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

2. **Auth Token**: API token for telemetry ingestion    - In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens) 3. **Service Name**: Choose a descriptive name (e.g., `order-api`, `checkout-service`)

- In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

Refer to [OpenTelemetry documentation](https://opentelemetry.io/docs/zero-code/dotnet/instrumentations/) for the complete list.

[Serilog](https://serilog.net/) with `Serilog.Formatting.Compact` produces single-line JSON output with exceptions serialized into a structured field.

- [OpenTelemetry .NET Documentation](https://opentelemetry.io/docs/languages/dotnet/)

- [Zero-Code Instrumentation for .NET](https://opentelemetry.io/docs/zero-code/dotnet/)

- [Environment Variable Specification](https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/)

- [Dash0 Kubernetes Operator](https://github.com/dash0hq/dash0-operator)

Install instrumentation packages for the libraries you use from the [OpenTelemetry Registry](https://opentelemetry.io/ecosystem/registry/?language=go).

curl -s https://proxy.golang.org/go.opentelemetry.io/otel/@v/v1.45.0.mod | grep '^go '

| `OTEL_LOGS_EXPORTER` | No | `none` | Leave unset: application logs stay on stdout per [logs](../logs.md) | | `OTEL_TRACES_SAMPLER` | Yes | `parentbased_always_on` | **Set to `always_on`** — the default lets callers switch off tracing, see

| `OTEL_TRACES_SAMPLER` | Yes | `parentbased_always_on` | **Set to `always_on`** — the default lets callers switch off tracing, see [sampling](../spans.md#sampling) | | `OTEL_EXPORTER_OTLP_ENDPOINT` | Yes | `http://localhost:4317` | OTLP co

| `OTEL_EXPORTER_OTLP_ENDPOINT` | Yes | `http://localhost:4317` | OTLP collector endpoint |

1. **OTLP Endpoint**: Your observability platform's OTLP endpoint    - In Dash0: [Settings → Organization → Endpoints](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Db29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUn

- In Dash0: [Settings → Organization → Endpoints](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Db29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUnJItM_GYAM2WK7cqmgdlbcDE0yjHlRZfr7KuDJj2W-yoPf-AmNVJ2I%3D)

- Format: `https://<region>.your-platform.com` 2. **Auth Token**: API token for telemetry ingestion    - In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

2. **Auth Token**: API token for telemetry ingestion    - In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens) 3. **Service Name**: Choose a descriptive name (e.g., `order-api`, `checkout-service`)

- In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

Go does not natively load `.env` files. Use a library like [godotenv](https://github.com/joho/godotenv) or source the file before running:

Use a library like [godotenv](https://github.com/joho/godotenv) or source the file before running:

[Credential-related source omitted]

Go uses individual instrumentation packages from the [OpenTelemetry Registry](https://opentelemetry.io/ecosystem/registry/?language=go).

Refer to the [OpenTelemetry Go instrumentation registry](https://opentelemetry.io/ecosystem/registry/?language=go) for the complete list.

// Wrap an HTTP client transport client := &http.Client{

client := &http.Client{

[zerolog](https://github.com/rs/zerolog) produces single-line JSON by default and handles errors as structured fields.

- [OpenTelemetry Go Documentation](https://opentelemetry.io/docs/languages/go/getting-started/)

- [OpenTelemetry Go Instrumentation Registry](https://opentelemetry.io/ecosystem/registry/?language=go)

- [Environment Variable Specification](https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/)

- [Dash0 Kubernetes Operator](https://github.com/dash0hq/dash0-operator)

OTEL_JAVA_VERSION=$(curl -sf "https://api.github.com/repos/open-telemetry/opentelemetry-java-instrumentation/releases/latest" \

| grep '"tag_name"' | cut -d'"' -f4) [ -z "$OTEL_JAVA_VERSION" ] && { echo "Failed to resolve OTel Java version" >&2; exit 1; } wget "https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/download/${OTEL_JAVA_VERSION

wget "https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/download/${OTEL_JAVA_VERSION}/opentelemetry-javaagent.jar"

| `OTEL_LOGS_EXPORTER` | No | `otlp` | Logs exporter (default is already `otlp`) | | `OTEL_TRACES_SAMPLER` | Yes | `parentbased_always_on` | **Set to `always_on`** — the default lets callers switch off tracing, see [sampling](../spans.md#sa

| `OTEL_TRACES_SAMPLER` | Yes | `parentbased_always_on` | **Set to `always_on`** — the default lets callers switch off tracing, see [sampling](../spans.md#sampling) | | `OTEL_EXPORTER_OTLP_ENDPOINT` | Yes | `http://localhost:4318` | OTLP co

| `OTEL_EXPORTER_OTLP_ENDPOINT` | Yes | `http://localhost:4318` | OTLP collector endpoint |

1. **OTLP Endpoint**: Your observability platform's OTLP endpoint    - In Dash0: [Settings → Organization → Endpoints](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUn

- In Dash0: [Settings → Organization → Endpoints](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUnJItM_GYAM2WK7cqmgdlbcDE0yjHlRZfr7KuDJj2W-yoPf-AmNVJ2I%3D)

- Format: `https://<region>.your-platform.com` 2. **Auth Token**: API token for telemetry ingestion    - In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

2. **Auth Token**: API token for telemetry ingestion    - In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens) 3. **Service Name**: Choose a descriptive name (e.g., `order-api`, `checkout-service`)

- In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

Refer to the [OpenTelemetry registry](https://opentelemetry.io/ecosystem/registry/?language=java) for the complete list.

The [logstash-logback-encoder](https://github.com/logfellow/logstash-logback-encoder) produces single-line JSON with stack traces serialized into a `stack_trace` field.

**Fix**: Verify the library version is supported by checking the [OpenTelemetry registry](https://opentelemetry.io/ecosystem/registry/?language=java).

- [OpenTelemetry Java Documentation](https://opentelemetry.io/docs/languages/java/)

- [Java Agent Releases](https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases)

- [Environment Variable Specification](https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/)

- [Dash0 Kubernetes Operator](https://github.com/dash0hq/dash0-operator)

- Next.js 13+ with App Router - **OTLP Endpoint**: Your observability platform's HTTP endpoint   - In Dash0: [Settings → Organization → Endpoints → "OTLP via HTTP"](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVcl

- **OTLP Endpoint**: Your observability platform's HTTP endpoint   - In Dash0: [Settings → Organization → Endpoints → "OTLP via HTTP"](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_

- In Dash0: [Settings → Organization → Endpoints → "OTLP via HTTP"](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUnJItM_GYAM2WK7cqmgdlbcDE0yjHlRZfr7KuDJj2W-yoPf-AmNVJ

- Format: `https://<region>.your-platform.com` - **Auth Token**: API token for telemetry ingestion   - In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

- **Auth Token**: API token for telemetry ingestion   - In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)   - For browser telemetry, use a token with limited permissions (Ingesting only)

- In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

[Credential-related source omitted]

// CRITICAL: Read env vars inside register() to ensure .env.local is loaded     const OTEL_ENDPOINT =       process.env.OTEL_EXPORTER_OTLP_ENDPOINT || 'http://localhost:4318';

[Credential-related source omitted]

process.env.OTEL_EXPORTER_OTLP_ENDPOINT || 'http://localhost:4318';

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

serviceName: 'my-nextjs-app-frontend',   endpoint: {     url: process.env.NEXT_PUBLIC_OTEL_ENDPOINT || 'http://localhost:4318',

endpoint: {     url: process.env.NEXT_PUBLIC_OTEL_ENDPOINT || 'http://localhost:4318',     authToken: process.env.NEXT_PUBLIC_OTEL_AUTH_TOKEN || 'dev-token',

url: process.env.NEXT_PUBLIC_OTEL_ENDPOINT || 'http://localhost:4318',

[Credential-related source omitted]

rm -rf .next && npm run dev

- [Next.js Instrumentation Docs](https://nextjs.org/docs/app/api-reference/file-conventions/instrumentation)

- [Dash0 SDK Web](https://github.com/dash0hq/dash0-sdk-web)

- [OpenTelemetry Node.js](https://opentelemetry.io/docs/languages/js/getting-started/nodejs/)

| `OTEL_LOGS_EXPORTER` | No | `none` | Set to `otlp` to export logs | | `OTEL_TRACES_SAMPLER` | Yes | `parentbased_always_on` | **Set to `always_on`** — the default lets callers switch off tracing, see [sampling](../spans.md#sampling) | | `

| `OTEL_TRACES_SAMPLER` | Yes | `parentbased_always_on` | **Set to `always_on`** — the default lets callers switch off tracing, see [sampling](../spans.md#sampling) | | `OTEL_EXPORTER_OTLP_ENDPOINT` | Yes | `http://localhost:4317` | OTLP co

| `OTEL_EXPORTER_OTLP_ENDPOINT` | Yes | `http://localhost:4317` | OTLP collector endpoint |

1. **OTLP Endpoint**: Your observability platform's OTLP endpoint    - In Dash0: [Settings → Organization → Endpoints](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUn

- In Dash0: [Settings → Organization → Endpoints](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUnJItM_GYAM2WK7cqmgdlbcDE0yjHlRZfr7KuDJj2W-yoPf-AmNVJ2I%3D)

- Format: `https://<region>.your-platform.com` 2. **Auth Token**: API token for telemetry ingestion    - In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

2. **Auth Token**: API token for telemetry ingestion    - In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens) 3. **Service Name**: Choose a descriptive name (e.g., `order-api`, `checkout-service`)

- In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

Refer to [OpenTelemetry documentation](https://opentelemetry.io/ecosystem/registry/?language=js) for the complete list.

// GOOD: explicit confirmation from downstream const response = await fetch(url);

const response = await fetch(url);

- [OpenTelemetry Node.js Documentation](https://opentelemetry.io/docs/languages/js/getting-started/nodejs/)

- [Auto-Instrumentation Package](https://www.npmjs.com/package/@opentelemetry/auto-instrumentations-node)

- [Environment Variable Specification](https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/)

- [Dash0 Kubernetes Operator](https://github.com/dash0hq/dash0-operator)

sudo apt-get install gcc make autoconf

| `OTEL_LOGS_EXPORTER` | No | `none` | Set to `otlp` to export logs | | `OTEL_TRACES_SAMPLER` | Yes | `parentbased_always_on` | **Set to `always_on`** — the default lets callers switch off tracing, see [sampling](../spans.md#sampling) | | `

| `OTEL_TRACES_SAMPLER` | Yes | `parentbased_always_on` | **Set to `always_on`** — the default lets callers switch off tracing, see [sampling](../spans.md#sampling) | | `OTEL_EXPORTER_OTLP_ENDPOINT` | Yes | `http://localhost:4318` | OTLP co

| `OTEL_EXPORTER_OTLP_ENDPOINT` | Yes | `http://localhost:4318` | OTLP collector endpoint |

1. **OTLP Endpoint**: Your observability platform's OTLP endpoint    - In Dash0: [Settings → Organization → Endpoints](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUn

- In Dash0: [Settings → Organization → Endpoints](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUnJItM_GYAM2WK7cqmgdlbcDE0yjHlRZfr7KuDJj2W-yoPf-AmNVJ2I%3D)

- Format: `https://<region>.your-platform.com` 2. **Auth Token**: API token for telemetry ingestion    - In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

2. **Auth Token**: API token for telemetry ingestion    - In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens) 3. **Service Name**: Choose a descriptive name (e.g., `order-api`, `checkout-service`)

- In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

Refer to [OpenTelemetry documentation](https://opentelemetry.io/ecosystem/registry/?language=php) for the complete list.

[Monolog](https://github.com/Seldaek/monolog) is the standard logging library for Laravel and Symfony.

- [OpenTelemetry PHP Documentation](https://opentelemetry.io/docs/languages/php/getting-started/)

- [OpenTelemetry PHP SDK on Packagist](https://packagist.org/packages/open-telemetry/sdk)

- [Environment Variable Specification](https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/)

- [Dash0 Kubernetes Operator](https://github.com/dash0hq/dash0-operator)

| `OTEL_LOGS_EXPORTER` | No | `otlp` | Log exporter (defaults to `otlp`, unlike Node.js) | | `OTEL_TRACES_SAMPLER` | Yes | `parentbased_always_on` | **Set to `always_on`** — the default lets callers switch off tracing, see [sampling](../spa

| `OTEL_TRACES_SAMPLER` | Yes | `parentbased_always_on` | **Set to `always_on`** — the default lets callers switch off tracing, see [sampling](../spans.md#sampling) | | `OTEL_EXPORTER_OTLP_ENDPOINT` | Yes | `http://localhost:4317` | OTLP co

| `OTEL_EXPORTER_OTLP_ENDPOINT` | Yes | `http://localhost:4317` | OTLP collector endpoint |

1. **OTLP Endpoint**: Your observability platform's OTLP endpoint    - In Dash0: [Settings → Organization → Endpoints](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUn

- In Dash0: [Settings → Organization → Endpoints](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUnJItM_GYAM2WK7cqmgdlbcDE0yjHlRZfr7KuDJj2W-yoPf-AmNVJ2I%3D)

- Format: `https://<region>.your-platform.com` 2. **Auth Token**: API token for telemetry ingestion    - In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

2. **Auth Token**: API token for telemetry ingestion    - In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens) 3. **Service Name**: Choose a descriptive name (e.g., `order-api`, `checkout-service`)

- In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

Python does not automatically load `.env` files. Use a library like [python-dotenv](https://pypi.org/project/python-dotenv/) or export variables in your shell before running:

Use a library like [python-dotenv](https://pypi.org/project/python-dotenv/) or export variables in your shell before running:

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

| Logging | logging (stdlib) | | gRPC | grpcio | | AI/LLM | [OpenLLMetry](https://github.com/traceloop/openllmetry), [OpenLit](https://github.com/openlit/openlit) (generative AI, Langchain observability) |

| AI/LLM | [OpenLLMetry](https://github.com/traceloop/openllmetry), [OpenLit](https://github.com/openlit/openlit) (generative AI, Langchain observability) |

Refer to [OpenTelemetry documentation](https://opentelemetry.io/ecosystem/registry/?language=python) for the complete list.

# GOOD: explicit confirmation from downstream response = requests.get(url)

response = requests.get(url)

The standard `logging` module prints multi-line stack traces by default. Use [python-json-logger](https://pypi.org/project/python-json-logger/) to output single-line JSON with the stack trace captured in a structured field.

Use [python-json-logger](https://pypi.org/project/python-json-logger/) to output single-line JSON with the stack trace captured in a structured field.

[structlog](https://www.structlog.org/) produces single-line JSON output by default when configured with its JSON renderer.

- [OpenTelemetry Python Documentation](https://opentelemetry.io/docs/languages/python/getting-started/)

- [Auto-Instrumentation Package](https://pypi.org/project/opentelemetry-distro/)

- [Environment Variable Specification](https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/)

- [Dash0 Kubernetes Operator](https://github.com/dash0hq/dash0-operator)

| `OTEL_LOGS_EXPORTER` | No | `none` | Set to `otlp` to export logs | | `OTEL_TRACES_SAMPLER` | Yes | `parentbased_always_on` | **Set to `always_on`** — the default lets callers switch off tracing, see [sampling](../spans.md#sampling) | | `

| `OTEL_TRACES_SAMPLER` | Yes | `parentbased_always_on` | **Set to `always_on`** — the default lets callers switch off tracing, see [sampling](../spans.md#sampling) | | `OTEL_EXPORTER_OTLP_ENDPOINT` | Yes | `http://localhost:4318` | OTLP co

| `OTEL_EXPORTER_OTLP_ENDPOINT` | Yes | `http://localhost:4318` | OTLP collector endpoint |

1. **OTLP Endpoint**: Your observability platform's OTLP endpoint    - In Dash0: [Settings → Organization → Endpoints](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUn

- In Dash0: [Settings → Organization → Endpoints](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUnJItM_GYAM2WK7cqmgdlbcDE0yjHlRZfr7KuDJj2W-yoPf-AmNVJ2I%3D)

- Format: `https://<region>.your-platform.com` 2. **Auth Token**: API token for telemetry ingestion    - In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

2. **Auth Token**: API token for telemetry ingestion    - In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens) 3. **Service Name**: Choose a descriptive name (e.g., `order-api`, `checkout-service`)

- In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

Refer to the [OpenTelemetry Ruby Contrib repository](https://github.com/open-telemetry/opentelemetry-ruby-contrib/tree/main/instrumentation) for the complete list.

[semantic_logger](https://github.com/reidmorrison/semantic_logger) produces single-line JSON with exceptions serialized into structured fields.

For Rails applications, [lograge](https://github.com/roidrage/lograge) replaces the default multi-line request log with a single-line JSON entry.

- [OpenTelemetry Ruby Documentation](https://opentelemetry.io/docs/languages/ruby/)

- [OpenTelemetry Ruby Contrib](https://github.com/open-telemetry/opentelemetry-ruby-contrib)

- [Environment Variable Specification](https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/)

- [Dash0 Kubernetes Operator](https://github.com/dash0hq/dash0-operator)

OTEL_JAVA_VERSION=$(curl -sf "https://api.github.com/repos/open-telemetry/opentelemetry-java-instrumentation/releases/latest" \

| grep '"tag_name"' | cut -d'"' -f4) [ -z "$OTEL_JAVA_VERSION" ] && { echo "Failed to resolve OTel Java version" >&2; exit 1; } wget "https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/download/${OTEL_JAVA_VERSION

wget "https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/download/${OTEL_JAVA_VERSION}/opentelemetry-javaagent.jar"

For sbt projects, resolve the agent from Maven Central via the [sbt-javaagent](https://github.com/sbt/sbt-javaagent) plugin. Maven artifacts are immutable and checksum-verified, which avoids the unpinned-runtime-download risk of fetching th

Find the current version at [sbt-javaagent releases](https://github.com/sbt/sbt-javaagent/releases).

The plugin resolves the agent JAR through sbt's dependency resolution (Maven Central), caches it in the local Ivy/Coursier cache, and wires `-javaagent:<resolved-path>` into the `run`, `test`, and packaging tasks automatically. Bump the ver

Bump the version when a new release is published: [Maven Central — opentelemetry-javaagent](https://central.sonatype.com/artifact/io.opentelemetry.javaagent/opentelemetry-javaagent).

Find the current version at [Maven Central — opentelemetry-api](https://central.sonatype.com/artifact/io.opentelemetry/opentelemetry-api).

Never fill a `<version>` placeholder in `build.sbt` from memory; verify the coordinate and version exist on Maven Central first, per [verify-dependencies](../verify-dependencies.md). Look the artifact up on [Maven Central](https://central.s

Look the artifact up on [Maven Central](https://central.sonatype.com/) (as the links above do), or verify resolution from the command line with Coursier, which sbt uses internally:

| `OTEL_LOGS_EXPORTER` | No | `otlp` | Logs exporter (default is already `otlp`) | | `OTEL_TRACES_SAMPLER` | Yes | `parentbased_always_on` | **Set to `always_on`** — the default lets callers switch off tracing, see [sampling](../spans.md#sa

| `OTEL_TRACES_SAMPLER` | Yes | `parentbased_always_on` | **Set to `always_on`** — the default lets callers switch off tracing, see [sampling](../spans.md#sampling) | | `OTEL_EXPORTER_OTLP_ENDPOINT` | Yes | `http://localhost:4318` | OTLP co

| `OTEL_EXPORTER_OTLP_ENDPOINT` | Yes | `http://localhost:4318` | OTLP collector endpoint |

1. **OTLP Endpoint**: Your observability platform's OTLP endpoint    - In Dash0: [Settings → Organization → Endpoints](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUn

- In Dash0: [Settings → Organization → Endpoints](https://app.dash0.com/settings/endpoints?s=eJwtyzEOgCAQRNG7TG1Cb29h5REMcVclIUDYsSLcXUxsZ95vcJgbxNObEjNET_9Eok9wY2FIlzlNUnJItM_GYAM2WK7cqmgdlbcDE0yjHlRZfr7KuDJj2W-yoPf-AmNVJ2I%3D)

- Format: `https://<region>.your-platform.com` 2. **Auth Token**: API token for telemetry ingestion    - In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

2. **Auth Token**: API token for telemetry ingestion    - In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens) 3. **Service Name**: Choose a descriptive name (e.g., `order-api`, `checkout-service`)

- In Dash0: [Settings → Auth Tokens → Create Token](https://app.dash0.com/settings/auth-tokens)

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

Refer to the [OpenTelemetry registry](https://opentelemetry.io/ecosystem/registry/?language=java) for the complete list.

The [logstash-logback-encoder](https://github.com/logfellow/logstash-logback-encoder) produces single-line JSON with stack traces serialized into a `stack_trace` field.

[scala-logging](https://github.com/lightbend-labs/scala-logging) is a thin Scala wrapper around SLF4J.

**Fix**: Verify the library version is supported by checking the [OpenTelemetry registry](https://opentelemetry.io/ecosystem/registry/?language=java).

- [OpenTelemetry Java Documentation](https://opentelemetry.io/docs/languages/java/)

- [Java Agent Releases](https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases)

- [Environment Variable Specification](https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/)

- [Dash0 Kubernetes Operator](https://github.com/dash0hq/dash0-operator)

|-------|-------------|-----------| | `user.id` | Spans, logs | Only if the value is an opaque identifier (UUID, internal ID), never a username or email | | `enduser.id` | Spans, logs | Same as `user.id` — use whichever matches the [Attribu

| `user.id` | Spans, logs | Only if the value is an opaque identifier (UUID, internal ID), never a username or email | | `enduser.id` | Spans, logs | Same as `user.id` — use whichever matches the [Attribute Registry](https://opentelemetry.i

| `enduser.id` | Spans, logs | Same as `user.id` — use whichever matches the [Attribute Registry](https://opentelemetry.io/docs/specs/semconv/registry/attributes/) |

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

- [OpenTelemetry Specification: Sensitive Data](https://opentelemetry.io/docs/specs/otel/overview/#sensitive-data)

- [Attribute Registry](https://opentelemetry.io/docs/specs/semconv/registry/attributes/)

The span hygiene rules in this file are aligned with the [Instrumentation Score](https://github.com/instrumentation-score/spec) specification — a vendor-neutral scoring system that quantifies how well a service follows OpenTelemetry best pr

for (let attempt = 1; attempt <= maxRetries; attempt++) {       try {         const response = await fetch(url);

try {         const response = await fetch(url);         return response;

const response = await fetch(url);

Record exception details as a structured log record, not as a span event. The [Span Event API is being deprecated](https://github.com/open-telemetry/opentelemetry-specification/blob/main/oteps/4430-span-event-api-deprecation-plan.md) in fav

The [Span Event API is being deprecated](https://github.com/open-telemetry/opentelemetry-specification/blob/main/oteps/4430-span-event-api-deprecation-plan.md) in favour of log-based events.

Follow the [Attribute Registry](https://opentelemetry.io/docs/specs/semconv/registry/attributes/) conventions:

Configure the `AlwaysOn` sampler explicitly in application SDKs. This overrides the [specified default](https://opentelemetry.io/docs/specs/otel/trace/sdk/#built-in-samplers), `ParentBased(root=AlwaysOn)`, which is exposed as `parentbased_a

This overrides the [specified default](https://opentelemetry.io/docs/specs/otel/trace/sdk/#built-in-samplers), `ParentBased(root=AlwaysOn)`, which is exposed as `parentbased_always_on` in `OTEL_TRACES_SAMPLER`.

# An external caller suppressing all telemetry for this request and everything downstream of it curl -H 'traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-00' \

curl -H 'traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-00' \

https://api.example.com/checkout

Defer all sampling decisions to the [Collector or observability pipeline](../../otel-collector/rules/sampling.md), where they can be changed centrally without redeploying applications. The Collector can apply head sampling with the [`probab

The Collector can apply head sampling with the [`probabilisticsamplerprocessor`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/probabilisticsamplerprocessor), or tail sampling with the [`tailsamplingp

Treat trace shape — spans, their parent-child relations, kinds, status codes, and attributes — as a functional requirement. Use an in-memory span exporter in integration tests to capture spans produced by the code under test and assert the 

The examples below use [JavaScript SDK 2.x APIs](https://github.com/open-telemetry/opentelemetry-js/blob/main/doc/upgrade-to-2.x.md): configure processors in the provider constructor and read parents through `parentSpanContext`.

- [Instrumentation Score Specification](https://github.com/instrumentation-score/spec) — vendor-neutral scoring for OpenTelemetry instrumentation quality

- [Semantic Conventions: Traces](https://opentelemetry.io/docs/specs/semconv/general/trace/) — general span conventions

- [HTTP Spans](https://opentelemetry.io/docs/specs/semconv/http/http-spans/) — HTTP-specific span and status rules

- [Dash0 Semantic Conventions Explainer](https://www.dash0.com/knowledge/otel-semantic-conventions-explainer) — comprehensive guide

- [Metrics](https://opentelemetry.io/docs/concepts/signals/metrics/)

- [Traces](https://opentelemetry.io/docs/concepts/signals/traces/)

- [Logs](https://opentelemetry.io/docs/concepts/signals/logs/)

- [Semantic Conventions](https://opentelemetry.io/docs/specs/semconv/)

|-------|---------------|------------| | `OTEL_SERVICE_NAME` is set | Print the environment variable in the application logs at startup | Set it in the deployment manifest or application config | | `OTEL_EXPORTER_OTLP_ENDPOINT` is set and r

| `OTEL_SERVICE_NAME` is set | Print the environment variable in the application logs at startup | Set it in the deployment manifest or application config | | `OTEL_EXPORTER_OTLP_ENDPOINT` is set and reachable | `curl -v <endpoint>/v1/trace

| `OTEL_EXPORTER_OTLP_ENDPOINT` is set and reachable | `curl -v <endpoint>/v1/traces` returns a response (even an error response confirms network reachability) | Fix the endpoint URL, check DNS resolution, open network policies or firewall 

# No incoming parent: expect a new SERVER root. curl http://localhost:8080/checkout

curl http://localhost:8080/checkout

# Sampled remote parent: expect this trace ID and parent span ID on the SERVER span. curl -H 'traceparent: 00-11111111111111111111111111111111-2222222222222222-01' http://localhost:8080/checkout

curl -H 'traceparent: 00-11111111111111111111111111111111-2222222222222222-01' http://localhost:8080/checkout

# Unsampled remote parent with AlwaysOn: expect exported spans with this trace ID. # The SERVER parent span ID must be 4444444444444444. curl -H 'traceparent: 00-33333333333333333333333333333333-4444444444444444-00' http://localhost:8080/ch

curl -H 'traceparent: 00-33333333333333333333333333333333-4444444444444444-00' http://localhost:8080/checkout

5. When the lookup shows the package is deprecated, yanked, or has no recent release, do not add it: fall back to the auto-instrumentation path or manual instrumentation per the language's SDK rule, and state why.    When this means removin

When this means removing a dependency that is already in the manifest, follow [Dropping an existing dependency](#dropping-an-existing-dependency). 6. When the lookup finds no package at all, do not invent a name: check the [OpenTelemetry re

6. When the lookup finds no package at all, do not invent a name: check the [OpenTelemetry registry](https://opentelemetry.io/ecosystem/registry/) for the library, and if nothing current exists, instrument manually per [spans](./spans.md) a

- [OTTL Guide](https://www.dash0.com/guides/opentelemetry-transformation-language-ottl)

- [OTTL Specification](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/pkg/ottl)

- [OTTL Functions Reference](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/pkg/ottl/ottlfuncs)

- [OTTL Playground](https://ottl.run)

The [Attribute Registry](https://opentelemetry.io/docs/specs/semconv/registry/attributes/) is the single source of truth for all defined attributes.

- [Attribute Registry](https://opentelemetry.io/docs/specs/semconv/registry/attributes/)

- [Semantic Conventions Specification](https://opentelemetry.io/docs/specs/semconv/)

- [Semantic Conventions Repository](https://github.com/open-telemetry/semantic-conventions)

- [Dash0 Semantic Conventions](https://www.dash0.com/documentation/dash0/semantic-conventions)

- [Dash0 Semantic Conventions Explainer](https://www.dash0.com/knowledge/otel-semantic-conventions-explainer)

1. **Search the registry first** — Look up the concept in the [Attribute Registry](https://opentelemetry.io/docs/specs/semconv/registry/attributes/). Use the standard name if it exists (e.g., prefer `http.request.method` over a custom `cust

When adding attributes to telemetry, always search the [Attribute Registry](https://opentelemetry.io/docs/specs/semconv/registry/attributes/) first and place each attribute at the correct telemetry level.

1. **Registry first.**    Before creating a custom attribute, search the [Attribute Registry](https://opentelemetry.io/docs/specs/semconv/registry/attributes/).

Before creating a custom attribute, search the [Attribute Registry](https://opentelemetry.io/docs/specs/semconv/registry/attributes/).

Full registry: https://opentelemetry.io/docs/specs/semconv/registry/attributes/

- [Attribute Registry](https://opentelemetry.io/docs/specs/semconv/registry/attributes/) — the single source of truth for all attribute definitions

- [Semantic Conventions Specification](https://opentelemetry.io/docs/specs/semconv/) — full specification across all signals

- [Dash0 Semantic Conventions Explainer](https://www.dash0.com/knowledge/otel-semantic-conventions-explainer) — comprehensive guide to understanding and applying conventions

- [Dash0 Semantic Conventions](https://www.dash0.com/documentation/dash0/semantic-conventions) — full list of derived attributes

- [Dash0 Semantic Conventions Explainer](https://www.dash0.com/knowledge/otel-semantic-conventions-explainer) — comprehensive guide to conventions

| `deployment.environment` | `deployment.environment.name` | | `http.server.duration` | `http.server.request.duration` (unit: ms → s) | | `http.client.duration` | `http.client.request.duration` (unit: ms → s) |

| `http.client.duration` | `http.client.request.duration` (unit: ms → s) |

This means you can upgrade your instrumentation libraries at your own pace — Dash0 handles the normalization. See [Dash0 Semantic Convention Upgrades](https://www.dash0.com/documentation/dash0/semantic-conventions/opentelemetry-semantic-con

- [Semantic Conventions Repository](https://github.com/open-telemetry/semantic-conventions) — source YAML models, version tags, and changelogs

- [Dash0 Semantic Convention Upgrades](https://www.dash0.com/documentation/dash0/semantic-conventions/opentelemetry-semantic-convention-upgrades) — automatic convention version management