ID: 8158
Title: New table layout for reporting
Component: Reporting & Availability
Level: 2
Class: New feature
Version: 1.2.7i1
Tables in the reporting are new per default painted in alternative
background shadings for odd and even rows. This is similar to the styling
on the screen. This is just a new default. You can change this back to the
previous behaviour in the global settings, if you like.
ID: 8159
Title: Reporting now can show inline timeline and legends of availability views
Component: Reporting & Availability
Level: 2
Class: New feature
Version: 1.2.7i1
ID: 8156
Title: New option for forcing a history logfile rotation based on its size
Component: cmc
Level: 2
Class: New feature
Version: 1.2.7i1
The Check_MK Micro Core now forces a rotation of the history logfile if its
size exceeds a configure limit. This avoids too large logfiles in situations
with a high logging volume. Large logfile make problems in certain Livestatus
queries. The default is now to force a rotation at a size of 20 MB. You can
configure this limit within the bounds of 10 KB and 1 GB.
ID: 8134
Title: Avoiding falsely reported packet loss by PING service
Component: cmc
Level: 2
Class: Bug fix
Version: 1.2.7i1
The PING services, which is being created for hosts which are not monitored
via SNMP or agent, sometimes reported packet loss of x% while the host check
of the microcore reported that the host is reachable without problems.
This issue was caused by the way the Micro Core icmpsender generated the ICMP
packages. These packages seemed to confuse the check_icmp plugin which is
executed by the PING service.
ID: 8153
Title: Fix notification delay if delay is greater than 2147 seconds
Component: cmc
Level: 2
Class: Bug fix
Version: 1.2.7i1
If you configured a notification delay of more than 2147 seconds (approx 35
minutes, precisely 2^31 micro seconds) then due to an internal range overflow
the actual delay would be somewhere between -2147 and +2147 seconds. So in
some cases the delay was just too short, in other it was negative and that
way totally ineffective. This has been fixed.
ID: 8129
Title: Create log entries for acknowledgements in monitoring log
Component: cmc
Level: 2
Class: New feature
Version: 1.2.7i1
When an acknowledgement is being created or removed or an acknowledgement
ends because of a state change or expires then now an entry in made in
the monitoring log. Example:
F+:var/check_mk/core/history
[1420818703] HOST ACKNOWLEDGE ALERT: xyserver12;STARTED;omdadmin;Some comment...
F-:
These entries are visiable via Multisite and via Livestatus. This only works
with the CMC.
ID: 8125
Title: Fix invalid number of Alert statistics view when exported as PDF
Component: Reporting & Availability
Level: 2
Class: Bug fix
Version: 1.2.7i1
The reason was that internally a limit on the number of raw lines from
the log query was imposed. This has been fixed.