Configure OTel resource detection to automatically populate resource attributes
domain: opentelemetry.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Enable the resource detector for your deployment environment such as AWS, GCP, Azure, or Kubernetes in the OTel SDK or Collector configuration
Map detected resource attributes to the OTel semantic convention resource attributes such as cloud.provider, k8s.pod.name, and host.id
Override auto-detected values with explicit configuration where the detected values are incorrect or insufficient
Verify resource attributes appear on spans and metrics in the backend by querying on service.name and deployment.environment
Use the Collector's resourcedetection processor when instrumenting services that cannot modify their SDK configuration directly
Known gotchas
Resource detection makes HTTP calls to metadata endpoints at startup; in environments without metadata services this causes slow startup or timeout errors if not handled gracefully
Auto-detected resource attributes may include ephemeral values like pod IP addresses; avoid using these as metric dimensions to prevent cardinality issues
Resource detectors are evaluated at SDK initialization time; dynamically changing deployment attributes after startup are not reflected in resource attributes
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?