We use cookies to ensure that we give you the best experience on our website.  Visit our Privacy Policy to learn more. If you continue to use this site, we will assume that you are okay with it.

Your choices regarding cookies on this site.
Your preferences have been updated.
In order for the changes to take effect completely please clear your browser cookies and cache. Then reload the page.

Werk #6580: Optionally send parts of the service state to Graphite/InfluxDB

TitleOptionally send parts of the service state to Graphite/InfluxDB
Date2018-09-17 09:58:22
Checkmk EditionCheckmk Enterprise Edition (CEE)
Checkmk Version1.6.0b1
LevelTrivial Change
ClassNew Feature
CompatibilityCompatible - no manual interaction needed

In addition to the existing options

  • Value
  • Unity of measurement
  • Warning threshold
  • Critical threshold
  • Minimum
  • Maximum

three new options have been added to the rule "Send metrics to Graphite/InfluxDB":

  • State
  • Scheduled downtime depth
  • Acknowledged

When these options are activated, the corresponding parts of the service state are sent via the Graphite/InfluxDB interface, too. Note that these value are sent once per service, while the already existing options are per metric. To avoid a clash with existing metric names, the three new metric names all start with an equals sign, because due to the Nagios metric syntax, no metric can start with that character. In detail:

  • =state: the current state of the service, 0/1/2/3 for OK/WARN/CRIT/UNKNOWN
  • =scheduled_downtime_depth: the number of downtimes the service is currently in
  • =acknowledged: whether the current problem, if any, has been acknowledged (0/1)

As an example, here the data sent to Graphite/InfluxDB for the "CPU load" service on host "myhost" when all options are enabled:

myhost.CPU_load.=state 0 1537170248
myhost.CPU_load.=scheduled_downtime_depth 0 1537170248
myhost.CPU_load.=acknowledged 0 1537170248
myhost.CPU_load.load1 1.05 1537170248
myhost.CPU_load.load1.warn 40 1537170248
myhost.CPU_load.load1.crit 80 1537170248
myhost.CPU_load.load1.min 0 1537170248
myhost.CPU_load.load1.max 8 1537170248
myhost.CPU_load.load5 0.75 1537170248
myhost.CPU_load.load5.warn 40 1537170248
myhost.CPU_load.load5.crit 80 1537170248
myhost.CPU_load.load5.min 0 1537170248
myhost.CPU_load.load5.max 8 1537170248
myhost.CPU_load.load15 0.71 1537170248
myhost.CPU_load.load15.warn 40 1537170248
myhost.CPU_load.load15.crit 80 1537170248
myhost.CPU_load.load15.min 0 1537170248
myhost.CPU_load.load15.max 8 1537170248