Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
16031 discussions

Checkmk Werk 10753: Allow more printable ASCII characters in email addresses

by Tom Baerwinkel

ID: 10753 Title: Allow more printable ASCII characters in email addresses Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 Printable ASCII characters like '#', '$', and "~" as defined by RFC5322 are now allowed in email addresses.

4 years, 6 months

Checkmk Werk 10983: check_dns: Fix "DNS CRITICAL - expected 'A, B, ...' but got 'B, A, ...'"

by Simon Jess

ID: 10983 Title: check_dns: Fix "DNS CRITICAL - expected 'A,B,...' but got 'B,A,...'" Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 Sort expected answers alphabetically which may include multiple IP addresses or host names separated by comma.

4 years, 6 months

Checkmk Werk 10840: Fix evaluation of time specific parameters if default parameters are tuple based

by Simon Jess

ID: 10840 Title: Fix evaluation of time specific parameters if default parameters are tuple based Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 Old tuple based parameters may look like C+: NAME_default_levels = (90.0, 95.0) C-: In this case if time specific parameters are additionally configured and the check is executed outside of this time period then the evaluation of these parameters crashed C+: TypeError: cannot convert dictionary update sequence element #0 to a sequence C-: Now we simply ignore the (old) tuple-based parameters. A rule with a timespecifc parameter settings always has an implicit default parameter set, even if no timeperiod matches.

4 years, 6 months

Checkmk Werk 10921: Monitor single files with mk_filestats

by Timotheus Bachinger

ID: 10921 Title: Monitor single files with mk_filestats Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 This werks allows to monitor single files with mk_filestats. If configured, a dedicated service is created per matched file on the monitored host.

4 years, 6 months

Checkmk Werk 10973: New bakery rule "Set cache age for plugins (UNIX)"

by Sven Panne

ID: 10973 Title: New bakery rule "Set cache age for plugins (UNIX)" Component: agents Level: 1 Class: New feature Version: 1.7.0i1 It is now possible to set a cache age for all UNIX agent plugins via agent bakery rule. In the new ruleset "Set cache age for plugins (UNIX)", you can define a set of a glob style pattern and an interval, that gets applied to all plugin files (files at /usr/lib/check_mk_agent/plugins on the target hosts) of the matching agent package and that results in caching the plugin's agent outputs for the given interval. Additionally, you can decide whether this set should override interval times from the plugin's dedicated ruleset. This ruleset can be specified and applied multiple times. Please note that no verification is done whether the configured intervals are suitable for the matching plugins. Especially, please be careful when overriding intervals from the plugin's dedicated rules, as there may be a default/minimal caching time for performance or other reasons.

4 years, 7 months

Checkmk Werk 10973: New bakery rule "Set cache age for plugins (UNIX)"

by Andreas Umbreit

4 years, 7 months

Checkmk Werk 10839: if.include: Fix missing performance data of interface groups on clusters

by Simon Jess

ID: 10839 Title: if.include: Fix missing performance data of interface groups on clusters Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 Interface groups may be configured on clusters. In order to detect counter wraps all metrics of each interface of the cluster nodes are checked. In the counter names the node name was missing. This led to empty performance data because counter wraps were wrongly detected.

4 years, 7 months

Checkmk Werk 10838: lnx_if: Fix grouping of interfaces on clusters

by Simon Jess

ID: 10838 Title: lnx_if: Fix grouping of interfaces on clusters Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 On clusters a check plugin processes all node data at once. Interfaces may be grouped by index. The check plugin {{lnx_if}} serially numbered the interface indices across all node data. This led to missing interfaces in a group. Now the check plugin serially numbers the interface indices PER node.

4 years, 7 months

Checkmk Werk 10975: Support local files in Agent Bakery

by Andreas Umbreit

ID: 10975 Title: Support local files in Agent Bakery Component: agents Level: 2 Class: New feature Version: 1.7.0i1 The agent bakery now recognizes files placed under the local hierachy of the Checkmk site and packages them as a replacement for the corresponding non-local/builtin-files. Previously, this feature was available for some files like "custom-files" or the agent itself. Now this holds true for all files that get packaged into the baked agent package. For example, if you want to replace a plugin file, that is located at <code>~/share/check_mk/agents/plugins/my_plugin</code>, you would place your own version at <code>~/local/share/check_mk/agents/plugins/my_plugin</code>. Additionally, the agent bakery watches all files that are relevant for a package and will invalidate the current package upon changes in file size, modification date, or file permissions, resulting in a newly baked package with new agent hash on bake request. This is visible by an orange-colored "Bake agents" button at the agent bakery. Especially, if a file is added to the local hierarchy as a replacement for a builtin-file, this will be recognized as a file change and result in a new package on bake request. Please note: Some files will get renamed by the bake process, e.g. the source file <code>check_mk_agent.linux</code> will result in <code>check_mk_agent</code> in the final agent package. In order to get a local file packaged, you always have to place your local file using the source name (Here: <code>~/local/share/check_mk/agents/check_mk_agent.linux</code>).

4 years, 7 months

Checkmk Werk 10974: Agent Bakery: require minimum length of 8 characters for agent signing key

by Andreas Umbreit

ID: 10974 Title: Agent Bakery: require minimum length of 8 characters for agent signing key Component: agents Level: 1 Class: New feature Version: 1.7.0i1 A minimum length of 8 characters is now required for the password for newly generated agent signing keys at the agent bakery. Already existing keys or keys that get imported are not affected. However, we would always suggest to choose a strong password, as the private key of the agent signing certificate is encrypted using this very password, and a weak/short combination could introduce a vulnerability.

4 years, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1