influxdata / influxdata/kapacitor
Alerts when kapacitor is restarted
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Good morning all,
We are facing an issue on kapacitor, related with alerts:
Everytime that the kapacitor service is restarted, we are receiving several INFO, WARNING and CRITICAL alerts.
But these alerts are not necessary, because the previous status were not changed.
Do you know the reason of this?
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
The issue names no files, tests, or entry points. Reproduce a Kapacitor service restart while alert statuses are unchanged, then trace the alert handling and state restoration behavior; done means INFO, WARNING, and CRITICAL alerts are not emitted solely because the service restarted, with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100