-
Notifications
You must be signed in to change notification settings - Fork 182
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
Event yaml definition should allow to document SeverityNumber #828
Comments
@lmolkova I don't think we should associate events with a specific severity number. The severity of an event is based to the context in which the event is occurring, not intrinsic to the event itself. For example, the same exception may be an error or a warning depending on the context. Other events may be debug, info, or warn depending on their context. Based on that, I don't think it is correct to imply there is a default or "correct" severity for events. |
Events SDK default for SeverityNumber |
Discussed at semconv WG 6/17:
|
Area(s)
area:events
What happened?
Description
Based on the spec-ed out Event parameters, events have optional SeverityNumber
But none of the existing events document it and it's not covered in the https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/events.md
Expected Result
We have a way to define and document severity for the events.
Semantic convention version
1.24.0
Additional context
No response
The text was updated successfully, but these errors were encountered: