Define HTTP exception events#3414
Conversation
|
This PR contains changes to area(s) that do not have an active SIG/project and will be auto-closed:
Such changes may be rejected or put on hold until a new SIG/project is established. Please refer to the Semantic Convention Areas |
60836cc to
4ffee8f
Compare
lmolkova
left a comment
There was a problem hiding this comment.
I believe we'll need to define default severity for these events (before stability) and probably add more attributes, but it can be done incrementally
👍 Added in 5cc9640
yeah, I'm torn on this (#3414 (comment)), did you have any preliminary thoughts? |
|
Discussed adding more attributes in Log SIG. Sampling. Adding attributes later wouldn't be breaking.
Instrumentations MAY provide flag to copy all span attributes over to exception. |
37e9d6f to
2b1236f
Compare
Added in 2810603 |
590ee3e to
fec4913
Compare
Part of migrating from recording exceptions as span events to recording them as logs.
Assigning event names to exceptions which correspond to existing semantic conventions provides an additional level of correlation between the signals, and makes it easy to view these specific sets of exceptions.
The idea would be to also define these for Database, RPC, Messaging (at least).
Prototype at open-telemetry/opentelemetry-java-instrumentation#16049