-
Notifications
You must be signed in to change notification settings - Fork 897
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
Conversation
a1421c7
to
939e470
Compare
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.
👍
it looks like the markdown-link-check doesn't understand |
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.
I have a few comments about requirement level, and a preference not to use extends
specifically on metrics.
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. |
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.
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
This change refactors HTTP semconv in the following way:
semantic_conventions\http-common.yaml
semantic_conventions\trace\http.yaml
semantic_conventions\metrics\http.yaml
Related: #2666, #2001
It also uses new
attribute_group
semconv type in a few places wherespan
was used incorrectlyThere are a couple of rough edges on tooling side - open-telemetry/build-tools#133. They are not blocking and can be resolved later.