I think it would be very helpful to have directly the flavor pushed with log entries into Sentry.
For instance, it would help understand where a message is coming from and capturing context. If something is going wrong, like an EC2 plugin message for a docker-cloud flavor, we would understand it much quicker.
(Technically: we do have that information in the DB, from the UUID, but it's not accessible to anyone and would require one more hop each time).
- relates to
-
JENKINS-53251 Review Sentry issues
-
- Resolved
-
[JENKINS-53309] Flavor should be pushed into Sentry
Link |
New:
This issue relates to |
Rank | New: Ranked higher |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Review [ 10005 ] | New: Resolved [ 5 ] |
Will be deployed with the next prod deploy