You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Standardize SREPDs logging mechanism to SREs can use the log to easily identify what cluster they logged into for which incident, at what time, to allow for easy compliance information lookup. SREPD should also have a command-line argument to retrieve the info from the log without the SRE having to open/grep/etc.
Done Criteria:
A command line argument exists to take a cluster ID and return the logs showing PagerDuty Incident ID, Timestamp, and ClusterID from the log file.
Debug logging is toggle-able via command line argument and config file
Logfile is viewable in a pane within SREPD for quick review of events that just occurred
Debug, error and general info is separated by Tag from "SRE Action" logs
SRE Action logs are a concise set of logs specific to actions taken in relation to the PagerDuty Incident (ack, note, silence, login, etc) and not informational, error or debug info.
The text was updated successfully, but these errors were encountered:
Standardize SREPDs logging mechanism to SREs can use the log to easily identify what cluster they logged into for which incident, at what time, to allow for easy compliance information lookup. SREPD should also have a command-line argument to retrieve the info from the log without the SRE having to open/grep/etc.
Done Criteria:
The text was updated successfully, but these errors were encountered: