[JIRA] (JENKINS-53309) Flavor should be pushed into Sentry
Title: Message Title R. Tyler Croy updated JENKINS-53309 Will be deployed with the next prod deploy Jenkins / JENKINS-53309 Flavor should be pushed into Sentry Change By: R. Tyler Croy Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53309) Flavor should be pushed into Sentry
Title: Message Title R. Tyler Croy updated JENKINS-53309 Jenkins / JENKINS-53309 Flavor should be pushed into Sentry Change By: R. Tyler Croy Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53309) Flavor should be pushed into Sentry
Title: Message Title R. Tyler Croy started work on JENKINS-53309 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53309) Flavor should be pushed into Sentry
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53309 Flavor should be pushed into Sentry Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-08-29 09:52 Labels: evergreen sentry Priority: Minor Reporter: Baptiste Mathus 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). Add Comment