Skip to content

Provide alerting best practices #694

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.

Sign up for GitHub

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

Jump to bottom
Open
liu-cong opened this issue Apr 14, 2025 · 3 comments
Open

Provide alerting best practices #694

liu-cong opened this issue Apr 14, 2025 · 3 comments
Labels
triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@liu-cong
Copy link
Contributor

liu-cong commented Apr 14, 2025 •
edited
Loading

What would you like to be added:

Provide a guide on how to configure alerting based on EPP metrics. This is essential for EPP to be production ready.

  1. Provide a general guidance on what metrics and recommended thresholds to alert on, and why they are needed.
  2. Optionally provide a reference implementation.

Why is this needed:
@liu-cong
Copy link
Contributor Author

cc @JeffLuoo

@kfswain
Copy link
Collaborator

kfswain commented Apr 21, 2025

What are we imagining here? Alerting may be techstack dependent

@liu-cong
Copy link
Contributor Author

What are we imagining here? Alerting may be techstack dependent

Updated the issue to clarify. The guide should focus more on "what and why", and the alerting tech stack is more of "how" and that can be either left blank or a reference implementation on a popular stack.

@kfswain kfswain added the triage/accepted Indicates an issue or PR is ready to be actively worked on. label Apr 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@liu-cong @kfswain