Werk #3466: Logwatch pages now work in distributed environment without HTTH reverse proxy

Component User interface
Title Logwatch pages now work in distributed environment without HTTH reverse proxy
Date May 2, 2016
Level Prominent Change
Class New Feature
Compatibility Compatible - no manual interaction needed
Checkmk versions & editions
1.4.0i1
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.4.0i1
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.4.0i1
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.4.0i1
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.4.0i1
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.4.0i1
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.4.0i1
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.4.0i1 Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)

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 mk_logwatch_path=...... Specify the absolute path to the base directory where Check_MK stores the logwatch files. This path always ends with /logwatch.

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.

To the list of all Werks