ID: 6594
Title: Status data is transferred in distributed setups
Component: HW/SW Inventory
Level: 1
Class: Bug fix
Version: 1.6.0i1
Werk 5605 introduced the integration of status data
into the HW/SW Inventory tree.
This worked only in single sites but not in distributed
setups.
ID: 6563
Title: Fixed displaying of joined perf-o-meter columns
Component: Reporting & Availability
Level: 1
Class: Bug fix
Version: 1.6.0i1
When adding views containing Perf-O-Meter painters of joined services the
Perf-o-meters were not displayed. Instead an empty cell was rendered.
ID: 6580
Title: Optionally send parts of the service state to Graphite/InfluxDB
Component: cmc
Level: 1
Class: New feature
Version: 1.6.0i1
In addition to the existing options
LI:Value
LI:Unity of measurement
LI:Warning threshold
LI:Critical threshold
LI:Minimum
LI:Maximum
three new options have been added to the rule "Send metrics to Graphite/InfluxDB":
LI:State
LI:Scheduled downtime depth
LI: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:
LI:=state: the current state of the service, 0/1/2/3 for OK/WARN/CRIT/UNKNOWN
LI:=scheduled_downtime_depth: the number of downtimes the service is currently in
LI:=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:
C+:
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
C-:
CMK-898
ID: 6617
Title: Check_MK is now available as Docker container
Component: Site Management
Level: 2
Class: New feature
Version: 1.6.0i1
Besides the traditional operating system packages we are now providing Check_MK
as Docker container image to improve the support of using Check_MK in containerized
environments.
For the moment the Docker images are published together with the other Check_MK
packages on the versions download pages for manual download.
Future releases of the Check_MK Raw Edition will be published on Docker Hub
(https://hub.docker.com/r/checkmk/check-mk-raw/). On this page you can already
find some information on how to use the images. These instructions apply to all
Check_MK Editions.
The Enterprise and Managed Services Edition containers will also be available through
a docker image repository in the future. For the moment you will have to download and
import the images manually using <tt>docker load</tt>.
ID: 6616
Title: Add --no-tmpfs option to "omd create"
Component: Site Management
Level: 1
Class: New feature
Version: 1.6.0i1
It's now possible to disable the temporary filesystem usage during
site creation.
ID: 6462
Title: aix_hacmp_resources: Now configurable via WATO
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0i1
Previously, the check would expect a resource to be online
on the first node. It can now be configured to accept
the resource to be online on any node.
ID: 6503
Title: Fixed error handling for duplicate EC rule IDs.
Component: WATO
Level: 1
Class: Bug fix
Version: 1.6.0i1
Trying to insert an EC rule with an already existing ID resulted in a GUI
crash, this has been fixed.
ID: 6564
Title: Fixed incorrect rate computation affecting various checks in some cases
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
All previous 1.5 releases used a partially broken counter / rate computation in
various checks in specific situations, e.g. inotify checks. Not all check
results were computed wrong, only the ones based on counter / rate
computations.
When a single check monitors several services on a host, only the first of
these services was affected by this issue.
ID: 6465
Title: cisco_stack: New check to monitor the status of Cisco stack switches
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0i1