Kuadrant / Kuadrant/kuadrant-operator
Add "cause based" example alert queries for DNS operator
Open
Nobody has claimed this yet.
area/observability
- Dominant language
- Go
- Stars
- 94
- Forks
- 89
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 43
Description
WHAT
Create cause-based example alert queries for the dns-operator.
The tabletop scenarios can be used as inspiration for the alerts
possible alerts:
- cannot access DNS Provider
- conflicted default GEO
DONE
- Create alerts for different scenarios for DNS operator
- Create Promtool unit tests for each new alert
Contributor guide
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 with the linked cause-based and tabletop scenario documents, then inspect the DNS operator's existing alert definitions. Use Promtool to add unit tests for each new scenario-based alert. Done means alerts cover the requested DNS operator scenarios and all new alerts have passing Promtool tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, prometheus
- Domain
- observability, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100