Checkmk werks level1 June 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
272 discussions

[2.4.0] Checkmk Werk 16877 created: Nutanix agent: improve error handling during fetch

by Checkmk werks level 1

[//]: # (werk v2) # Nutanix agent: improve error handling during fetch key | value ---------- | --- date | 2024-06-18T10:47:59+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes This werk improves the error handling when the agent is executed. Prior to this change, the Check_MK service displayed that a Crash Report should be submitted whenever the agent failed to retrieve the data. This has been changed with this werk.

3 months

[2.4.0] Checkmk Werk 17074 created: MS Exchange: Use consistent units (ms/s) in rules & graphs

by Checkmk werks level 1

[//]: # (werk v2) # MS Exchange: Use consistent units (ms/s) in rules & graphs key | value ---------- | --- date | 2024-06-18T07:20:14+00:00 version | 2.4.0b1 class | fix edition | cee component | checks level | 1 compatible | yes Various msexch_* checks reported its values in ms in the summary/ruleset but displayed the same value as seconds in the graph. With this werk, all units will be reported consistently.

3 months

[2.2.0] Checkmk Werk 16768 created: Show traceback if a crash occurs during special agents execution

by Checkmk werks level 1

Title: Show traceback if a crash occurs during special agents execution Class: fix Compatible: compat Component: checks Date: 1718634477 Edition: cre Level: 1 Version: 2.2.0p28 Currently, in the event of a crash during the execution of a special agent, the traceback is not displayed in the user interface but is only saved in the crash report on disk. With this werk, the traceback will also be shown in the user interface.

3 months

[2.2.0] Checkmk Werk 16766 created: mknotifyd: use site names in service description

by Checkmk werks level 1

Title: mknotifyd: use site names in service description Class: fix Compatible: incomp Component: checks Date: 1716821823 Edition: cre Level: 2 Version: 2.2.0p28 This update affects users monitoring the OMD Notify Connection services, regardless of whether the connection is encrypted. Previously it was not possible to correctly monitor the Notification Spooler connection with TLS. For encrypted incoming connections, the IP address and port were unavailable because managed by stunnel using Unix sockets. Consequently, services for encrypted connections were named incorrectly and always displayed the IP address as 127.0.0.1. To resolve this issue, we have updated the service naming. Now, the names of the involved sites will be shown in the format: OMD MySite Notification Spooler connection to MyRemoteSite. Impact: LI: Currently monitored services (e.g., those configured with unencrypted connections) will continue to work as usual. LI: Upon rediscovery, new services will be discovered and will adopt the new naming convention. For this reason, this werk is flagged as incompatible LI: To maintain service history, users can create a service description translation rule. This can be done in the configuration at: Setup > Agents > Access to agents > Translation of service descriptions. Use a regex or static string to map the old service names to the new ones.

3 months

[2.2.0] Checkmk Werk 15337 created: Add support for monitoring oracle 23ai

by Checkmk werks level 1

Title: Add support for monitoring oracle 23ai Class: feature Compatible: compat Component: checks Date: 1718714220 Edition: cre Level: 1 Version: 2.2.0p28 We extended the regular expression to detect processes of Oracle 23ai, we now also search for <code>db_pmon_</code>.

3 months

[2.3.0] Checkmk Werk 16768 created: Show traceback if a crash occurs during special agents execution

by Checkmk werks level 1

[//]: # (werk v2) # Show traceback if a crash occurs during special agents execution key | value ---------- | --- date | 2024-06-17T14:27:57+00:00 version | 2.3.0p7 class | fix edition | cre component | checks level | 1 compatible | yes Currently, in the event of a crash during the execution of a special agent, the traceback is not displayed in the user interface but is only saved in the crash report on disk. With this werk, the traceback will also be shown in the user interface.

3 months

[2.3.0] Checkmk Werk 16766 created: mknotifyd: use site names in service description

by Checkmk werks level 1

[//]: # (werk v2) # mknotifyd: use site names in service description key | value ---------- | --- date | 2024-05-27T14:57:03+00:00 version | 2.3.0p7 class | fix edition | cre component | checks level | 2 compatible | no This update affects users monitoring the _OMD Notify Connection_ services, regardless of whether the connection is encrypted. Previously it was not possible to correctly monitor the Notification Spooler connection with TLS. For encrypted incoming connections, the IP address and port were unavailable because managed by stunnel using Unix sockets. Consequently, services for encrypted connections were named incorrectly and always displayed the IP address as 127.0.0.1. To resolve this issue, we have updated the service naming. Now, the names of the involved sites will be shown in the format: _OMD MySite Notification Spooler connection to MyRemoteSite_. Impact: - Currently monitored services (e.g., those configured with unencrypted connections) will continue to work as usual. - Upon rediscovery, new services will be discovered and will adopt the new naming convention. For this reason, this werk is flagged as incompatible - To maintain service history, users can create a service description translation rule. This can be done in the configuration at: _Setup_ > _Agents_ > _Access to agents_ > _Translation of service descriptions_. Use a regex or static string to map the old service names to the new ones.

3 months

[2.3.0] Checkmk Werk 15337 created: Add support for monitoring oracle 23ai

by Checkmk werks level 1

[//]: # (werk v2) # Add support for monitoring oracle 23ai key | value ---------- | --- date | 2024-06-18T12:37:00+00:00 version | 2.3.0p7 class | feature edition | cre component | checks level | 1 compatible | yes We extended the regular expression to detect processes of Oracle 23ai, we now also search for `db_pmon_`.

3 months

[2.4.0] Checkmk Werk 16768 created: Show traceback if a crash occurs during special agents execution

by Checkmk werks level 1

[//]: # (werk v2) # Show traceback if a crash occurs during special agents execution key | value ---------- | --- date | 2024-06-17T14:27:57+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes Currently, in the event of a crash during the execution of a special agent, the traceback is not displayed in the user interface but is only saved in the crash report on disk. With this werk, the traceback will also be shown in the user interface.

3 months

[2.4.0] Checkmk Werk 16766 created: mknotifyd: use site names in service description

by Checkmk werks level 1

[//]: # (werk v2) # mknotifyd: use site names in service description key | value ---------- | --- date | 2024-05-27T14:57:03+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 2 compatible | no This update affects users monitoring the _OMD Notify Connection_ services, regardless of whether the connection is encrypted. Previously it was not possible to correctly monitor the Notification Spooler connection with TLS. For encrypted incoming connections, the IP address and port were unavailable because managed by stunnel using Unix sockets. Consequently, services for encrypted connections were named incorrectly and always displayed the IP address as 127.0.0.1. To resolve this issue, we have updated the service naming. Now, the names of the involved sites will be shown in the format: _OMD MySite Notification Spooler connection to MyRemoteSite_. Impact: - Currently monitored services (e.g., those configured with unencrypted connections) will continue to work as usual. - Upon rediscovery, new services will be discovered and will adopt the new naming convention. For this reason, this werk is flagged as incompatible - To maintain service history, users can create a service description translation rule. This can be done in the configuration at: _Setup_ > _Agents_ > _Access to agents_ > _Translation of service descriptions_. Use a regex or static string to map the old service names to the new ones.

3 months

← Newer
1
...
8
9
10
11
12
13
14
...
28
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 June 2024