oskoperator / oskoperator/osko
Figure out how to handle severity label in alerting Prometheus Rule
Open
Nobody has claimed this yet.
P2
- Dominant language
- Go
- Stars
- 20
- Forks
- 3
- Avg merge
- 44m
- Merged PRs (30d)
- 7
Description
For example, in automatically generated rules, we already create two different severities in one alerting PrometheusRule
How to decide on what those should be? Opsgenie expects P1 - P4, PagerDuty might expect something else
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the automatically generated alerting PrometheusRule path and the existing severity values. Compare the needs mentioned for Opsgenie and PagerDuty, then define an agreed severity-handling approach and confirm that generated rules use it consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, prometheus
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100