On Friday, June 10, 2016 at 4:26:25 PM UTC-6, [email protected] wrote:
>
> Okay, in way that makes sense.
> I have been trying to capture the ALIVE event but so far it eludes me.
> Probably because I do not fully understand what I am looking at in the
> output, nor how this works under the hood.
> So if Kapacitor has uses two minute interval starting at say t=00:00:00.
> From that point on it expects state to be OK. Kapacitor will query the DB
> at t=00:02:00. Say there are no counts in the past 2mins at the time of
> queiry, this will trigger Deadman and emit a CRITICAL alert. This state
> will be present until t=00:04:00, at which point it will query the DB
> again. If at that point there are counts present it should trigger back to
> OK state. If no counts are present then another CRITICAL alert is generated?
This is correct,y ou will get another CRITICAL alert.
> I changed the interval to 1 minute and took another data stream which has
> more counts to make it easier. I am watching a 1 sec graph taking data from
> the same DB so I can see exactly when data is present or not. I am
> capturing DEAD events which display as follows shown below. I see this
> output for exactly 30secs before all counters are cleared. That may not
> mean anything since output does not have to equal actual state?
>
When you say all counters are cleared, do you mean the counters in the
output of `kapacitor show` ? If so than that could be the problem as it
means the task is being stopped and started again loosing all of its state.
Out of troubleshooting time for today. I will get back to this tomorrow.
>
> DOT:
> digraph kapacitor_task_deadman_nl_stat_update_11 {
> graph [throughput="0.00 batches/s"];
>
> query1 [avg_exec_time_ns="0" batches_queried="1" connect_errors="0"
> points_queried="2" query_errors="0" ];
> query1 -> noop3 [processed="1"];
> noop3 [avg_exec_time_ns="0" ];
>
> stats2 [avg_exec_time_ns="0" ];
> stats2 -> derivative4 [processed="3"];
>
> derivative4 [avg_exec_time_ns="0" ];
> derivative4 -> alert5 [processed="2"];
>
> alert5 [alerts_triggered="1" avg_exec_time_ns="0" crits_triggered="1"
> infos_triggered="0" oks_triggered="0" warns_triggered="0" ];
>
>
--
Remember to include the InfluxDB version number with all issue reports
---
You received this message because you are subscribed to the Google Groups
"InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit
https://groups.google.com/d/msgid/influxdb/6e6b69b9-70f6-4345-ada4-77efb702284b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
