Skip to content

Support resource detectors for service telemetry #14311

Closed

Description

@iblancasa

Component(s)

service

Is your feature request related to a problem? Please describe.

The collector's self-observability telemetry doesn't use resource detectors, which means:

  1. Environment variables don't work: OTEL_RESOURCE_ATTRIBUTES and OTEL_SERVICE_NAME are ignored (see [telemetry] Add OTEL_RESOURCE_ATTRIBUTES to otlp-emitted metrics #10909).
  2. 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.
  3. 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

  1. axw commented on Dec 19, 2025

    @axw
    Contributor

    I haven't tested it, but there's a detection/development field that we should probably align with: https://github.com/open-telemetry/opentelemetry-configuration/blob/ddc8c8f47085eb5637a4b1e084b65e384521f8b9/schema/resource.yaml#L12-L16

    That only supports container, host, process, and service detectors at the moment, though -- no cloud.

    Describe alternatives you've considered
    No response

    The alternative is to send telemetry to another local collector to enrich. Probably not ideal, but it's an option.

  2. iblancasa commented on Dec 19, 2025

    @iblancasa
    MemberAuthor

    I haven't tested it, but there's a detection/development field that we should probably align with: https://github.com/open-telemetry/opentelemetry-configuration/blob/ddc8c8f47085eb5637a4b1e084b65e384521f8b9/schema/resource.yaml#L12-L16

    That only supports container, host, process, and service detectors at the moment, though -- no cloud.

    Interesting. I will take a look. Thanks!

  3. iblancasa commented on Jan 12, 2026

    @iblancasa
    MemberAuthor

    I was asked to split #14312 into smaller PRs.

    So I propose these smaller tasks:

  4. iblancasa commented on Oct 1, 2026

    @iblancasa
    MemberAuthor

    Closing since the work was finished.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions