OpenTelemetry fully supports the AWS Tracing header
Note the failure to detect any resource information MUST NOT be considered an error, whereas an error that occurs during an attempt to detect resource information SHOULD be considered an error.
/metadataendpoint or whatever, what should happen?
I was doing a final comb of the tracing spec to prepare for the release of the JS API and I noticed current trace API spec states:
The API MUST implement methods to create a SpanContext. These methods SHOULD be the only way to create a SpanContext. This functionality MUST be fully implemented in the API, and SHOULD NOT be overridable.
In JS the SpanContext is just an interface that any plain object can meet and there currently exists no API to create a span context. What is the intention behind requiring the API to be the only way to create a SpanContext