ID: 0902
Title: event console view: fixed exception on rendering host tags for unknown hosts
Component: Event Console
Level: 1
Class: Bug Fix
Version: 1.2.5i3
The event console was unable to render specific host tag columns
when the monitoring system had no knowledge of the host in question.
ID: 0894
Title: wagner_titanus_topsense.smoke: New check for Smoke Detectors in Wagner Titanus Top Sens devices
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.5i3
ID: 0887
Title: Add new column painter "Host Notifications Enabled"
Component: Multisite
Level: 1
Class: New Feature
Version: 1.2.5i3
This new column has been added to the view <i>Host problems for NagStaMon</i> and is used
for providing that information to NagStaMon. Note: You will need to update NagStaMon in order
to use this new information.
ID: 0893
Title: wagner_titanus_topsense.alarm: New check for Alarms Triggered on Wagner Titanus Top Sens devices
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.5i3
ID: 0892
Title: wagner_titanus_topsense: new info check and overall status check for Wagner Titanus Top Sens devices
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.5i3
ID: 0832
Title: solaris_mem: fixed invalid calculation of total swap
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.5i3
Solaris systems which reported the memory information like<br>
Memory: 10G phys mem, 1905M free mem, 8002M total swap, 8002M free swap<br>
got incorrect total swap values in the check.
ID: 0831
Title: table statehist: no longer crashes on TIMEPERIOD TRANSITION entries with an invalid syntax
Component: Livestatus
Level: 1
Class: Bug Fix
Version: 1.2.5i3
The livestatus table could crash incomplete TIMEPERIOD TRANSITION logentries which where
caused by a maximum line length. <br><br>
<tt>Working:</tt><br>
[1391727600] TIMEPERIOD TRANSITION: good_transition;0;1<br>
<tt>Caused crash:</tt><br>
[1391727600] TIMEPERIOD TRANSITION: this_timeperiod_transition_name_is_way_too_lo
ID: 0885
Title: New option for writing all messages into a syslog-like logfile
Component: Event Console
Level: 1
Class: New Feature
Version: 1.2.5i3
The new Event Console global option <i>Syslog-like message logging</i> will enable
logging of <b>all</b> incoming events into logfiles that have syslog format.
These files will be stored below <tt>var/check_mk/mkeventd/messages</tt> and will
be named with the same scheme as the history logfiles. They will adopt the same
rotation principle as the history files.
If you are using Check_MK in a non-OMD environment and enable this option then
please make sure that you have some logrotate configuration or similar for
deleting outdated files.
If you are using OMD then consider enabling the global <i>Diskspace Cleanup</i>.