Skip to content

Resource detectors and service.instance.id #9564

Description

@trask

Hi!

I was working through open-telemetry/semantic-conventions#3860 with @kathiehuang and @Lewis-E and I had a question about a prior discussion in this repo.

It's not clear to me why resource detectors shouldn't record service.instance.id when they have a reasonably appropriate data source such as CONTAINER_APP_REPLICA_NAME on Azure Container Apps or WEBSITE_INSTANCE_ID on Azure App Services.

Could you expand on whether this is a Go SDK limitation or a concern about whether this should be allowed under the specification or semantic conventions? Thanks!

Related:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions