I investigated a 'bug' in kapacitor and upgraded to 1.0.0-rc2. Kapacitor doesn't work anymore. I know this is a vague and useless remark, but I don't know how to describe it otherwise. The steps I took are:
- made a reinstall of kapacitor 0.13.1 (a docker container with the content of /var/lib/kapacitor as an external volume) - ran: curl -G 'http://localhost:8086/query?db=telegraf' --data-urlencode 'q=SELECT count(usage_idle) FROM cpu and that responded correctly - created a tick script by copying the example in the Getting started manual (usage_idle) - recorded the stream using command: kapacitor record stream -task cpu_test -duration 20s However this record command never returns. The /var/log/kapacitor/kapacitor.log file contains the following lines: ... [httpd] 2016/09/06 10:24:42 I! ::1 - - [06/Sep/2016:10:24:42 +0000] GET / kapacitor/v1/recordings/3848ad70-dc7e-4b24-afca-d0a0dfe374a0 HTTP/1.1 202 209 - KapacitorClient 200e0ce5-741c-11e6-8ab0-000000000000 7.848494ms [httpd] 2016/09/06 10:24:43 I! ::1 - - [06/Sep/2016:10:24:43 +0000] GET / kapacitor/v1/recordings/3848ad70-dc7e-4b24-afca-d0a0dfe374a0 HTTP/1.1 202 209 - KapacitorClient 205c8036-741c-11e6-8ab1-000000000000 545.448µs ... And it never stops The result of the show command is: ID: cpu_test Error: Type: stream Status: enabled Executing: true Created: 06 Sep 16 09:18 UTC Modified: 06 Sep 16 09:51 UTC LastEnabled: 06 Sep 16 09:51 UTC Databases Retention Policies: ["telegraf"."default"] TICKscript: stream // Select just the cpu measurement from our example database. |from() .measurement('cpu') |alert() .crit(lambda: "usage_idle" < 70) // Whenever we get an alert write it to a file. .log('/tmp/alerts.log') DOT: digraph cpu_test { graph [throughput="0.00 points/s"]; stream0 [avg_exec_time_ns="0" ]; stream0 -> from1 [processed="0"]; from1 [avg_exec_time_ns="0" ]; from1 -> alert2 [processed="0"]; alert2 [alerts_triggered="0" avg_exec_time_ns="0" crits_triggered="0" infos_triggered="0" oks_triggered="0" warns_triggered="0" ]; } The tickscript doesn't generate alerts too. I hope someone as an creative idea where to look for a possible solution for this problem. Thanks! -- 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 influxdb+unsubscr...@googlegroups.com. To post to this group, send email to influxdb@googlegroups.com. 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/13fa89dd-5d5d-48b6-924b-5b38fca01a59%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
