Checkmk werks level1 February 2014

checkmk-werks-lvl1@lists.checkmk.com

6 participants
58 discussions

Check_MK Werk 0562: esx_vsphere_vm.guest_tools: new check to monitor guest tools status

by Andreas Boesl

ID: 0562 Title: esx_vsphere_vm.guest_tools: new check to monitor guest tools status Component: Checks & Agents Level: 1 Class: New Feature Version: 1.2.5i1 This check allows to monitor if the guestTools version of the VM is up-to-date. Possible values and states: <ul> <li>"VMware Tools is installed, and the version is current" - State OK)</li> <li>"VMware Tools is installed, but the version is not current" - State WARN)</li> <li>"VMware Tools has never been installed" - State CRIT)</li> <li>"VMware Tools is installed, but it is not managed by VMWare" - State WARN)</li> </ul> The resulting state of each value can also be modified by the WATO rule <tt>Virtual machine guest tools status</tt>

10 years, 2 months

Check_MK Werk 0704: windows_os_bonding: new check for bonding interfaces on windows

by Bernd Stroessenreuther

ID: 0704 Title: windows_os_bonding: new check for bonding interfaces on windows Component: Checks & Agents Level: 1 Class: New Feature Version: 1.2.5i1 new check for bonding interfaces on windows configured on operating system level

10 years, 2 months

Check_MK Werk 0561: quicksearch: now able to search with multiple filters

by Andreas Boesl

ID: 0561 Title: quicksearch: now able to search with multiple filters Component: Multisite Level: 2 Class: New Feature Version: 1.2.5i1 The classical quicksearch allowed certain filter prefixes, which specified the item to look for. For example: <ul> <li>h: {search_text} # Find hostname, host_address or hostalias</li> <li>s: {search_text} # Find service</li> <li>hg: {search_text} # Find hostgroup</li> <li>sg: {search_text} # Find servicegroup</li> </ul> The new search feature enhances the service search. You can now combine these filters to thin out the results. For example: C+: s: mem h: localhost C-: This will search for all services containing <tt>mem</tt> on the localhost. Furthermore you can combine these filters. C+: s: mem s: cpu h: localhost h: switch-intern C-: This will search for all services containing <tt>mem</tt> OR <tt>cpu</tt> on the hosts <tt>localhost</tt> OR <tt>switch-intern</tt>. The search algorhytm is as follow: <ul> <li>Same filters are combined with <tt>OR</tt></li> <li>Different filters are combined with <tt>AND</tt></li> </ul> The query <tt>h: localhost s: mem s: cpu h:switch-intern</tt> actually results in the following livestatus query: C+: GET services Cache: reload Columns: service_description host_name hostgroups servicegroups Filter: host_name ~~ switch-intern Filter: host_name ~~ localhost Or: 2 Filter: service_description ~~ cpu Filter: service_description ~~ mem Or: 2 And: 2 Limit: 80 C-: You can also add the <tt>hg:</tt> and <tt>sg:</tt> filters to the query. Note: Right now, this multisearch filter only works if at least one of the filters is a service (<tt>s:</tt>).

10 years, 2 months

Check_MK Werk 0137: Fixed printer_pages

by Bastian Kuhn

ID: 0137 Title: Fixed printer_pages Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.2.5i1 The old version used a not exsisting OID who leads to a error when using inline snmp.

10 years, 2 months

Check_MK Werk 0720: Fix timeperiod computation with CMC and flexible notifications

by Mathias Kettner

ID: 0720 Title: Fix timeperiod computation with CMC and flexible notifications Component: Notifications Level: 1 Class: Bug Fix Version: 1.2.5i1 If you used the Check_MK Micro Core and flexible notifications and used the state of a timeperiod as a notification condition then this condition would fail. Timeperiods would be computed just once after every configuration restart. This has been fixed now.

10 years, 2 months

Check_MK Werk 0703: brocade_mlx: omit inventory of cpu and memory on more states

by Bernd Stroessenreuther

ID: 0703 Title: brocade_mlx: omit inventory of cpu and memory on more states Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.2.5i1 If for a module the status is "Blocked for full height card" it is omitted during inventory for CPU and Memory checks, because there is no sense in checking them.

10 years, 2 months

Check_MK Werk 0586: rmon_stats: new snmp check to gather network traffic statistics on RMON enabled network interfaces

by Götz Golla

ID: 0586 Title: rmon_stats: new snmp check to gather network traffic statistics on RMON enabled network interfaces Component: Checks & Agents Level: 2 Class: New Feature Version: 1.2.5i1

10 years, 2 months

Check_MK Werk 0702: Rule for checking agents for wanted version

by Bernd Stroessenreuther

ID: 0702 Title: Rule for checking agents for wanted version Component: Checks & Agents Level: 2 Class: New Feature Version: 1.2.5i1 You can now define a rule (in WATO it is called "Check for correct version of Check_MK agent") to check if the Check_MK Agents have one wanted version. You may give a version number manually or take the version number of the monitoring site as a reference. If the Agent has a different version, the Check_MK service on this host returns a WARN status, or what ever status you did define in the rule "Status of the Check_MK service".

10 years, 2 months

Check_MK Werk 0585: check_mk_agent.linux: more efficient handling of cups printer queues

by Götz Golla

ID: 0585 Title: check_mk_agent.linux: more efficient handling of cups printer queues Component: Checks & Agents Level: 2 Class: Bug Fix Version: 1.2.5i1 The handling of printer queues has been made more efficient for cases when many printer queues (>> 100) are to be monitored. This part of the agent is now a factor of 10-20 faster !

10 years, 2 months

Check_MK Werk 0584: agent_vsphere: special agent now handles non-standard https port correctly

by Götz Golla

ID: 0584 Title: agent_vsphere: special agent now handles non-standard https port correctly Component: Checks & Agents Level: 2 Class: Bug Fix Version: 1.2.5i1 The special agent vsphere to monitor ESX-Servers and vcenters can be configured to use a non-standard port for the vsphere https connection. This might be useful for firewall traversals etc. The configuration was possible before this fix in WATO, but it was never used, so that the default https port 443 was always used. With this fix the port which is actually configured in WATO will be used for https. If a vcenter is queried including the check_mk_agent, the check_mk_agent will still be queried on the standard check_mk_agent port 6556, whereas the https connection port will be the one configured in WATO.

10 years, 2 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 February 2014