Kapacitor measurements and fields
Kapacitor exposes internal performance through the
Use the Telegraf
kapacitor plugins to capture these metrics and store them in InfluxDB.
Enable the Kapacitor input plugin in your Telegraf configuration file:
# ... [[inputs.kapacitor]] ## Multiple URLs from which to read Kapacitor-formatted JSON ## Default is "http://localhost:9092/kapacitor/v1/debug/vars". urls = [ "http://localhost:9092/kapacitor/v1/debug/vars" ] # ...
Visualize Kapacitor metrics
Use the Kapacitor Monitor dashboard to visualize Kapacitor metrics.
Kapacitor measurements & fields
Kapacitor exposes the following measurements and fields through the
The number of enabled Kapacitor tasks.
The number of Kapacitor/InfluxDB subscriptions.
The total number of Kapacitor tasks.
kapacitor_edges measurement stores fields with information related to
in Kapacitor TICKscripts.
The number of messages collected by TICKscript edges.
The number of messages emitted by TICKscript edges.
kapacitor_ingress measurement stores fields with information related to data
coming into Kapacitor.
The number of points received by Kapacitor.
kapacitor_load measurement stores fields with information related to the
Kapacitor Load Directory service.
The number of errors reported from the load directory service.
kapacitor_memstats measurement stores fields related to Kapacitor memory usage.
The number of bytes of memory allocated by Kapacitor that are still in use.
The number of bytes of memory used by the profiling bucket hash table.
The number of heap objects freed.
The number of bytes of memory used for garbage collection system metadata.
The fraction of Kapacitor’s available CPU time used by garbage collection since Kapacitor started.
The number of reachable and unreachable heap objects garbage collection has not freed.
The number of heap bytes waiting to be used.
The number of heap bytes in use.
The number of allocated objects.
The number of heap bytes released to the operating system.
The number of heap bytes obtained from
The nanosecond epoch time of the last garbage collection.
The total number of pointer lookups.
The total number of mallocs.
The number of bytes in use by mcache structures.
The number of bytes used for mcache structures obtained from
The number of bytes in use by mspan structures.
The number of bytes used for mspan structures obtained from
The nanosecond epoch time of the next garbage collection.
The number of completed garbage collection cycles.
The number of bytes used for other system allocations.
The total number of nanoseconds spent in garbage collection “stop-the-world” pauses since Kapacitor started.
The number of bytes in use by the stack allocator.
The number of bytes obtained from
system for stack allocator.
The number of bytes of memory obtained from
The total number of bytes allocated, even if freed.
kapacitor_nodes measurement stores fields related to events that occur in
The total number of alerts inhibited by TICKscripts.
The total number of alerts triggered by TICKscripts.
The average execution time of TICKscripts in nanoseconds.
The number of critical (
crit) alerts triggered by TICKscripts.
The number of errors caused caused by TICKscripts.
The number of info (
info) alerts triggered by TICKscripts.
The number of ok (
ok) alerts triggered by TICKscripts.
The number of points written to InfluxDB or back to Kapacitor.
The number of warning (
warn) alerts triggered by TICKscripts.
The total number of unique series processed.
The number of errors that occurred when writing to InfluxDB or other write endpoints.
kapacitor_topics measurement stores fields related to
The number of events collected by Kapacitor topics.
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for and this documentation. To find support, use the following resources:
InfluxDB Cloud customers can contact InfluxData Support.