[feature request] schema url for resources

[thompson-tomo]

Package

OpenTelemetry

Is your feature request related to a problem?

The dotnet resource instrumentation doesn't support schema url https://github.com/open-telemetry/opentelemetry-specification/blob/main/spec-compliance-matrix.md#resource

What is the expected behavior?

When a resource is returned by a resource detector it should also contain a schema url property as per the spec. The resource merge process should then consider the schema url and the logic defined in the spec. It should also be exported to backends.

Which alternative solutions or features have you considered?

N/a

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.}

[martincostello]

#6164

[thompson-tomo]

@martincostello i had seen #6164 however that issue only talks about activity source & meter whereas this issue is focussed on resource aka resource detection. Hence different topic especially as we first need a way for libraries to provide the values & then change the resource merge method to consider the schema url. Only once that is done have we caught up to the state of activity source & meter enabling us to look at exporting the schema url value.

Suggest re-opening this to track capturing of the schema url from resource detector libraries and then broadening #6164 to cover exporting the schema url properties where appropriate.

[martincostello]

If we're going to add one then we need to add the other too, we might as well just include it all in the same issue for "supporting schema URLs", so we can just make the existing issue that one too.

[thompson-tomo]

That doesn't necessarily need to be the case atleast as per https://github.com/open-telemetry/opentelemetry-specification/blob/main/spec-compliance-matrix.md where they are listed as individual features ie you can have 1 without the other. This change could have been made long before it was supported on meters & activity source.

In effect that issue could be seen as the start of an epic with a range of different tasks as mentioned in the comment it would involve updating exporters, instrumentations to provide the values and even extending resource detection.

The key thing is schema url = semantic conventions url.

[cijothomas]

Resource's support for schema_url is something that can be done purely in this repo. The one for Activity/Meter requires .NET runtime support, so better to track them separately.

[martincostello]

Resource's support for schema_url is something that can be done purely in this repo. The one for Activity/Meter requires .NET runtime support, so better to track them separately.

Is that not something already possible with the changes in .NET 10?

[cijothomas]

Resource's support for schema_url is something that can be done purely in this repo. The one for Activity/Meter requires .NET runtime support, so better to track them separately.

Is that not something already possible with the changes in .NET 10?

Yes. #6164 can be closed, but this issue is to be kept open to cover Resource. (I just meant to say this is not a duplicate issue, so should be reopened for tracking)

[martincostello]

Is it eligible to be closed? Does some work not need to be done to use the new .NET 10 property?

[cijothomas]

Is it eligible to be closed? Does some work not need to be done to use the new .NET 10 property?

You are right. Some work still required in this repo before closing 6164.

(Irrespective, this issue can be reopened to track the Resource support)