Checkmk werks level2

checkmk-werks-lvl2@lists.checkmk.com

1 participants
1349 discussions

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 agent_netapp 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 2674: Added native support for monitoring via IPv6

by Lars Michelsen

ID: 2674 Title: Added native support for monitoring via IPv6 Component: Core & Setup Level: 2 Class: New Feature Version: 1.2.7i3 Check_MK is now providing native support for monitoring IPv6 and even dual-stack hosts. This has been implemented in a clean and straight forward way. For each host you can choose which address family shal be used for communication with this host. By default Check_MK is still using only IPv4, but now you can change it to IPv6 for monitoring IPv6 only hosts. In WATO this is done by configuring the host attribute IP Address Family. You can even configure one host to be monitored via IPv4 and IPv6 at the same time. In this situation you need to decide which of the both address families is the primary one. The primary address family is the one which is used for regular monitoring tasks (communication with the agent or SNMP). The secondary address family is only being pinged by default. For the secondary address family a dedicated PING service named (PING v4 or PING v6) is added to the dual-stack hosts. By default the primary address family is IPv4 for all dual-stack hosts. In WATO this can be changed by configuring the rule set Primary IP address family of dual-stack hosts. In some cases you want to perform active checks to check the avilability of a service, e.g. HTTP, using both IPv4 and IPv6. For this case you can add two active checks to the dual-stack host, one having IPv6 enabled and one without having it enabled for using IPv4. But each active check needs to support IPv6 on its own. For the moment the only check working vith IPv6 is <tt>check_http</tt>. This is the default and recommended way for monitoring dual-stack hosts. You use one address family for monitoring the whole system and the other one is just being pinged. Note: If you use the Check_MK Enterprise Edition togehter with the Micro Core, the Smart PING mechanism is not used for IPv6 hosts at the moment. This mechanism has a slightly slower performance, but if you don't have too many IPv6 hosts, this should be OK for the beginning. The basic implementation for IPv6 monitoring has been done. But there are several components in the Check_MK environment left which need to be extended to be fully compatible with IPv6. Some of them are: LI: Parent scanning (check_mk --scan-parents) LI: WATO - Host-Diagnose LI: WATO - Most active checks LI: Event Console LI: Notification Forwarding LI: Livestatus Proxy LI: Several active checks LI: Most special agents LI: The Check_MK Appliance

8 years, 11 months

Check_MK Werk 2649: Bulk renaming of hosts in WATO

by Mathias Kettner

ID: 2649 Title: Bulk renaming of hosts in WATO Component: WATO Level: 2 Class: New Feature Version: 1.2.7i3 The function for renaming hosts in WATO is now available in a new bulk mode. This is a new button in each folder, where you can recursively rename hosts in a generic way. There are several types of renamings that can be done: LI:case translation into lower or upper case LI:adding and removing suffixes LI:adding prefixes LI:regular expression operations (much like <tt>sed</tt>) LI:explicit mappings For each affected site only one restart of the site is needed. This can speed up renaming operations with lots of hosts drastically when compared to renaming each host apart.

8 years, 11 months

Check_MK Werk 2646: New system for displaying time graphs of metrics

by Mathias Kettner

ID: 2646 Title: New system for displaying time graphs of metrics Component: Multisite Level: 3 Class: New Feature Version: 1.2.7i3 Check_MK now has a new implementation of how metrics time graphs (formerly known as performance graphs or PNP graphs) are being created. Instead of hand crafted PNP templates, templates are now being created by Check_MK's new metrics system. In the new declaration file <tt>share/check_mk/web/plugins/metrics/check_mk.py</tt> all names of performance variables are being assigned to units, titles and colors. Graph and Perf-O-Meter definitions both make use of these. The advantages are: LI:Graphs and Perf-O-Meters are much simpler to declare LI:Graphs and Perf-O-Meters now share the same color scheme LI:Graphs are more streamlined LI:It is now much easier to change some general properties of all graphs LI:Default graphs are more intelligent LI:Future addons that work with metrics data are easier to implement Note: existing PNP templates have not been removed but still exist and have precedence over the automatically generated ones. But they will not be maintained anymore and no new manual templates will be created by us anymore.

8 years, 11 months

Check_MK Werk 2645: Fix garbled notification context when \n appears in service description

by Mathias Kettner

ID: 2645 Title: Fix garbled notification context when \n appears in service description Component: Notifications Level: 2 Class: Bug Fix Version: 1.2.7i3 When your service has the name <tt>C:\tmp\network.log</tt>, then the <tt>\n</tt> would be interpreted as newline and everything after the \ was lost. This has been fixed.

8 years, 11 months

Check_MK Werk 2431: WATO Snapshots: Fixed broken performancedata backup

by Andreas Boesl

ID: 2431 Title: WATO Snapshots: Fixed broken performancedata backup Component: WATO Level: 2 Class: Bug Fix Version: 1.2.7i3 WATO was unable to import snapshots with included performance data. This error was a side effect of werk #2486.

8 years, 12 months

Check_MK Werk 2602: Tracking of incompatible Werks

by Mathias Kettner

ID: 2602 Title: Tracking of incompatible Werks Component: Multisite Level: 2 Class: New Feature Version: 1.2.7i3 This new feature helps you updating your configuration after an update to a newer Check_MK version. Check_MK now keeps track about all Incompatible Werks. Such a Werk denotes a software change that might require your knowledge or interaction. In many cases it is just a service rediscovery of some affected hosts that needs to be done. In other cases manual adaptation of your configuration is neccessary. Check_MK now shows you all such Werks in the new version page (click on the Check_MK version number at the top of the sidebar for going there). If you have admin permissions then you can actively acknowledge incompatible werks that you already have checked until you are clean. After each software update you now will see at one glance if some new incompatible Werk has happened since your last update. Note: In order to keep things easy the tracking does not include any Werk that appeared in a version before the start of the 1.2.7 version branch.

8 years, 12 months

Check_MK Werk 2601: Access to Werks (change log) directly in the user interface

by Mathias Kettner

ID: 2601 Title: Access to Werks (change log) directly in the user interface Component: Multisite Level: 2 Class: New Feature Version: 1.2.7i3 Your Check_MK installation now has a new GUI page for showing the complete history of changes (Werks) that are included in the version that is running. You can set several filters for searching within this log. You reach the new page by clicking on the Check_MK version number at the top of the side bar.

8 years, 12 months

Check_MK Werk 2430: Fixed crash with availability queries when using nagios as core

by Andreas Boesl

ID: 2430 Title: Fixed crash with availability queries when using nagios as core Component: Core & Setup Level: 2 Class: Bug Fix Version: 1.2.7i3 The nagios core crashed when a query on the statehist table did return zero entries. This happened when a timewindow was queried where the hosts/services in question did not exist.

8 years, 12 months

Check_MK Werk 2599: Fix newly introduced fatal bug preventing creation of new hosts in WATO

by Mathias Kettner

ID: 2599 Title: Fix newly introduced fatal bug preventing creation of new hosts in WATO Component: WATO Level: 2 Class: Bug Fix Version: 1.2.7i3 This fixes the error message Invalid User Input, Please specify a hostname.

8 years, 12 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level2