ID: 3585
Title: Implemented API for exporting the full host inventory
Component: HW/SW-Inventory
Level: 2
Class: New Feature
Version: 1.2.9i1
The HW/SW inventory data can now be exported using a webservice. This webservice
outputs the raw structured inventory data of a host.
The URL to this webservice is <tt>http://[MONITORING-SERVER]/[SITE]/check_mk/host_inv_api.py?host=[HOST]&outp…</tt>.
You choose one of these output formats: <tt>json</tt>, <tt>xml</tt>, <tt>python</tt>.
The data provided by this webservice looks as follows:
C+:
{
"result": {
"hardware": {
"memory": {
"total_ram_usable": 16697331712,
"total_swap": 17049841664,
"total_vmalloc": 35184372087808
}
},
"networking": {
"hostname": "Klappspaten"
}
},
"result_code": 0
}
C-:
The data below the key <tt>result</tt> is the HW/SW inventory data.
In case an error occurs during processing of the request, for example a host can not be found,
the <tt>result_code</tt> is set to 1 and the result contains the error message:
C+:
{"result": "Found no inventory data for this host.", "result_code": 1}
C+:
ID: 3575
Title: User logins can now be limited to single session at a time
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.9i1
Normally a user can login to the GUI from unlimited number of clients at
the same time. If you want to enforce your users to be able to login only once
(from one client which means device and browser), you can enable this option.
When the user logs out or is inactive for the configured amount of time, the
session is invalidated automatically and the user has to log in again from the
current or another device.
ID: 3134
Title: windows agent: fixed bug where the last message of an eventlog was always re-read
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.9i1
ID: 3472
Title: Service list of a host: Move section of vanished services to top of the page
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.9i1
The vanished services usually indicate a problem or invalid service configuration and
should be shown rather on the top of the page then after the long list of services.
ID: 3471
Title: Repair ignoring discovery errors when bogus %s is contained in service description
Component: Core & Setup
Level: 2
Class: Bug Fix
Version: 1.2.9i1
This problem often appeard after an upgrade from 1.2.6 to 1.2.8 on monitored ESX servers.
ID: 3572
Title: Added user login session idle timeout
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.9i1
It is now possible to configure a login session idle timeout globally or for each user
individually. When a user logs in and leaves the GUI open without interacting with it,
Check_MK does not invalidate the users login session. The login is valid until the user
closes the window or logs out. With the new option enabled, it is possible to configure
a maximum allowed idle time after which each user has to renew the login.
ID: 3469
Title: Show type of rule match of a rule (first, per-parameter, all) in WATO
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.9i1
This additional information makes it clearer to the user whether a just the
first matching rule defines the parameter, or further matching rules can
have influence, too.
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.