You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Support resource detectors for service telemetry #14311
Cloud metadata requires manual config: when running on AWS/GCP/Azure, you have to manually configure all the cloud attributes (region, account, instance type, etc.) instead of auto-detecting them.
Host information missing: basic stuff like host.id that could be auto-detected requires manual setup.
Describe the solution you'd like
Since this is something that is available as part of the go-sdk, I would like to see a detectors new field under .service.telemetry that allow enabling the detectores available in the go sdk.
Describe alternatives you've considered
No response
Additional context
No response
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
Activity
axw commentedon Dec 19, 2025
I haven't tested it, but there's a
detection/developmentfield that we should probably align with: https://github.com/open-telemetry/opentelemetry-configuration/blob/ddc8c8f47085eb5637a4b1e084b65e384521f8b9/schema/resource.yaml#L12-L16That only supports container, host, process, and service detectors at the moment, though -- no cloud.
The alternative is to send telemetry to another local collector to enrich. Probably not ideal, but it's an option.
iblancasa commentedon Dec 19, 2025
Interesting. I will take a look. Thanks!
iblancasa commentedon Jan 12, 2026
I was asked to split #14312 into smaller PRs.
So I propose these smaller tasks:
Allow enabling resource detectors via configuration (open-telemetry#1…
iblancasa commentedon Oct 1, 2026
Closing since the work was finished.