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.
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).
|InfluxDBOut
It’s a simple problem: we want to have an instance which ignores all user input.
The problem can be split into two parts:
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.