The current TICK stack requires you to “template” your Kapacitor tasks through Chronograf if you want the alerts to show up in the Chronograf status page (or history). However, Kapacitor tasks generated by Chronograf have messy long names and do therefore not describe what they are actually monitoring (i.e.
My current set of custom tasks have names like:
ram_usage and so on (and for readability sake they are actually formatted in a good way).
What I want to be able to do, is linking custom written Kapacitor tasks to Chronograf. I first tried mimicking the pipeline of a Chronograf generated Kapacitor task with one of my own custom tasks. Then I found out, that there must be some special type of relation between Chronograf’s generated tasks and Kapacitor. I guess Chronograf generated tasks are also stored somehwere inside Chronograf’s BoltDB.
Is there a way to link custom written Kapacitor tasks to Chronograf’s status page and history log?
Btw: If you template the task through Chronograf first and then overwrite the task with a custom TICK script
kapacitor define chronograf-v1-e52857d9-908d-44bf-8c3b-ba39374928d7 cpu_usage.tick, the alert rule in Chronograf gets renamed to the id and becomes unusable through the web interface (expected, but not the name change).