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
This adds basic schema URL support in the API + SDK, specifically in and
around Resources, Tracers, Tracer Provider, and the OTLP exporter.
Some notes, in no particular order:
- I did not add schema URLs to any of our instrumentation, because that
was a lot of work.
- The _API_ ProxyTracer tests around "asking for a tracer multiple times
returns the same thing" don't actually work, because we don't do
anything with the name+version(+schema url, after this change) that
you pass in. I don't think that matters, but I'm not really sure.
- I didn't add the schema information to the jaeger/zipkin exporters,
after surveying what Go and Python were doing. I don't see an easy
place to add it in, either.
1. The behavior of merging two resources with different, non-empty
schema URLs is implementation dependent. I chose to _drop_ the schema
URL in that case and continue merging resources as before. *Is this
what we want?* Other SDKs do things differently (Go returns an error,
Python logs an error and returns the old resource, etc).
2. I did *not* add support to the Configurator for setting the
schema_url on the default Resource that gets initialized. That seemed
like the kind of thing folks would do incorrectly, but you can still
do such a thing by creating and assigning an entire Resource if you
wish. *Is this what we want?*
0 commit comments