Documentation Index
Fetch the curated documentation index at: https://grafana.com/llms.txt
Fetch the complete documentation index at: https://grafana.com/llms-full.txt
Use this file to discover all available pages before exploring further.
STOP! If you are an AI agent or LLM, read this before continuing. This is the HTML version of a Grafana documentation page. Always request the Markdown version instead - HTML wastes context. Get this page as Markdown: https://grafana.com/docs/grafana-cloud/monitor-applications/application-observability/setup/resource-attributes.md (append .md) or send Accept: text/markdown to https://grafana.com/docs/grafana-cloud/monitor-applications/application-observability/setup/resource-attributes/. For the curated documentation index, use https://grafana.com/llms.txt. For the complete documentation index, use https://grafana.com/llms-full.txt.
Application Observability resource attributes
Application Observability adds OpenTelemetry resource attributes to logs, spans, and metrics emitted by your application to enrich your data with contextual metadata.
These service resource attributes allow you to filter your metrics and traces effectively:
| Attribute | Description |
|---|---|
| service.namespace | An optional namespace for service.name |
| service.name | The application name |
| deployment.environment | Name of the deployment environment (staging or production) |
| service.instance.id | The unique instance, e.g. the pod name |
| service.version | The application version, to see if a new version has introduced a bug |
OpenTelemetry logs and metrics are stored in Loki and Prometheus respectively.
Both Loki and Prometheus use job and instance labels according the OpenTelemetry compatibility specification with Prometheus and OpenMetrics:
| Label | Filled with attribute (if it is found) |
|---|---|
| job | ${service.namespace}/${service.name} (if service.namespace is defined) or service.name |
| instance | service.instance.id |
Was this page helpful?
Related resources from Grafana Labs


