influxdata / influxdata/kapacitor
Kapacitor - No data sent by Telegraf agent versus empty data sent by telegraf agent
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
I had a basic query,
Is Kapacitor smart enough to distinguish between the following cases -
1) No data - telegraf not sending data into influxDB only
2) Empty data - telegraf sends the data, but couldn't capture the particular metrics. Or the metrics had no value, but telegraf nevertheless captured the "empty data" and reported it in influxDB
Let's assume I'm monitoring the used percentage for memory.
Case I - Telegraf is down, InfluxDB is not appended with new data, ie no new timestamps for the memory measurement.
Case II - Telegraf captures the data, the data itself has empty values, and telegraf appends this empty data to influxDB, with new timestamps.
So in case I, no new timestamps (and corresponding data) are added to influxDB, but in case II timestamps are data with the corresponding empty data.
Is Kapacitor (basically the deadman) currently smart enough to determine the difference between the two cases?
Thanks
Contributor guide
Research direction
The issue discusses Kapacitor's deadman behavior with Telegraf and InfluxDB, but names no files, tests, or implementation entry points. First determine whether the requested distinction is supported and where deadman handling is defined; done would require a documented, testable distinction between missing timestamps and empty values.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100