We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
open-telemetry/opentelemetry-specification#1345 changed the specification to reverse the order in which Resource attributes are merged (updating resource takes precedence).
This needs to be changed in the Go implementation to conform to spec.
The text was updated successfully, but these errors were encountered:
Resolves open-telemetry#1500
c24e1aa
Reverse order of attribute precedence when merging two Resources (#1501)
1952d7b
* Reverse order of attribute precedence when merging two Resources This reflects a change in the specification itself. open-telemetry/opentelemetry-specification#1345 * Resolves #1500 Co-authored-by: Tyler Yahn <[email protected]>
Reverse order of attribute precedence when merging two Resources (ope…
a4604cc
…n-telemetry#1501) * Reverse order of attribute precedence when merging two Resources This reflects a change in the specification itself. open-telemetry/opentelemetry-specification#1345 * Resolves open-telemetry#1500 Co-authored-by: Tyler Yahn <[email protected]>
Successfully merging a pull request may close this issue.
open-telemetry/opentelemetry-specification#1345 changed the specification to reverse the order in which Resource attributes are merged (updating resource takes precedence).
This needs to be changed in the Go implementation to conform to spec.
The text was updated successfully, but these errors were encountered: