Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15912 discussions

Check_MK Werk 2435: New graphing system: fixed broken graphs for iSCSI checks

by Andreas Boesl

ID: 2435 Title: New graphing system: fixed broken graphs for iSCSI checks Component: Multisite Level: 1 Class: Bug Fix Version: 1.2.7i4 The graph metrics for iSCSI contained a typo. This has been fixed.

8 years, 11 months

Check_MK Werk 2660: fixed windows agent using the wrong working directory

by Sebastian Herbord

ID: 2660 Title: fixed windows agent using the wrong working directory Component: Checks & Agents Level: 2 Class: Bug Fix Version: 1.2.7i4 The windows agent in the recent releases, when started as a service fell back to using the current working directory when started as a service. For a service this is c:/windows/system32

8 years, 11 months

Check_MK Werk 2680: LDAP: Fixed exception when syncing groups using configurations from previous versions

by Lars Michelsen

ID: 2680 Title: LDAP: Fixed exception when syncing groups using configurations from previous versions Component: Multisite Level: 1 Class: Bug Fix Version: 1.2.7i3 This fixes the exception "TypeError: 'LDAPUserConnector' object has not attribute '__getitem__'.

8 years, 11 months

Check_MK Werk 2695: hp_msa_disk, hp_msa_volume: these checks now report more information about disks and volumes of a HP MSA 2040 Storage System

by Simon Betz

ID: 2695 Title: hp_msa_disk, hp_msa_volume: these checks now report more information about disks and volumes of a HP MSA 2040 Storage System Component: Checks & Agents Level: 1 Class: New Feature Version: 1.2.7i3

8 years, 11 months

Check_MK Werk 2659: Added IPv6 support to the windows agent

by Sebastian Herbord

ID: 2659 Title: Added IPv6 support to the windows agent Component: Checks & Agents Level: 2 Class: New Feature Version: 1.2.7i3 added support for connecting to the windows agent via IPv6. This support is active by default and can be disabled via configuration file.

8 years, 11 months

Check_MK Werk 2694: cmctc_lcp: this check monitors now the device levels

by Simon Betz

ID: 2694 Title: cmctc_lcp: this check monitors now the device levels Component: Checks & Agents Level: 1 Class: New Feature Version: 1.2.7i3

8 years, 11 months

Check_MK Werk 2652: jolokia_metrics: better handling of situation where agent does not respond

by Mathias Kettner

ID: 2652 Title: jolokia_metrics: better handling of situation where agent does not respond Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.2.7i3 In case the Jolokia agent cannot be queried the Check_MK services does not any longer complain about missing agent sections. Instead on the main service of the instance goes CRIT and all other services will be skipped and become stale. This avoids bogus notifcations.

8 years, 11 months

Check_MK Werk 2434: NetApp monitoring: Cluster-Mode is now supported, changes in existing 7Mode checks

by Andreas Boesl

ID: 2434 Title: NetApp monitoring: Cluster-Mode is now supported, changes in existing 7Mode checks Component: Checks & Agents Level: 2 Class: New Feature Version: 1.2.7i3 This update enables to monitor NetApp Filers running in Cluster-Mode. The new <i>agent_netapp</i> is able to automatically detect whether the filer is running in 7Mode or Cluster-Mode, so you only have to configure the credentials in the datasource rule as usual. Some of the existing 7Mode checks have been adjusted. Overall there are now less summary checks available (e.g. fan, temperature, psu). You need to do a service discovery on each NetApp filer. The following table shows the list of available checks and the currently supported NetApp mode. <table> <tr><th>Check</th><th>Description</th><th>7Mode</th><th>Cluster-Mode</th></tr> <tr> <td>netapp_api_aggr</td> <td>Used space and trend of aggregations</td> <td>X</td> <td>X</td></tr> <tr> <td>netapp_api_cluster</td> <td>Cluster status</td> <td>X</td> <td></td></tr> <tr> <td>netapp_api_cpu</td> <td>CPU utilization of nodes</td> <td></td> <td>X</td></tr> <tr> <td>netapp_api_cpu.utilization</td> <td>CPU utilization for 7Mode filer</td> <td>X</td> <td></td></tr> <tr> <td>netapp_api_cpu.nvram_bat</td> <td>NVRAM battery status</td> <td></td> <td>X</td></tr> <tr> <td>netapp_api_disk.summary</td> <td>Disk summary check. Includes total raw capacity and info about broken/spare ratio</td> <td>X</td> <td>X</td></tr> <tr> <td>netapp_api_fan</td> <td>Fan status</td> <td>X</td> <td>X</td></tr> <tr> <td>netapp_api_fcp</td> <td>Fibrechannel interfaces traffic and latency</td> <td></td> <td>X</td></tr> <tr> <td>netapp_api_if</td> <td>Ethernet interfaces</td> <td>X</td> <td>X</td></tr> <tr> <td>netapp_api_protocol</td> <td>Read OPS / Write OPS for each protocol (nfs, nfsv4, cifs, fcp, iscsci)</td> <td>X</td> <td></td></tr> <tr> <td>netapp_api_psu</td> <td>Power supplies</td> <td>X</td> <td>X</td></tr> <tr> <td>netapp_api_snapvault</td> <td>Snapvault Lag-time</td> <td>X</td> <td></td></tr> <tr> <td>netapp_api_status</td> <td>Diagnosis status</td> <td>X</td> <td>X</td></tr> <tr> <td>netapp_api_temp</td> <td>Temperature sensors, grouped by shelf</td> <td>X</td> <td>X</td></tr> <tr> <td>netapp_api_info</td> <td>Displays NetApp version</td> <td>X</td> <td>X</td></tr> <tr> <td>netapp_api_vf_stats.traffic</td> <td>vFiler traffic (Read/Write OPS, Net-Data Send/Recv, Read/Write Bytes)</td> <td>X</td> <td></td></tr> <tr> <td>netapp_api_vf_stats</td> <td>CPU utilization of vFilers</td> <td>X</td> <td></td></tr> <tr> <td>netapp_api_vf_status</td> <td>vFiler status, e.g running</td> <td>X</td> <td></td></tr> <tr> <td>netapp_api_vs_status</td> <td>vServer status, e.g running</td> <td></td> <td>X</td></tr> <tr> <td>netapp_api_volumes</td> <td>Used space an trend of volumes. Able to record detailed performance data for each protocol</td> <td></td> <td></td></tr> <tr> <td>netapp_api_vs_traffic</td> <td>vServer Traffic Summary Ethernet Interfaces</td> <td></td> <td>X</td></tr> <tr> <td>netapp_api_vs_traffic.fcp</td> <td>vServer Traffic Summary Fibrechannel Interfaces</td> <td></td> <td>X</td></tr> <tr> <td>netapp_api_vs_traffic.cifs</td> <td>vServer Traffic Summary Cifs</td> <td></td> <td>X</td></tr> <tr> <td>netapp_api_vs_traffic.iscsi</td> <td>vServer Traffic Summary ISCSI</td> <td></td> <td>X</td></tr> <tr> <td>netapp_api_vs_traffic.nfsv3</td> <td>vServer Traffic Summary nfsv3</td> <td></td> <td>X</td></tr> <tr> <td>netapp_api_vs_traffic.nfsv4</td> <td>vServer Traffic Summary nfsv4</td> <td></td> <td>X</td></tr> <tr> <td>netapp_api_vs_traffic.nfsv4_1</td> <td>vServer Traffic Summary nfsv4.1</td> <td></td> <td>X</td></tr> </table>

8 years, 11 months

Check_MK Werk 2651: Do not allow adding of duplicate hosts anymore

by Mathias Kettner

ID: 2651 Title: Do not allow adding of duplicate hosts anymore Component: WATO Level: 1 Class: New Feature Version: 1.2.7i3 WATO now makes sure that you cannot add a host with a name that already exists in some folder anymore. That avoids problems when later activating changes (where duplicate hosts are not allowed anyway). Note: In previous versions you <i>could</i> have created a host with the same name on different sites. This is not possible anymore.

8 years, 11 months

Check_MK Werk 2679: hp_proliant_power: Not discoverying when host is reporting "absent" state

by Lars Michelsen

ID: 2679 Title: hp_proliant_power: Not discoverying when host is reporting "absent" state Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.2.7i3 When the host is reporting a state of "absent" for power metering, this check is useless, so not discovering the service when this state is reported.

8 years, 11 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1