Kapacitor

Hammering nails into Kapacitor coffin

TICK is dead

Sometimes there are sad moments when you realize you’ve chosen the wrong tech. It takes time to internalize a new shiny tech, to get some expertise in it. That expertise later yield only one meaningful insight…

Avoiding combinatorial explosion in continuous queries in Influx

How not to do CQs, and how to do them right

My small development environment suddenly stops producing performance data. I looked into few places and quickly…

no data in retention policy in Kapacitor

Mild WTF which had cost me 1 hour of my life

If you suspect that your task does not receive data, check Kapacitor configuration file.

kapacitor-unit — almost perfect

Testing a foundation for stable complexity. The more complex something is the higher is demand for stability, and a single industry-proven way for stability in large (complex) projects is testing.

How to write back Kapacitor alerts into influx

There is a problem: you want to save alerts from Kapacitor back into InfluxDB, but when you use |InfluxDBOut, all you get is original data which had trigger alert with zero information on the alert itself (its level, message, id, etc).

Assorted small tricks for Kapacitor

There are many small things I found and done in kapacitor tasks. They are tiny, but each of them is solving some problem, which caused me a delay, or struggle at some point. Here they are, small tricks.

Reducing size of data in a…

Wading through TICKscript documentation

I begin to work with TICK stack (influx + telegraf + kapacitor). I have some experience with Influx (mostly together with Grafana). Telegraf looks simple (no new ideas, just a config grind).