Checkmk werks level1 December 2023

checkmk-werks-lvl1@lists.checkmk.com

1 participants
128 discussions

[1.5.0] Checkmk Werk 4580 adapted: informix_dbspaces, informix_locks, informix_logusage, informix_sessions, informix_status, informix_tabextents: New checks for IBM Informix DBs

by Checkmk werks level 1

Werk 4580 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: informix_dbspaces, informix_locks, informix_logusage, informix_sessions, informix_status, informix_tabextents: New checks for IBM Informix DBs Level: 1 Component: checks Compatible: compat Edition: cre Version: 1.5.0i1 Date: 1491293050 Class: feature In order to use these checks you have to install the related agent plugin {{mk_informix}} and state a configuration file informix.cfg. <ul> <li>ONINIT_PATH; Default is empty, which means auto detection:</li> <li>ONINIT_PATH=/PATH/TO/ONINIT-BINARY</li> </ul> Excluding sections: status, sessions, locks, tabextents, dbspaces, logusage: <ul> <li>EXCLUDES_INFORMIX-INSTANCE="SECTION SECTION ..."</li> <li>EXCLUDES_INFORMIX-INSTANCE=ALL</li> <li>EXCLUDES="SECTION SECTION ..."</li> <li>EXCLUDES=ALL</li> </ul> ------------------------------------<diff>------------------------------------------- Title: informix_dbspaces, informix_locks, informix_logusage, informix_sessions, informix_status, informix_tabextents: New checks for IBM Informix DBs Level: 1 Component: checks Compatible: compat Edition: cre Version: 1.5.0i1 Date: 1491293050 Class: feature In order to use these checks you have to install the related agent plugin {{mk_informix}} and state a configuration file informix.cfg. <ul> <li>ONINIT_PATH; Default is empty, which means auto detection:</li> - <ul> <li>ONINIT_PATH=/PATH/TO/ONINIT-BINARY</li> </ul> + - <li>Excluding sections: status, sessions, locks, tabextents, dbspaces, logusage:</li> ? ---- ----- + Excluding sections: status, sessions, locks, tabextents, dbspaces, logusage: <ul> <li>EXCLUDES_INFORMIX-INSTANCE="SECTION SECTION ..."</li> <li>EXCLUDES_INFORMIX-INSTANCE=ALL</li> <li>EXCLUDES="SECTION SECTION ..."</li> <li>EXCLUDES=ALL</li> </ul> - </ul>

9 months, 1 week

[1.2.3] Checkmk Werk 50 adapted: New concept of favorite hosts and services plus matching filters and views

by Checkmk werks level 1

Werk 50 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: New concept of favorite hosts and services plus matching filters and views Level: 2 Component: multisite Version: 1.2.3i7 Date: 1383411707 Class: feature The new "Favorites" feature introduces a new pair of commands for hosts and services: <i>Add to favourites</i> and <i>Remove from favourites</i>. It allows you to manage your personal list of favourite hosts and services. This list is saved on a per-user-base. Objects on this list are marked with a star icon. The favourites-list can be used for filtering. Two new predefined views "Favourite hosts" and "Favourite services" are available for showing you favourite objects. Also the new filters have been added to several views. Please note, that when you make a host a favourite, the services of that host will not automatically get favourites as well. But you easily can use the "Service Search" view for listing all services on favorite hosts, if you like that behaviour. With a combination of the existing filters you can do many useful queries like "Show me all problems on my favourite hosts in host group X". The advantage of favourites as opposed to host- and service groups are: <ul> <li>No change to the monitoring configuration is neccessary and thus no restart of the core.</li> <li>Each user can manage his indiviual list.</li> </ul> ------------------------------------<diff>------------------------------------------- Title: New concept of favorite hosts and services plus matching filters and views Level: 2 Component: multisite Version: 1.2.3i7 Date: 1383411707 Class: feature The new "Favorites" feature introduces a new pair of commands for hosts and services: <i>Add to favourites</i> and <i>Remove from favourites</i>. It allows you to manage your personal list of favourite hosts and services. This list is saved on a per-user-base. Objects on this list are marked with a star icon. The favourites-list can be used for filtering. Two new predefined views "Favourite hosts" and "Favourite services" are available for showing you favourite objects. Also the new filters have been added to several views. Please note, that when you make a host a favourite, the services of that host will not automatically get favourites as well. But you easily can use the "Service Search" view for listing all services on favorite hosts, if you like that behaviour. With a combination of the existing filters you can do many useful queries like "Show me all problems on my favourite hosts in host group X". The advantage of favourites as opposed to host- and service groups are: <ul> <li>No change to the monitoring configuration is neccessary and thus no restart of the core.</li> - <li>Each user can manage his indiviual list.</li>. ? - + <li>Each user can manage his indiviual list.</li> </ul>

9 months, 1 week

[1.2.7] Checkmk Werk 1665 adapted: agent_netapp: New special agent for NetApp monitoring via Web-API

by Checkmk werks level 1

Werk 1665 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: agent_netapp: New special agent for NetApp monitoring via Web-API Level: 3 Component: checks Class: feature Compatible: compat State: unknown Version: 1.2.7i1 Date: 1418736173 The new agent_netapp allows you to collect data from a NetApp Filer through its Web-API. Right now <b>only 7-Mode</b> setups are supported, but Cluster-Mode is following soon. H2: Agent setup This agent does not run out of the box, because it depends on some files from the <i>Netapp Manageability SDK</i> from NetApp. You can download it <a href="http://mysupport.netapp.com/NOW/cgi-bin/software/?product=NetApp+Manageabil…">here (customer/partner login required)</a> In this package you will find a python API binding. The agent_netapp requires the two python files (<tt>NaElement.py</tt> / <tt>NaServer.py</tt>) to be put into the sites local directory <tt>~/local/lib/python</tt>. (Our plan is to eleminate this tedious step in a future version) Once the agent has all required files you need to create a user account with the following permissions: <ul> <li>perf-object-get-instances</li> <li>net-ifconfig-get</li> <li>aggr-list-info</li> <li>storage-shelf-bay-list-info</li> <li>disk-list-info</li> <li>vfiler-list-info</li> <li>vfiler-get-status</li> <li>volume-list-info</li> <li>system-get-version</li> <li>system-get-info</li> <li>storage-shelf-environment-list-info</li> <li>cf-status</li> <li>diagnosis-status-get</li> </ul> Note: This list might increase in later versions If the new agent is able to access the Web-API the following new checks are ready to process the data: <table> <tr><th>Check</th><th>Description</th></tr> <tr><td>netapp_api_aggr</td><td>Used space and trend of aggregations</td></tr> <tr><td>netapp_api_volumes</td><td>Used space and trend of volumes. Able to record detailed performance data for each protocol</td></tr> <tr><td>netapp_api_cluster</td><td>Cluster status</td></tr> <tr><td>netapp_api_cpu</td><td>Overall CPU utilization</td></tr> <tr><td>netapp_api_disk</td><td>Disk summary check. Includes total raw capacity and info about broken and spare disks</td></tr> <tr><td>netapp_api_if</td><td>Interface checks (Fibrechannel not include so far)</td></tr> <tr><td>netapp_api_protocol</td><td>Read OPS / Write OPS for each protocol (nfs, nfsv4, cifs, fcp, iscsci)</td></tr> <tr><td>netapp_api_status</td><td>Filers Diagnosis Status (overall status)</td></tr> <tr><td>netapp_api_version</td><td>Version information</td></tr> <tr><td>netapp_api_vf_stats.traffic</td><td>vFiler traffic (Read/Write OPS, Net-Data Send/Recv, Read/Write Bytes)</td></tr> <tr><td>netapp_api_vf_stats.cpu_util</td><td>vFiler CPU utilization</td></tr> <tr><td>netapp_api_vf_status</td><td>vFiler status</td></tr> <tr><td>netapp_api_psu</td><td>Power supplies summary which are relevant to that filer. Reports broken units</td></tr> <tr><td>netapp_api_fan</td><td>Fans summary which are relevant to that filer. Reports broken units</td></tr> <tr><td>netapp_api_temp</td><td>Temperature sensor summary for internal and ambient sensors relevant to that filer. Reports broken units</td></tr> </table> Note: This is the initial version of this agent. It has been tested on a handful of NetApp systems. ------------------------------------<diff>------------------------------------------- Title: agent_netapp: New special agent for NetApp monitoring via Web-API Level: 3 Component: checks Class: feature Compatible: compat State: unknown Version: 1.2.7i1 Date: 1418736173 The new agent_netapp allows you to collect data from a NetApp Filer through its Web-API. Right now <b>only 7-Mode</b> setups are supported, but Cluster-Mode is following soon. H2: Agent setup This agent does not run out of the box, because it depends on some files from the <i>Netapp Manageability SDK</i> from NetApp. You can download it <a href="http://mysupport.netapp.com/NOW/cgi-bin/software/?product=NetApp+Manageabil…">here (customer/partner login required)</a> In this package you will find a python API binding. The agent_netapp requires the two python files (<tt>NaElement.py</tt> / <tt>NaServer.py</tt>) to be put into the sites local directory <tt>~/local/lib/python</tt>. (Our plan is to eleminate this tedious step in a future version) Once the agent has all required files you need to create a user account with the following permissions: <ul> <li>perf-object-get-instances</li> <li>net-ifconfig-get</li> <li>aggr-list-info</li> <li>storage-shelf-bay-list-info</li> <li>disk-list-info</li> <li>vfiler-list-info</li> <li>vfiler-get-status</li> <li>volume-list-info</li> <li>system-get-version</li> <li>system-get-info</li> <li>storage-shelf-environment-list-info</li> <li>cf-status</li> <li>diagnosis-status-get</li> </ul> Note: This list might increase in later versions If the new agent is able to access the Web-API the following new checks are ready to process the data: <table> <tr><th>Check</th><th>Description</th></tr> <tr><td>netapp_api_aggr</td><td>Used space and trend of aggregations</td></tr> <tr><td>netapp_api_volumes</td><td>Used space and trend of volumes. Able to record detailed performance data for each protocol</td></tr> <tr><td>netapp_api_cluster</td><td>Cluster status</td></tr> <tr><td>netapp_api_cpu</td><td>Overall CPU utilization</td></tr> <tr><td>netapp_api_disk</td><td>Disk summary check. Includes total raw capacity and info about broken and spare disks</td></tr> <tr><td>netapp_api_if</td><td>Interface checks (Fibrechannel not include so far)</td></tr> <tr><td>netapp_api_protocol</td><td>Read OPS / Write OPS for each protocol (nfs, nfsv4, cifs, fcp, iscsci)</td></tr> <tr><td>netapp_api_status</td><td>Filers Diagnosis Status (overall status)</td></tr> <tr><td>netapp_api_version</td><td>Version information</td></tr> <tr><td>netapp_api_vf_stats.traffic</td><td>vFiler traffic (Read/Write OPS, Net-Data Send/Recv, Read/Write Bytes)</td></tr> <tr><td>netapp_api_vf_stats.cpu_util</td><td>vFiler CPU utilization</td></tr> <tr><td>netapp_api_vf_status</td><td>vFiler status</td></tr> <tr><td>netapp_api_psu</td><td>Power supplies summary which are relevant to that filer. Reports broken units</td></tr> - <tr><td>netapp_api_fan</td><td>Fans summary which are relevant to that filer. Reports broken units</td><tr> + <tr><td>netapp_api_fan</td><td>Fans summary which are relevant to that filer. Reports broken units</td></tr> ? + <tr><td>netapp_api_temp</td><td>Temperature sensor summary for internal and ambient sensors relevant to that filer. Reports broken units</td></tr> </table> Note: This is the initial version of this agent. It has been tested on a handful of NetApp systems.

9 months, 1 week

[2.2.0] Checkmk Werk 16035 created: CSV export for availability timelines of hosts

by Checkmk werks level 1

Title: CSV export for availability timelines of hosts Class: fix Compatible: compat Component: multisite Date: 1702457176 Edition: cre Level: 1 Version: 2.2.0p18 When exporting all availability timelines of a host as a CSV file only the last timeline was written to the CSV file. Now all timelines are written again like in Checkmk 2.0 and before.

9 months, 1 week

[2.2.0] Checkmk Werk 16354 adapted: nginx_status_2.py: Fix SyntaxError

by Checkmk werks level 1

Werk 16354 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: nginx_status_2.py: Fix SyntaxError Class: fix Compatible: compat Component: checks Date: 1701879932 Edition: cre Level: 1 Version: 2.2.0p17 The Python 2-version of the NGINX agent plugin crashed with a SyntaxError: C+: File "nginx_status_2.py", line 132 config: dict = {} ^ SyntaxError: invalid syntax C-: ------------------------------------<diff>------------------------------------------- Title: nginx_status_2.py: Fix SyntaxError Class: fix Compatible: compat Component: checks Date: 1701879932 Edition: cre Level: 1 Version: 2.2.0p17 The Python 2-version of the NGINX agent plugin crashed with a SyntaxError: - C:+ + C+: File "nginx_status_2.py", line 132 config: dict = {} ^ SyntaxError: invalid syntax - C:- + C-:

9 months, 1 week

[2.3.0] Checkmk Werk 16035 created: CSV export for availability timelines of hosts

by Checkmk werks level 1

Title: CSV export for availability timelines of hosts Class: fix Compatible: compat Component: multisite Date: 1702457176 Edition: cre Level: 1 Version: 2.3.0b1 When exporting all availability timelines of a host as a CSV file only the last timeline was written to the CSV file. Now all timelines are written again like in Checkmk 2.0 and before.

9 months, 1 week

[2.3.0] Checkmk Werk 16354 adapted: nginx_status_2.py: Fix SyntaxError

by Checkmk werks level 1

Werk 16354 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: nginx_status_2.py: Fix SyntaxError Class: fix Compatible: compat Component: checks Date: 1701879932 Edition: cre Level: 1 Version: 2.3.0b1 The Python 2-version of the NGINX agent plugin crashed with a SyntaxError: C+: File "nginx_status_2.py", line 132 config: dict = {} ^ SyntaxError: invalid syntax C-: ------------------------------------<diff>------------------------------------------- Title: nginx_status_2.py: Fix SyntaxError Class: fix Compatible: compat Component: checks Date: 1701879932 Edition: cre Level: 1 Version: 2.3.0b1 The Python 2-version of the NGINX agent plugin crashed with a SyntaxError: - C:+ + C+: File "nginx_status_2.py", line 132 config: dict = {} ^ SyntaxError: invalid syntax - C:- + C-:

9 months, 1 week

[2.1.0] Checkmk Werk 16011 created: HW/SW Inventory: Fix error while merging inventory and status data tables if one is empty

by Checkmk werks level 1

Title: HW/SW Inventory: Fix error while merging inventory and status data tables if one is empty Class: fix Compatible: compat Component: inv Date: 1702281903 Edition: cre Level: 1 Version: 2.1.0p38

9 months, 1 week

[2.2.0] Checkmk Werk 16283 created: notification rule: update rule no longer creates a new rule

by Checkmk werks level 1

Title: notification rule: update rule no longer creates a new rule Class: fix Compatible: compat Component: rest-api Date: 1702294645 Edition: cre Level: 1 Version: 2.2.0p18 This werk addresses an issue found when updating a rule via the REST-API. Previously, it would instead of updating an existing rule, create a new one. We now update the existing rule as would be expected.

9 months, 1 week

[2.2.0] Checkmk Werk 16033 created: Unable to create crash report

by Checkmk werks level 1

Title: Unable to create crash report Class: fix Compatible: compat Component: checks Date: 1701086091 Edition: cre Level: 1 Version: 2.2.0p18 When custom check plugins that used tuples as dictionary keys in the section crashed, the crash creation failed and crashed itself. Now the crash creation no longer fails and the crash is created successfully.

9 months, 1 week

← Newer
1
2
3
4
5
6
7
8
...
13
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 December 2023