Skip to content

Conversation

@trask
Copy link
Member

@trask trask commented Oct 25, 2025

Related to #12846

.addAttributesExtractors(additionalExtractors)
.addOperationMetrics(HttpClientMetrics.get());
.addOperationMetrics(HttpClientMetrics.get())
.setSchemaUrl(SchemaUrls.V1_37_0);
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it makes sense to set schema url to the most recent version of schema that the instrumentation conforms to(?)

cc @lmolkova

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added this to next week's Semantic Convention SIG meeting to get feedback

trask added 7 commits October 25, 2025 15:04
The test framework was not copying the schema URL from the protobuf
ScopeSpans to the InstrumentationScopeInfo when converting spans,
causing all schema URL assertions to fail even though spans were
correctly emitting schema URLs.
The instrumenterBuilder() method in DefaultHttpClientInstrumenterBuilder
was creating new Instrumenter builders without setting the schema URL.
This affected connection-level instrumentations (e.g., Netty connection
spans for error cases) which use this method to create their instrumenters.

Fixes failing tests in finagle-http-23.11 where connection error spans
were missing the schema URL.
The TelemetryConverter now correctly preserves schema URLs from protobuf
data. The MeterTest files create meters with schema URL 'http://schema.org',
so the test expectations need to be updated to match.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant