I’m currently in a quandary where I have to rollup metrics and store them for years at a time, but I only have Elasticsearch as a backend, not InfluxDB. It was suggested by @daniel that Kapacitor could potentially serve the purpose of taking the stream data from Telegraf, roll it up, and send it ba…

@jasonmkeller What are you having trouble with?

To start at the top, I’ve installed Kapacitor and tried to enable it to start on system startup, but I get this error… systemctl enable kapacitor Failed to execute operation: Too many levels of symbolic links On the script syntax, I’m completely lost as to how in tickscript how to nest the two ope…

@jasonmkeller Hmm… That sounds like a packaging issue. Getting both of those operations into one tick script should be doable. Can you share what OS you are using and the /etc/systemd/system/kapacitor.service or /etc/init.d/kapacitor file?

RHEL7… # ls -lh /etc/systemd/system lrwxrwxrwx. 1 root root 41 Apr 7 10:01 kapacitor.service -> /usr/lib/systemd/system/kapacitor.service -rw-rw-r--. 1 root root 466 Mar 22 22:47 kibana.service -rw-r--r--. 1 root root 511 Mar 30 13:47 logstash.service Looks like it probably doesn’t like the s…

RHEL7 failed to enable service #1309 on Github now

From @jasonmkeller on the github issue: oooh! that poke did it. I’d have never guessed to switch an output from telegraf to the api endpoint of kapacitor (I thought that was only for commands to it, not data). $ kapacitor stats ingress Database Retention Policy Measurement Points Received _…

Right now I’m flushing the data from Kapacitor back to Telegraf via an http input to take advantage of the native Elasticsearch plugin (I built from MASTER to take that for a spin prior to 1.3 dropping, and thus far the performance has been markedly better (80% better) than the GELF output (which we…

# tail -50 /var/log/kapacitor/kapacitor.log [httpd] 127.0.0.1 - - [11/Apr/2017:16:54:10 -0500] "POST /write?db=telegraf HTTP/1.1" 204 0 "-" "-" 64b4765d-1f01-11e7-82ed-000000000000 458 [httpd] 127.0.0.1 - - [11/Apr/2017:16:54:20 -0500] "POST /write?db=telegraf HTTP/1.1" 204 0 "-" "-" 6aaa58f3-1f01-1…

For the derivative calculation it should be something like this: stream |from() .measurement('m') .groupBy(*) |derivative('value') .unit(1s) // This will handle the clear/roll over of the counter. // Basically the derivative operation compares two points…

Using Kapacitor to rollup metrics

InfluxDB 1 Kapacitor

jackzampolin April 7, 2017, 10:51pm 6

@jasonmkeller Can you open an issue on Kapacitor with this info? We like to get those build issues taken care of. I’m checking on the TICKScript question for you

Topic		Replies	Views
Kapacitor data aggregation does not save aggregated data for all series influxdb , kapacitor	8	1918	April 3, 2017
Error in log kapacitor, please solution for solve	0	2692	August 20, 2018
InfluxDB CQ vs Kapacitor Batch vs Kapacitor Stream influxdb , kapacitor	7	3515	March 15, 2017
Telegraf -> Kapacitor -> InfluxDB possible? influxdb , telegraf , kapacitor	2	2406	March 7, 2017
Multiple Data Center Replication with InfluxDB	2	2905	January 31, 2019

Using Kapacitor to rollup metrics

Related topics