Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
-
Evergreen - Milestone 2
Description
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.
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Sprint | Evergreen - Milestone 2 [ 516 ] |
Attachment | screenshot-1.png [ 44471 ] |
Description |
h3. We have errors in Sentry about the log levels we send |
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 | R. Tyler Croy [ rtyler ] | Baptiste Mathus [ batmat ] |
Rank | Ranked higher |
Labels | evergreen sentry | evergreen newbie-friendly sentry |
Assignee | Baptiste Mathus [ batmat ] | R. Tyler Croy [ rtyler ] |
Assignee | R. Tyler Croy [ rtyler ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Assignee | Jochen Schalanda [ joschi ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Resolution | Fixed [ 1 ] | |
Status | In Review [ 10005 ] | Closed [ 6 ] |
Rank | Ranked lower |
I gave this one a try in https://github.com/jenkins-infra/evergreen/pull/328.