Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15940 discussions

[2.2.0] Checkmk Werk 16010 created: Custom graphs/Graph collections: Fix permissions if admin wants to see custom graphs from other users

by Checkmk werks level 1

Title: Custom graphs/Graph collections: Fix permissions if admin wants to see custom graphs from other users Class: fix Compatible: compat Component: multisite Date: 1702027122 Edition: cee Level: 1 Version: 2.2.0p18

9 months, 2 weeks

[2.3.0] Checkmk Werk 16010 created: Custom graphs/Graph collections: Fix permissions if admin wants to see custom graphs from other users

by Checkmk werks level 1

9 months, 2 weeks

[2.3.0] Checkmk Werk 16358 created: Session termination after maximum session age

by Checkmk werks level 1

Title: Session termination after maximum session age Class: feature Compatible: compat Component: wato Date: 1702467423 Edition: cre Level: 1 Version: 2.3.0b1 To mitigate the risk of a session takeover you can now define a maximum session duration. This is set by default to 24 hours. For the case that somebody is actively using the session over this duration you can also configure a threshold to warn users about the upcoming session termination. This value is set by default to 15 minutes. You can disable this feature completely via the global setting *Session management*.

9 months, 2 weeks

[2.3.0] Checkmk Werk 16207 created: host_tag_group: Fix 500 status code when creating a host_tag_group with id already in use

by Checkmk werks level 1

Title: host_tag_group: Fix 500 status code when creating a host_tag_group with id already in use Class: fix Compatible: compat Component: rest-api Date: 1702550742 Edition: cre Level: 1 Version: 2.3.0b1 Before this Werk, when trying to create a host_tag_group using an id belonging to an aux_tag the endpoint returned a status 500 (Internal Server Error). This Werk fixes that behaviour and now returns a status 400, informing that the id is in use. CMK-15167

9 months, 2 weeks

[2.2.0] Checkmk Werk 15873 created: ucd_cpu_load: Consider the number of CPUs

by Checkmk werks level 1

Title: ucd_cpu_load: Consider the number of CPUs Class: fix Compatible: compat Component: checks Date: 1697635673 Edition: cre Level: 1 Version: 2.2.0p18 The number of CPUs in UCD SNMP Daemon: CPU Utilization was hardcoded to 1, which is mostly wrong today. With this Werk we count the number of CPUs by fetching {HOST-RESOURCES-V2-MIB::hrProcessorFrwID}. If this is not available the check falls back to 1 CPU.

9 months, 2 weeks

[2.1.0] Checkmk Werk 13478 adapted: Mitigate wrong conversion of disabled service rules on update

by Checkmk werks level 1

Werk 13478 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Mitigate wrong conversion of disabled service rules on update Class: fix Compatible: incomp Component: wato Date: 1639747685 Edition: cre Knowledge: doc Level: 1 State: unknown Version: 2.1.0b1 During <tt>cmk-update-config</tt> some disabled services rules are being broken by introducing an undesired escaping. This werk reduces the number of cases in which this happens. Users "Disabled Services" rules were affected if they fullfilled all of the following criteria: <ul> <li>They have exactly one host condition (explicit or pattern)</li> <li>They have no tag based conditions</li> <li>All their patterns for the service name end in "<tt>$</tt>"</li> </ul> After this werk, only rules will be affected if they additionally <ul> <li> have exactly one explicit host condition (not a regular expression)</li> <li> contain both quoted and unquoted special characters in their service name pattern</li> </ul> For instance: "<tt>Foo[12]$</tt>" and "<tt>Foo\[12\]$</tt>" will remain unchanged, whereas "<tt>Foo\[1\][2]$</tt>" will be changed to "<tt>Foo\[1\]\[2\]$</tt>". If this still affects you, you can avoid meeting the above criteria. For instance try to replace "<tt>my_hostname</tt>" by "<tt>~^my_hostname$</tt>" or to craft a service name pattern that does not require the trailing "<tt>$</tt>". ------------------------------------<diff>------------------------------------------- Title: Mitigate wrong conversion of disabled service rules on update Class: fix Compatible: incomp Component: wato Date: 1639747685 Edition: cre Knowledge: doc Level: 1 State: unknown Version: 2.1.0b1 During <tt>cmk-update-config</tt> some disabled services rules are being broken by introducing an undesired escaping. This werk reduces the number of cases in which this happens. Users "Disabled Services" rules were affected if they fullfilled all of the following criteria: <ul> <li>They have exactly one host condition (explicit or pattern)</li> <li>They have no tag based conditions</li> <li>All their patterns for the service name end in "<tt>$</tt>"</li> </ul> After this werk, only rules will be affected if they additionally <ul> <li> have exactly one explicit host condition (not a regular expression)</li> - <li> contain both quoted and unquoted special characters</li> in their service name pattern ? ----- + <li> contain both quoted and unquoted special characters in their service name pattern</li> ? +++++ </ul> For instance: "<tt>Foo[12]$</tt>" and "<tt>Foo\[12\]$</tt>" will remain unchanged, whereas "<tt>Foo\[1\][2]$</tt>" will be changed to "<tt>Foo\[1\]\[2\]$</tt>". If this still affects you, you can avoid meeting the above criteria. For instance try to replace "<tt>my_hostname</tt>" by "<tt>~^my_hostname$</tt>" or to craft a service name pattern that does not require the trailing "<tt>$</tt>". -

9 months, 2 weeks

[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, 2 weeks

[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: Add to favourites and Remove from favourites. 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: Add to favourites and Remove from favourites. 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, 2 weeks

[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 only 7-Mode 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 Netapp Manageability SDK 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 only 7-Mode 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 Netapp Manageability SDK 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, 2 weeks

[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, 2 weeks

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1