-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Blog post: HTTP semantic conventions declared stable #3472
Conversation
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.
Nice blog. I made a first pass. See inline comments.
a9796fc
to
a93ef48
Compare
Co-authored-by: Liudmila Molkova <[email protected]>
Co-authored-by: Patrice Chalin <[email protected]>
a93ef48
to
971f27a
Compare
971f27a
to
29fe8fc
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.
LGTM and left some comments inline.
- The `url.*` namespace, which can be reused in the future by non-HTTP | ||
semantic conventions | ||
- The `client.*` and `server.*` namespaces, which are easier to reason about | ||
and work better on logs (where there is no span kind) |
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.
What exactly does that mean?
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've expanded this bullet, lmk if it helps
namespaces | ||
- Further alignment with Prometheus by adopting seconds as the standard unit for | ||
metrics | ||
- Attributes which are less generally useful are no longer captured by default |
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.
As a reader, not sure I understand what you mean with "to implement a transition plan". What do I have to do, if anything? Are there scripts that help me automate things? Maybe I don't need to do anything since OpenTelemetry is taking care of it, etc.
I suggest being more explicit about expectations and shared responsibility model.
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.
thx, I redid the transition plan section to try to make it clearer, ptal
Co-authored-by: Patrice Chalin <[email protected]>
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.
@trask: I've added the first table, PTAL and merge if you like it. I'll work on the other sections after that.
Co-authored-by: Patrice Chalin <[email protected]>
Co-authored-by: Patrice Chalin <[email protected]>
Co-authored-by: Patrice Chalin <[email protected]>
Co-authored-by: Patrice Chalin <[email protected]>
Co-authored-by: Patrice Chalin <[email protected]>
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.
This is looking great! One final copyedit. 🚀
Thanks @mhausenblas |
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.
Let's make this monday of next week and merge.
I re-triggered the production build, and the HTTP semconv is now live! https://opentelemetry.io/blog/2023/http-conventions-declared-stable/ |
Would love to publish this before KubeCon.
Of course, we still have to declare HTTP semconv stabillity first. There's a decent chance that will happen on Friday (11/3).DONE!Closes open-telemetry/semantic-conventions#43
Preview: https://deploy-preview-3472--opentelemetry.netlify.app/blog/2023/http-conventions-declared-stable/