Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15966 discussions

Checkmk Werk 15013: $HOSTADDRESS and $HOSTNAME can now be used in aggregation names

by External contributor

ID: 15013 Title: $HOSTADDRESS and $HOSTNAME can now be used in aggregation names Component: BI Level: 1 Class: Bug fix Version: 2.2.0i1 As stated in the inline help $HOSTADDRESS and $HOSTNAME can now be used in aggregation names.

1 year, 9 months

Checkmk Werk 15002: Fix "Base on role" default while cloning roles

by Ronny Bruska

ID: 15002 Title: Fix "Base on role" default while cloning roles Component: Setup Level: 1 Class: Bug fix Version: 2.2.0i1 If you cloned a rule multiple times, from the second clone on, the "Based on role" property had the default "Administrator", no matter what initial builtin role was cloned. The property will now always show the builtin role of the source role that was cloned. E.g. if you clone "guest" multiple times, the clones will always show "Guest user".

1 year, 9 months

Checkmk Werk 15056: aux_tags: rest-api endpoint implementation

by Gav

ID: 15056 Title: aux_tags: rest-api endpoint implementation Component: REST API Level: 1 Class: New feature Version: 2.2.0i1 This werk introduces the implementation of the Auxiliary Tags endpoints. These endpoints replace the old Web-API functionality. Users can now GET, CREATE, PUT and DELETE Auxiliary Tags via the REST API. Client scripts should be adjusted accordingly.

1 year, 10 months

Checkmk Werk 14904: aux_tags: New REST API endpoint implementation

by Gav

ID: 14904 Title: aux_tags: New REST API endpoint implementation Component: REST API Level: 1 Class: New feature Version: 2.2.0i1 This werk introduces the implementation of the Auxiliary Tags endpoints. These endpoints replace the old Web-API functionality. Users can now GET, CREATE, PUT and DELETE Auxiliary Tags via the REST API. Client scripts should be adjusted accordingly.

1 year, 10 months

Checkmk Werk 15035: wut_webio: handling of case when state is empty

by Wontek Hong

ID: 15035 Title: wut_webio: handling of case when state is empty Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 It is possible that a device occasionally returns an empty string for different reasons such as a firmware problem. Prior to this werk, this case was left unhandled. This werk resolves this issue.

1 year, 10 months

Checkmk Werk 14969: In case of error show most recent message in service summary

by Rebekka Seltmann

ID: 14969 Title: In case of error show most recent message in service summary Component: Checks & agents Level: 1 Class: New feature Version: 2.2.0i1 This werk only affects maintainers of custom special agents: Previously, when an error occurred when executing a special agent, the first exception line was displayed in the service summary of the Check_MK service. Since the last line is usually the most recent message, e.g. when displaying traceback, this werk changes the summary to be the last line.

1 year, 10 months

Checkmk Werk 14968: Crash reporting for special agents

by Rebekka Seltmann

ID: 14968 Title: Crash reporting for special agents Component: Checks & agents Level: 1 Class: New feature Version: 2.2.0i1 The following special agents now create a crash report if they encounter an unforeseen exception: LI: Apache ActiveMQ queues LI: Cisco Meraki LI: Datadog LI: Elasticsearch LI: Google Cloud Platform (GCP) LI: HPE StoreOnce via REST API 4.x LI: IPMI Sensors via Freeipmi or IPMItool LI: Microsoft Azure Status LI: MobileIron API LI: MQTT broker statistics LI: Nutanix Prism LI: Proxmox VE LI: SMB Share fileinfo If a crash occurs, the Check_MK and Check_MK Discovery services will become CRIT as before, but now display a message with the Crash-ID.

1 year, 10 months

Checkmk Werk 15000: Fix combined graphs in reports

by Ronny Bruska

ID: 15000 Title: Fix combined graphs in reports Component: Reporting & Availability Level: 1 Class: Bug fix Version: 2.2.0i1 Since werk #14295 in version 2.1.0p14, some combined graphs showed an exception like "Cannot render graph: host, service description or regex not found in context". A workaround was, to edit the content element and set the missing context filter. Unfortunately, if you used host or service groups as filter, this workaround didn't work.

1 year, 10 months

Checkmk Werk 15038: Distributed configuration: Fix active Setup menu on remote site

by Joerg Herbel

ID: 15038 Title: Distributed configuration: Fix active Setup menu on remote site Component: Multisite Level: 1 Class: Bug fix Version: 2.2.0i1 On remote sites with enabled configuration replication which were one major version ahead of the central site, the Setup menu was always active, even if Disable remote configuration was selected in the central site. Hence, users could actively change the configuration, which was however overwritten upon the next configuration synchronization with the central site. Note that this issue also occured if a remote site running on the same major version as the central site was updated to the next higher major version. In case the central site was updated as well (st. both sites ran on the same major version again), the issue could be solved by activating changes for the remote site in the central site for the first time after updating both sites. This issue was present since 2.0.0p6 / 2.1.0.

1 year, 10 months

Checkmk Werk 14925: Tighten permissions for Event Console pipe and sockets

by Maximilian Wirtz

ID: 14925 Title: Tighten permissions for Event Console pipe and sockets Component: Event Console Level: 1 Class: Bug fix Version: 2.2.0i1 For some internal communication of the Event Console Unix sockets are used. These reside in <tt>tmp/run/mkeventd/</tt> and used to be world readable. Since these sockets are not meant to be used from site external scripts and we cannot foresee the side-effects the permissions were changed so that only Checkmk can read and write to them. To make it easier to write custom events to the Event Console there is a Unix pipe also in <tt>tmp/run/mkeventd/</tt>. This pipe used to be world readable and writeable. With this Werk the permission is changed so that the Pipe is only world writeable. So custom scripts can still write events to this pipe but can no longer read from this pipe. If you used these sockets or pipe with custom scripts and rely on the previous permissions, you still can change them (eg. with <tt>chmod</tt>). Please be aware that we do not support this customization.

1 year, 10 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1