influxdata / influxdata/kapacitor
Monitor tag value changes
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Having the possibility to monitor tag value changes as a batch query would be extremely useful.
For example instead of using the deadman function you could compare the server tag values for the last 10 minutes to the values 60+10 minutes ago to see if any servers stopped sending in data. What this also would allow us to do is to monitor for new servers sending in data.
Contributor guide
Research direction
Start by reading Kapacitor's existing deadman function and batch-query handling to understand how time ranges and tag values are represented. Define how a query would compare tag values across the two periods and how it would identify missing or newly reporting servers; done means the behavior is specified and covered by appropriate query tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100