influxdata / influxdata/kapacitor

Data point insertion mandatory after defining deadman tickscript

Open
#2,172 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
2.4k
Forks
479
Avg merge
4d 16h
Merged PRs (30d)
4

Description

I have multiple deadman tick script and me and my team have found a bug with the underlying functionality of deadman. You need to insert atleast 2 datapoints, once you have created task, so as for your deadman script to work. This is intermittent as well, because sometimes only ONE datapoint is successful, in generating a deadman alert.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the deadman tickscript behavior described: create a task, then insert one and two datapoints and compare alert results. Trace the deadman processing path in Kapacitor to identify why datapoint insertion is required or intermittent. Done means the behavior is reproducible, its cause is understood, and deadman alerts trigger reliably with the intended input.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.