ID: 8177
Title: Acknowledgement notifications are now suppressed when notifications are disabled
Component: cmc
Level: 1
Class: Bug fix
Version: 1.2.7i1
Previous versions sent out notifications when acknowledging problems, even when the
notifications were disabled for an object, for example by disabling all notifications
globally.
ID: 8178
Title: Processing SNMP values unmodified to checks (might break some SNMP checks)
Component: inline-snmp
Level: 1
Class: Bug fix
Version: 1.2.7i1
Previous versions of the Inline-SNMP code were replacing and
stripping different characters from the values reported by
SNMP. This has been done to be compatible to the classic SNMP
behaviour and to fix different cases of strange characters in
the SNMP data.
We decided to clean this totally up that the single checks get
the real unmodified SNMP values which then need to be handled
by the SNMP checks individually.
ID: 8171
Title: Agents are not baked automatically anymore
Component: agents
Level: 1
Class: Bug fix
Version: 1.2.7i1
Previously the agent bakery was baking all needed agents during each reload/restart etc.
by default. This has been disabled now. You might re-enable it by setting the global
configuration option <i>Automatically create monitoring agents</i> again if you really
need it.
For all other users: When you open up the WATO Monitoring Agents page, there is a new
button <i>Bake Agents</i> now, which you can click to let the bakery update all needed
agents. Each WATO change or Check_MK update makes the button be highlighted to let you
know there might be changes affecting the baked agents. Once clicked on the button,
all needed agents are baked and the highlighting is removed.
ID: 8166
Title: Limit SNMP OID Ranges now supporting ranges from the end of the table
Component: inline-snmp
Level: 1
Class: New feature
Version: 1.2.7i1
When performing walks on an OID during checking, Check_MK fetches all sub OIDs regardless
whether these values are needed or not. For example, if you monitor a single
network interface of a switch with hundrets of ports, the check will fetch the
information for all the interfaces, while only one is used.
The OID range limiting can be used to reduce the amount of fetched OIDs, but please note,
this is only useful for special cases like the example above and only used when you
perform bulkwalks.
Previous versions did only support ranges starting from the start of an SNMP table. With
this change it is also possible to specify OID ranges of N entries from the end of the
SNMP table.
When such an "end limit" is configured, the first column of a table is fetched in total,
while only keeping the requested OIDs but also saving the needed indexes of this table.
For all additional columns of this table only the requested OIDs are fetched.