Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardize normalized logging so SREs can reference the logs for Compliance #7

Open
clcollins opened this issue Dec 11, 2023 · 0 comments

Comments

@clcollins
Copy link
Owner

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant