Details
-
Type:
Epic
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: evergreen
-
Epic Name:Provide access to Essentials Logging to some developers
-
Similar Issues:
-
Sprint:Evergreen - Milestone 1
Description
We should offer a way to some people to get access to Essentials logging, so that they can understand usage patterns, issues, and improve them.
Acceptance criteria:
- Some developers, who have been marked as allowed to, should be able to access Essentials error logging received from running instances
- Those developers shall see only the Essentials logging, not all logs from Jenkins Infrastructure.
Technical insights
- LDAP is used behind the scene, so R. Tyler Croy says we should be able to restrict/offer access leveraging it.
Attachments
Issue Links
- is blocked by
-
INFRA-1643 Investigate how to segregate infra logs visibility per user role
-
- Closed
-
- is blocking
-
JENKINS-53419 Demo Jenkins Evergreen successfully at DevOps World Jenkins World in SF
-
- Resolved
-
TBD whether we have a dedicated team of developers monitoring new errors and explicitly notifying those responsible; or whether there is a larger pool of “Essentials” developers with access to all the errors who would just be paying the most attention to those introduced by changes they had themselves made.