Understanding Kapacitor’s deadman Act

Nobody has claimed this yet.

Hi, I'm using telegraf to supervise some process. So I thought it could be interesting if kapacitor is able to notify me when any process die.

I think this can be done with Kapacitor's deadman switch (if a process die, telegraf's procstat input can't send data to influxdb). But i'm having troubles with this, if I kill the process, Kapacitor will send the alert, but when I restart the process, Kapacitor still sending the alert.

I'm trying something like this:

|deadman(1.0, 10s)
.slack()
.channel('#alerts-staging')

If no point has been arrived in 10s, send the alert ( I think it works like that).

But executing kapacitor show in the task, I can see graph [throughput="0.00 points/s"];
I don't know if this thoughput matters.

I'm using kapacitor 1.3.1-1 on Debian 8.

Thanks.

Reproduce the reported behavior with Kapacitor 1.3.1-1, the procstat input, and the deadman task shown in the issue. Check the task output from kapacitor show, including throughput, before and after restarting the supervised process. Done means determining why the alert does not clear and documenting or fixing the behavior.

Written by the indexing model from the issue text.