-
Notifications
You must be signed in to change notification settings - Fork 889
New issue
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
Remove component
attribute from semantic conventions
#447
Remove component
attribute from semantic conventions
#447
Conversation
@@ -13,7 +13,6 @@ attribute names. | |||
|
|||
| Attribute name | Notes and examples | Required? | | |||
| :------------- | :----------------------------------------------------------- | --------- | | |||
| `component` | Database driver name or database name (when known) `"JDBI"`, `"jdbc"`, `"odbc"`, `"postgreSQL"`. | Yes | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A follow-up for this is #245.
I think we are ready to merge this one, but @arminru might need to do some merging locally first (there's no option to resolve conflicts using the github UI). |
@carlosalberto done! (although I did press the Update branch button on GH 😉) |
@arminru possibly you created the PR without checking the "allow maintainers to update" option checked? |
See open-telemetry/opentelemetry-specification#447 Adapters will later be able to specify what instrumentation library they are, and the exporters can then log this however they want: #264 Co-authored-by: Matthew Wear <[email protected]>
In #271 it was decided to drop the span attribute
component
from the semantic conventions.