Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15953 discussions

Checkmk Werk 15219: time_period: disallow builtin timeperiod in timeperiod exclude

by Gav

ID: 15219 Title: time_period: disallow builtin timeperiod in timeperiod exclude Component: REST API Level: 1 Class: Bug fix Version: 2.2.0i1 This werk fixes an issue where the user could via the REST-API select the builtin time period 24X7 as the timeperiod to exclude in a custom time period. This is no longer possible.

1 year, 7 months

Checkmk Werk 15272: juniper_fru: support for Juniper MX2010

by Benedikt Seidl

ID: 15272 Title: juniper_fru: support for Juniper MX2010 Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1

1 year, 7 months

Checkmk Werk 14182: BI aggregations: Introduced option to freeze aggregation structure

by Andreas Boesl

ID: 14182 Title: BI aggregations: Introduced option to freeze aggregation structure Component: BI Level: 1 Class: New feature Version: 2.2.0i1 You can now choose to freeze the structure of an aggregation group. Once created, aggregations will never change their structure unless the user triggers a rebuild. To enable frozen aggregations, you have to set the new option <tt>New aggregations are frozen</tt> in the aggregation configuration page. If this option is set, all aggregation trees created from this aggregation are considered frozen right after their creation. It is still possible to re-freeze single trees of such an aggregation group. A snowflake icon has been introduced to indicate that an aggregation is frozen. If you click on this icon, an additional view will show the difference between the frozen aggregate and its live version. On this page you can also send a command to refreeze the frozen aggregation.

1 year, 7 months

Checkmk Werk 13972: Filters of 'list rulesets' endpoint have no effect

by Teresa Siegmantel

ID: 13972 Title: Filters of 'list rulesets' endpoint have no effect Component: REST API Level: 1 Class: Bug fix Version: 2.2.0i1 Using various filters of the 'list rules' endpoint (GET '/domain-types/ruleset/collections/all') had no effect on the result. This is no longer the case. With this fix, the originally intended default behavior of the parameter such as 'used' and 'deprecated' are now respected and the endpoint returns only used rules unless specified otherwise.

1 year, 7 months

Checkmk Werk 15273: agent_azure: "No scheme supplied"

by Benedikt Seidl

ID: 15273 Title: agent_azure: "No scheme supplied" Component: agents Level: 1 Class: Bug fix Version: 2.2.0i1 Under certain circumstances agent_azure was exiting with the following error: C+: Invalid URL '': No scheme supplied. Perhaps you meant http://? C-:

1 year, 7 months

Checkmk Werk 15232: Re-evaluate active MKPs for minor version differences

by Moritz Kiemer

ID: 15232 Title: Re-evaluate active MKPs for minor version differences Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 This affects the newly introduced feature of having different MKPs active for remote sites with deviating Checkmk versions. Previously, we only re-evaluated the active MKPs for major version differences, but in fact we must do it whenever the remote sites version is not the same as the central sites version (as an MKP may only be applicable to a specific patch release).

1 year, 7 months

Checkmk Werk 15088: Views: Regex in 'Joined column' is now possible

by Simon Jess

ID: 15088 Title: Views: Regex in 'Joined column' is now possible Component: Multisite Level: 1 Class: New feature Version: 2.2.0i1 Now you can use regexes in {{Joined column}}s. If multiple entries are found the first one of the sorted entries will be used. These regexes can be combined with macros in inventory based views and are evaluated {{AFTER}} the macro replacements. These macros don't need to be escaped, all other special characters have to be escaped: {{ORA $SID$\.SYSTEM Tablespace}} Example: <ul> <li>Choose {{Oracle instances}} as the data source</li> <li>Choose {{SID}} with {{$SID$}} below macros</li> <li>Now you can connect {{Services: Summary}} of the services {{ORA $SID$.(SYSAUX|TEMP) Tablespace}} below {{Joined column}}</li> </ul> Note: These regexes are basically case sensitive. If you need case insensitive regexes you have to add the global flag {{(?i)}} at the beginning of this regex. Example: <ul> <li>From the data source {{Oracle instances}} we get the SIDs in upper case format</li> <li>Items in filesystem service description are in lower case format</li> <li>Use the regex {{(?i)Filesystem /path/to/$SID$}} below {{Joined services}} in order to join the related service column</li> </ul>

1 year, 7 months

Checkmk Werk 15182: Abort update if incompatible user IDs are found

by Hannes Rantzsch

ID: 15182 Title: Abort update if incompatible user IDs are found Component: Site Management Level: 1 Class: New feature Version: 2.2.0i1 In Checkmk 2.2.0 the use of certain special characters in user IDs is no longer allowed. As a result, some user IDs that were previously valid in Checkmk version 2.1.0 will become invalid in version 2.2.0. The validation affects both local users and users from external connections such as LDAP. However, local users created in the Web UI are guaranteed to be compatible as the same restrictions were already applied there. Since Checkmk 2.2.0 will not work if any incompatible user ID is present, <tt>omd update</tt> will look for them and abort if any incompatible user ID is found. To be compatible with Checkmk version 2.2.0 please ensure that all user IDs adhere to the following restrictions: The first character of a user ID must be a digit, a letter, an underscore (<tt>_</tt>), or a dollar sign (<tt>$</tt>). The rest of the user ID may additionally contain dash (<tt>-</tt>), at (<tt>@</tt>), and dot (<tt>.</tt>).

1 year, 7 months

Checkmk Werk 15145: agent_azure: Remove caching from the azure_usagedetails section

by Sofia Colakovic

ID: 15145 Title: agent_azure: Remove caching from the azure_usagedetails section Component: agents Level: 1 Class: Bug fix Version: 2.2.0i1 Usage details section provides yesterday's Azure resource costs used in the "Cost" check plugin. Until now, the section data was fetched once a day and cached. The problem is that because yesterday's costs are still being calculated in the Azure's Cost Management, they change throughout the day. In order to report the cost data as soon as possible and to be consistent with the Azure's Cost Management, the caching of the azure_usagedetails section has been removed.

1 year, 7 months

Checkmk Werk 15381: Host Tag can now be "null" in REST API responses

by Wontek Hong

ID: 15381 Title: Host Tag can now be "null" in REST API responses Component: REST API Level: 1 Class: Bug fix Version: 2.2.0i1 The REST API can now return "null" values for host tags. Previously, the inclusion of "null" in the allowed enums broke the validation. This werk fixes this "null" bug.

1 year, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1