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: 8036
Title: Suppressing unwanted error messages
Component: inline-snmp
Level: 1
Class: Bug fix
Version: 1.2.5i1
In some cases, the netsnmp library directly outputs error messages
to stdout. This can be disabled by setting the verbose option
of the netsnmp module to 0, which is set to 1 by default. Hopefully
this does not suppress too many helpful error messages.
ID: 8037
Title: Inline-SNMP bulk walk now handles timeout errors like the classic SNMP code
Component: inline-snmp
Level: 1
Class: Bug fix
Version: 1.2.5i1
Previous versions produced error messages like "Empty response to SNMP query for ..."
in case of a timeout when doing a bulk walk with inline SNMP. This was a different
handling to non bulk walk queries and SNMPv1, which resulted in strange error
behavious. This has now been consolidated and fixed. These timeouts are now mostly
suppressed and are only visible when using the <tt>-v</tt> flag with <tt>check_mk</tt>.
ID: 8032
Title: Add information about previous hard state of hosts and services
Component: cmc
Level: 1
Class: Bug fix
Version: 1.2.5i3
This is needed to provide the rule based notifications with information
about the original state of an object, when an alert happens and the
object has more than one check attempt.
ID: 8033
Title: Fix PING check on clusters without services
Component: config
Level: 1
Class: Bug fix
Version: 1.2.5i3
The PING check that is created on clusters that have no other services
always failed with <tt>check_icmp: Failed to resolve -m</tt>. This happened
only some operating systems only (e.g. RedHat 6.5). The reason is probably
in different versions of the <tt>getopt</tt> function. This has been fixed.
ID: 8031
Title: Allow to limit number of hosts and service via config
Component: config
Level: 1
Class: New feature
Version: 1.2.5i1
There are now two new global settings for <tt>main.mk</tt> that allow limiting
the number of monitored hosts and/or services. This option only works when
using the Check_MK Micro Core. Example:
F+:main.mk
cmc_host_limit = 100
cmc_service_limit = 3000
F-:
If you now try to activate a configuration with more than 100 hosts or more
then 3000 services you will run into an error and the old configuration is
being kept. It is also possible to just set a limit on hosts <i>or</i>
services. Setting the according variable to <tt>None</tt> deactivates the
limit. This is the default.
This setting can <b>not</b> be changed via WATO. It can be useful in situations
where you give access to a user or customer via WATO but want to restrict
the amount of objects that he/she can monitor.
ID: 8028
Title: Fix column last_hard_state: show same value as soft state
Component: cmc
Level: 1
Class: Bug fix
Version: 1.2.5i1
The livestatus implementation of the Micro Core did output the current state instead
of the last hard state in the column last_hard_state. This has been fixed.
ID: 8029
Title: New external command for creating log entries
Component: cmc
Level: 1
Class: New feature
Version: 1.2.5i1
The core has now the new external command LOG. This creates entries in
the monitoring history. It is currently being used by the overhauled Check_MK
notification system in order to log the notifications that are actually
be sent out after condideration of notification rules.
ID: 8030
Title: Set default host check interval for non-Smart-PING hosts to 60 seconds
Component: config
Level: 1
Class: Bug fix
Version: 1.2.5i1
The host check interval for hosts when using the Micro Core has been 6 seconds.
This is a good setting when using Smart-PING (which is the default). When you
switch to an alternative command like <tt>check_tcp</tt>, then 6 seconds is
too fast in most situations. So we changed the default interval for all
non-Smart-PING hosts to 60 seconds.
ID: 8027
Title: CMC now allows spaces in the names of performance variables
Component: cmc
Level: 1
Class: Bug fix
Version: 1.2.5i1
This makes the Micro Core compatible to the different variants that
Nagios allows for performance data variables. Now it is allowed to
specify <tt>"foo bar test"=18</tt> or <tt>'foo bar test'=18</tt>
as performance data. This means that the name of the variable
may be quoted with either single or double quotes.