ID: 8045
Title: Do no increase notification number on recovery notifications
Component: cmc
Level: 2
Class: Bug fix
Version: 1.2.5i3
When a notification of the type RECOVERY is being created then the
notification number is not longer increased. This is neccessary.
Otherwise RECOVERY notifications always have at least a number of 2
which garbles possible escalations.
ID: 8044
Title: Fixed different behaviour of inline SNMP and normal SNMP mode which resulted in check exceptions
Component: inline-snmp
Level: 2
Class: Bug fix
Version: 1.2.5i5
Fixed a bug in our inline SNMP bulk walk implementation which resulted in
different behaviour compared to classic SNMP mode. This resulted (at least
in our case) in exceptions during checking.
ID: 8038
Title: Adapted bulkwalk behaviour of snmp command to fix issue with missing OID
Component: inline-snmp
Level: 2
Class: Bug fix
Version: 1.2.5i1
The previous implementation of the bulkwalk in our inline SNMP code was not
working as e.g. the snmpbulkwalk command of net-snmp. The bulkwalk command
asks for an OID via bulkwalk, processes the response and when none of the
responded OIDs matches this OID, the command performs an explicit SNMP GET
on the requested OID to get that single value. This has now been added.
ID: 8035
Title: Inline-SNMP now handles errors in case of SNMP errors like "noSuchName ..."
Component: inline-snmp
Level: 2
Class: Bug fix
Version: 1.2.5i1
Previous versions made SNMP communication fail once a single OID could not be
fetched. This has been fixed to match the behaviour of the classic SNMP code.
ID: 8034
Title: Automatically packages RPM and DEB agents for Linux
Component: agents
Level: 3
Class: New feature
Version: 1.2.5i3
Check_MK now creates RPM and DEB packages for your Linux agents via WATO.
Via rules in the new section <i>Monitoring Agents</i> you can configure
settings and plugins for the agent. The new WATO module <i>Monitoring Agents</i>
allows you to download the RPM or DEB packages of the various configurations.
<b>Note</b>: This feature is not finished yet and still experimental. Most
of the according WATO rules are still missing. There is no documentation
yet. <b>Use at your own risk!</b>.
ID: 8025
Title: Add all custom variables of host, service and contact to notification
Component: cmc
Level: 2
Class: New feature
Version: 1.2.5i1
The CMC now automatically adds all custom variables of hosts, service and
contacts to the notification context. The variable name is prefixed with
the word <tt>HOST</tt>, <tt>SERVICE</tt> or <tt>CUSTOM</tt> and - as its
variable name custom - converted to upper case. So a host variable with
the name <tt>_foobar</tt> will be available as <tt>HOST_FOOBAR</tt> in the
notification context. The names will be prefixed with <tt>NOTIFY_</tt> and put
into the environment of the notification plugin. So at the end the variable
will be available as <tt>NOTIFY_HOST_FOOBAR</tt>, e.g. in a shell script:
F+:mynotify.sh
echo "Foobar: $NOTIFY_HOST_FOOBAR"
F-:
H2:Notes
<ul>
<li>In the configuration files in <tt>main.mk</tt> or below <tt>conf.d</tt>
the variables can be set via <tt>extra_host_conf</tt> or <tt>extra_service_conf</tt>.
You need to have the variable names begin with an underscore. So a variable name of <tt>foobar</tt>
is not allowed. You have to write either <tt>_foobar</tt> or <tt>_FOOBAR</tt>.</li>
<li>When you add contact custom variables via WATO (button <i>Custom Attributes</i>
in the users management</i>) the underscore will <i>automatically</i> be added.</li>
<li>when using Nagios as monitoring core you have to adapt <tt>check_mk_templates.cfg</tt>
whenever you add a new custom variable.</li>
</ul>
ID: 8018
Title: Flapping notifiations for services are no longer sent if switched off
Component: cmc
Level: 2
Class: Bug fix
Version: 1.2.5i1
The users global notification option "Service" - "Start or end of flapping state"
was not processed correctly by the core, so the user received flapping alert
notifications even if this option was disabled.
ID: 8011
Title: Complete German translation of GUI
Component: WATO
Level: 3
Class: New feature
Version: 1.2.5i1
The complete user interface of Multisite and WATO is now available in German language.
Every user can select either English or German as language. In a global setting you
can specify the default language.