ID: 11344
Title: Discover correct galera setups
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.0.0i1
The galera subchecks discovered services in cases galera was not configured. This was fixed with this werk.
Furthermore a crash regarding the discovered parameters is fixed.
ID: 11367
Title: Enforcing 32-bit interface checks is now done by disabling if64 SNMP section
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.0.0i1
This werk is only relevant for users who are currently using the ruleset "Hosts
forced to use 'if' instead of 'if64'".
The rule "Include or exclude SNMP sections", which allows users to disable individual
SNMP sections, will now replace the more specific rule for enforcing the usage of
the 32- …
[View More]instead of the 64-bit interface check ("Hosts forced to use 'if' instead
of 'if64'"). As of this werk, the latter rule is deprecated. To make Checkmk fall
back to the 32-bit interface check, use "Include or exclude SNMP sections" to disable
the corresponding 64-bit section (mostly <tt>if64</tt>).
This werk is incompatible only for users who actually activated the rule "Hosts
forced to use 'if' instead of 'if64'". As described above, such users have
to deactivate the section <tt>if64</tt>, otherwise, upon re-discovery, Checkmk
will start to use the check plugin <tt>if64</tt> instead of <tt>if</tt>. Note
that besides the check plugin <tt>if64</tt>, the rule "Hosts forced to use 'if'
instead of 'if64'" could also be used to make Checkmk use <tt>if</tt> instead of
<tt>if_brocade</tt> and <tt>if_lancom</tt>. This option is still available,
however, in these two particular cases, users will have to deactivate both the
sections <tt>if_brocade</tt>/<tt>if_lancom</tt> and <tt>if64</tt>. If only the
former were deactivated, Checkmk would fall back to <tt>if64</tt>.
[View Less]
ID: 11337
Title: job: addition of job monitoring to AIX agent
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.0.0i1
This change introduces the job monitoring functionality to the
AIX agent. The behaviour is similar to the job monitoring process
of the Solaris and Linux agent. The resulting services contain time
related information of the jobs.
ID: 11368
Title: netapp_api_luns: Report correct total size
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.0.0i1
The check plugin <tt>netapp_api_luns</tt>, which monitors the usage of LUNs of
Netapp filers, can be configured to not apply any levels to the used storage and
only report the total size of the LUN instead. The size report by the check
plugin in this particular case was wrong by a factor of 1024^2, which is fixed
by this werk.
ID: 11394
Title: Add option to filter views and dashboards by multiple WATO folders
Component: WATO
Level: 1
Class: New feature
Version: 2.0.0i1
A new filter "Multiple WATO Folders" is implemented to allow the user to
select a list of WATO Folders. Using this filter in combination with the
existing "WATO folder" filter may result in unexpected results, thus make
sure to only enable one of these filters per view.
ID: 11208
Title: check_mailboxes: Handle invalid mailbox names
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.0.0i1
A space character in a mailbox name provided via {--mailbox=<NAME>}, e.g. "My Inbox"
would lead to a known exception:
imaplib.IMAP4.error: SELECT command error: BAD [b"parse error: wrong character; expected '(' but got 'I'"]
see https://bugs.python.org/issue13940
This fix quotes mailbox names and thus fixes the …
[View More]described behaviour.
Also, provided mailbox names which do not exist on the server would have been ignored silently. This
fix will render the check UNKNOWN in case any non-existent names are encountered.
[View Less]
ID: 11481
Title: LDAP: Fix AttributeError if attribute "Disable Notifications" is used
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.0.0i1
If you used the option "LDAP attribute to sync" for "Disable Notifications" in
a LDAP connection, the Users page crashes with "AttributeError ('unicode'
object has no attribute 'get')".
The reason is, that the attribute from the LDAP sync is a boolean, that returns
"True" or "FALSE" in unicode.
>From now on, …
[View More]the GUI can handle this kind of format.
[View Less]
ID: 11115
Title: agent_bi: Filter by groups
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Filtering aggregations by groups using the datasource program rule
in the WATO had not been working.
ID: 11270
Title: oracle_instance: Fix missing uptime column if status data inventory is enabled
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
If {{Status data inventory}} is enabled via the rule {{Do hardware/software inventory}}
then {{HW/SW inventory data}} and {{status data}} are inventorized and merged in the
view {{Inventory of HOST}}. To make this work properly we have to identify the
rows in both trees. Previously we only used …
[View More]the {{SID}} column. In newer
{{Oracle}} agent outputs there may be several rows with the same {{SID}} but
different {{process names}}. Thus we add the {{process name}} column and use
it as an additional key for the identifier such that both trees can display the full
information of each output line.
[View Less]