-
Bug
-
Resolution: Fixed
-
Minor
-
-
Evergreen - Milestone 2
We have errors in Sentry about the log levels we send
This is because only the following levels are allowed/understood in Sentry (https://docs.sentry.io/clients/node/usage/#raven-node-additional-data):
Sentry is aware of the following levels:
- debug (the least serious)
- info
- warning
- error
- fatal (the most serious)
Expected behavior
We should send levels that Sentry understands, and map the levels we currently send as-is extracted from Java.
As we only send >= WARNING anyway, we mainly (only?) have to map severe to fatal.
[JENKINS-53551] Map log levels sent to Sentry
Sprint | New: Evergreen - Milestone 2 [ 516 ] |
Attachment | New: screenshot-1.png [ 44471 ] |
Description |
Original:
h3. We have errors in Sentry about the log levels we send |
New:
h3. We have errors in Sentry about the log levels we send !screenshot-1.png! This is because only the following levels are allowed/understood in Sentry ([https://docs.sentry.io/clients/node/usage/#raven-node-additional-data):] {quote}Sentry is aware of the following levels: * debug (the least serious) * info * warning * error * fatal (the most serious){quote} h3. Expected behavior We should send levels that Sentry understands, and map the levels we currently send as-is extracted from Java. As we only send >= WARNING anyway, we mainly (only?) have to map {{severe}} to {{fatal}}. |
Assignee | Original: R. Tyler Croy [ rtyler ] | New: Baptiste Mathus [ batmat ] |
Rank | New: Ranked higher |
Labels | Original: evergreen sentry | New: evergreen newbie-friendly sentry |
Assignee | Original: Baptiste Mathus [ batmat ] | New: R. Tyler Croy [ rtyler ] |
Assignee | Original: R. Tyler Croy [ rtyler ] |
I gave this one a try in https://github.com/jenkins-infra/evergreen/pull/328.