ID: 11847
Title: Windows agent may get winperf data without spawning new process
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.1.0i1
Since this release it is possible to generate winperf data without spawning a
new process.
To enable this feature you should edit check_mk.user.yml file and set in the
section <tt>winperf</tt> the key <tt>fork</tt> in <tt>no</tt>
This setting is primary intended for problem solving and should be used carefully,
because Windows OS may leak handles when winperf API is used.
ID: 11846
Title: Windows agent supports logging for winperf
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.1.0i1
Since this release it is possible to log messages from winperf.
To get log you have to edit check_mk.user.yml file and set in the
section <tt>winperf</tt> the key <tt>trace</tt> to <tt>yes</tt>.
Restart of the service is mandatory. The log will be provided in the file
<log/winperf.log</tt>
ID: 12022
Title: New inventory plugins for Fortinet systems
Component: HW/SW Inventory
Level: 1
Class: New feature
Version: 2.1.0i1
This werk introduces four new inventory plugins plugins. They all
gather their data via SNMP.
<ul>
<li><tt>fortisandbox_system</tt>: Inventorizes the operating system
version of Fortinet FortiSandbox systems.</li>
<li><tt>fortisandbox_software</tt>: Inventorizes the versions of the
software of Fortinet FortiSandbox systems. Examples include the version
of the tracer engine and the sniffer.</li>
<li><tt>fortiauthenticator_system</tt>: Inventorizes the model and the
serial number of Fortinet FortiAuthenticator systems.</li>
<li><tt>fortigate_ha</tt>: Inventorizes the HighAvailability mode,
priority, schedule, group id and group name of Fortinet FortiGate
Systems.</li>
</ul>
ID: 11725
Title: storcli_pdisks, storcli_vdisks: Support multiple RAID controllers per system
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
When monitoring LSI MegaRAID controller via StorCLI, now all drives
of all RAID controllers of a system do get discovered and added as a service.
Previously, the discovery did only find the first controller of a system.
To differentiate between the controllers, the item name is prepended by "Cn.",
where n is the number of the controller.<br>
E.g.:
<ul>
<li><tt>RAID Virtual Drive 0/0</tt> would become <tt>RAID Virtual Drive C0.0/0</tt>
for controller 0</li>
<li><tt>RAID PDisk EID:Slot-Device 13:9-19</tt> would become
<tt>RAID PDisk EID:Slot-Device C1.13:9-19</tt> for controller 1</tt></li>
</ul>
As this Werk changes the item name, this is an incompatible change and will
require re-discovering the services.
ID: 11705
Title: mk_postgres: compatibility for python2.6
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
The mk_postgres agent plugin crashed and did not produce any agent sections if run with python2.6.
The following error message occured:
"ImportError: No module named argparse"
In order to run this plugin with python2.6 you need to redeploy the agent plugin.
ID: 12021
Title: Windows agent plugin for MySQL (<tt>mk_mysql</tt>): support MariaDB
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.1.0i1
The Windows agent plugin <tt>mk_mysql</tt> for monitoring MySQL databases
now supports MariaDB. If you want to use this feature, you have to update
the plugin on the corresponding hosts. No other configuration steps are
necessary. You will then discover additional services on these hosts.
Users who simply want to continue monitoring their already existing MySQL
DBs do not have to take any steps.
ID: 11352
Title: iptables: Keep ACK after update/restart
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
In case a changed iptable config - which results in {CRIT} - was acknowledged, the ACK vanished after a <tt>omd update<\tt> or <tt>omd restart<\tt>.
The reason therfore is that the check will go to state {OK} for one checkinterval after the update/restart and then become {CRIT} again.
The intermediate state is now {PENDING}, which is actually more precise.