Skip to content
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

Conversation

arminru
Copy link
Member

@arminru arminru commented Feb 7, 2020

In #271 it was decided to drop the span attribute component from the semantic conventions.

@@ -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 |
Copy link
Member

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.

@carlosalberto
Copy link
Contributor

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).

@arminru
Copy link
Member Author

arminru commented Feb 11, 2020

@carlosalberto done! (although I did press the Update branch button on GH 😉)

@dyladan
Copy link
Member

dyladan commented Feb 11, 2020

@arminru possibly you created the PR without checking the "allow maintainers to update" option checked?

mwear added a commit to open-telemetry/opentelemetry-ruby that referenced this pull request May 26, 2020
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]>
carlosalberto pushed a commit to carlosalberto/opentelemetry-specification that referenced this pull request Oct 31, 2024
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.

7 participants