influxdata / influxdata/kapacitor
Alert for INFO level, even if the "previousLevel" is the SAME (INFO)
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Good afternoon all !
I am receiving an issue:
Everytime that I restart kapacitor or update a tickscript and save it (restart that tick), I am receiving INFO alerts, even if the previous level is INFO. Example for log:
{"id":"lwsn_portal_status_DART_hostname_teste","message":XXXXX","time":"2021-12-22T20:49:58.44Z","duration":0,"level":"INFO","data":{"series":[{"name":"lwsn_web_transaction","tags":{"agent_type":"ts","hostname":"xxxxxxx","id_agent":"418"},"columns":["time","inquire_time_taken_status","status_service","status_service_down","status_service_up"],"values":[["2021-12-22T20:49:58.44Z",1,"UP",-1,3]]}]},"previousLevel":"INFO","recoverable":false}
And I am using .stateChangesOnly().
Any ideas?
Contributor guide
Research direction
Start by reproducing the alert after restarting Kapacitor or updating a tickscript that uses .stateChangesOnly(), and compare the emitted level with previousLevel. Trace the alert state-change handling to determine why identical INFO levels generate alerts; done means repeated INFO levels are suppressed while genuine level changes still alert.
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
- 35/100