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

Use attribute_group for cross-signal HTTP attributes #3183

Merged
merged 7 commits into from
Feb 14, 2023

Conversation

lmolkova
Copy link
Contributor

@lmolkova lmolkova commented Feb 7, 2023

This change refactors HTTP semconv in the following way:

  • common (between traces and metrics) attributes moved to semantic_conventions\http-common.yaml
  • tracing-specific attributes are still defined in semantic_conventions\trace\http.yaml
  • metric definitions stay in semantic_conventions\metrics\http.yaml

Related: #2666, #2001

It also uses new attribute_group semconv type in a few places where span was used incorrectly

There are a couple of rough edges on tooling side - open-telemetry/build-tools#133. They are not blocking and can be resolved later.

@lmolkova lmolkova force-pushed the http-attribute-groups branch from a1421c7 to 939e470 Compare February 8, 2023 02:28
Copy link
Member

@trask trask left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

semantic_conventions/http-common.yaml Outdated Show resolved Hide resolved
@trask
Copy link
Member

trask commented Feb 8, 2023

it looks like the markdown-link-check doesn't understand /specification/trace/semantic_conventions/http.md#http-server-definitions 😞

@arminru arminru added semconv:HTTP area:semantic-conventions Related to semantic conventions spec:trace Related to the specification/trace directory spec:metrics Related to the specification/metrics directory labels Feb 8, 2023
@trask
Copy link
Member

trask commented Feb 9, 2023

ping @jsuereth @jamesmoessis @arminru

Copy link
Contributor

@jamesmoessis jamesmoessis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a few comments about requirement level, and a preference not to use extends specifically on metrics.

semantic_conventions/http-common.yaml Show resolved Hide resolved
semantic_conventions/metrics/http.yaml Show resolved Hide resolved
@reyang reyang merged commit 102b00d into open-telemetry:main Feb 14, 2023
Comment on lines -249 to +257
SHOULD include the [application root](#http-server-definitions) if there is one.
SHOULD include the [application root](/specification/trace/semantic_conventions/http.md#http-server-definitions) if there is one.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unless I'm missing something, ... why add an absolute path to an in-page target?
To me this is just confusing because it gives the impression that the target is in another page when it is not.

The same remark applied to the two other links to in-page targets below. IMHO, these changes should be reverted.

/cc @carlosalberto

@marcalff marcalff mentioned this pull request Mar 6, 2023
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
area:semantic-conventions Related to semantic conventions semconv:HTTP spec:metrics Related to the specification/metrics directory spec:trace Related to the specification/trace directory
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants