ID: 3129
Title: new view and datasource containing the results of the last periodic discovery check
Component: Multisite
Level: 1
Class: New Feature
Version: 1.2.9i1
With this change, the results of the "Check_MK Discovery"-check can now be presented in their own
searchable, sortable and filterable view.
In addition the check was extended to also include information about services disabled through a
rule. This gives users with no access to wato the chance to see that those checks were intentionally
suppressed.
ID: 3527
Title: WATO service discovery: fixed warning with locked hosts
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.2.9i1
Starting a single or a bulk discovery on locked hosts no longer raises a warning
when WATO tries to modify an attribute concerning a failed service discovery.
ID: 3431
Title: netextreme_cpu_util: new check which monitors the CPU utilization of a Extreme Networks Switch which supports the EXTREME-MIB
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.9i1
ID: 3466
Title: Logwatch pages now work in distributed environment without HTTH reverse proxy
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.9i1
The web pages for viewing and acknowledging files from logwatch checks now no longer
need a HTTP reverse proxy setup but simply work. The use Livestatus - just like the
other status data. This means that in the Enterprise Edition you can now drop the
reverse proxying totally. In the Raw Edition you still need it for the performance
graphs from PNP4Nagios.
In a manual setup you need to tell the Livestatus Nagios-Module where it finds
the logwatch files with the option <tt>mk_logwatch_path=.....</tt>. Specify the
absolute path to the base directory where Check_MK stores the logwatch files.
This path always ends with <tt>/logwatch</tt>.
Note: You need to update Livestatus / Check_MK on all remote sites. If you just
update the central site then the logwatch GUI will stop working.