Checkmk werks level1 June 2019

checkmk-werks-lvl1@lists.checkmk.com

21 participants
163 discussions

Checkmk Werk 7709: Removed remaining, deprecated 'check{name, type}' argument in discovery functions which led to crashes during discovery

by Simon Jess

ID: 7709 Title: Removed remaining, deprecated 'check{name,type}' argument in discovery functions which led to crashes during discovery Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1

5 years, 4 months

Checkmk Werk 7482: mk_mysql: More consistent naming of instances

by Moritz Kiemer

ID: 7482 Title: mk_mysql: More consistent naming of instances Component: Checks & agents Level: 1 Class: Bug fix Version: 1.6.0i1 The naming of different mysql instances has been simplified. The item names of the monitored instances are now given by the corresponding sockets (e.g. an instance using the socket "/var/run/mysql.sock" will be called "/var/run/mysql.sock"). If no socket can be determined, only one instance will be monitored, using the default name "mysql". Previously as a third attempt the <tt>--user=</tt> option found in the output of <tt>ps -fww -C mysqld</tt> has been used as instance name. This is not longer considered. The determination of the sockets themselves is unchanged: If no sockets are listed in the config file, the socket is determined by the <tt>--socket=</tt> option found in <tt>ps -fww -C mysqld</tt>. If you are monitoring mysql instances that do not use the default item name "mysql", a rediscovery is required.

5 years, 4 months

Checkmk Werk 7351: Removed "checks" configuration variable

by Lars Michelsen

ID: 7351 Title: Removed "checks" configuration variable Component: Core & setup Level: 2 Class: Bug fix Version: 1.6.0b1 The Checkmk configuration variable <tt>checks</tt> was removed It was used in hand configured Checkmk configurations in the early days. This variable was never configurable by WATO. In case you configured Check_MK only via WATO you will not be affected by this issue. In case you need to migrate your configuration, you could move the configuration to the WATO ruleset "Classical Active and Passive Monitoring Checks".

5 years, 4 months

Checkmk Werk 7760: Web API: Changed format of rules in get_ruleset/set_ruleset

by Lars Michelsen

ID: 7760 Title: Web API: Changed format of rules in get_ruleset/set_ruleset Component: WATO Level: 2 Class: Bug fix Version: 1.6.0b1 The Web API calls <tt>get_ruleset</tt> and <tt>set_ruleset</tt>, that were added with #4699 in Checkmk 1.5 have been changed in an incompatible way. If you use these API calls in your scripts, you will have to change these script to be compatible with Checkmk 1.6 and newer. The change was caused by the change of the internal rule data structure, which is described in detail in #7352. The API calls now work with the internal rule format with the difference that the <tt>host_folder</tt> condition is removed from the rules returned by <tt>get_ruleset</tt> and automatically added to the rules that are written with <tt>set_ruleset</tt>.

5 years, 4 months

Checkmk Werk 7353: Changed format of host tags in hosts.mk configuration files

by Lars Michelsen

ID: 7353 Title: Changed format of host tags in hosts.mk configuration files Component: Core & setup Level: 2 Class: Bug fix Version: 1.6.0b1 The internal data format of the Checkmk host and cluster definitions, normally configured via WATO "Hosts" pages has been changed. If you only use WATO for configuring Checkmk this change will not be relevant for you, since the data format will be changed automatically during update to 1.6x. Have a look at #7352 for further information on the update mechanism. In case you edit hosts.mk (or other .mk) files manually or via script to define the <tt>all_hosts</tt> or <tt>clusters</tt> configuration options, you will likely have to change your scripts or at least the configuration files. A host definition with it's tags in the old format looks like this: F+:hosts.mk all_hosts += [ "my-host|cmk-agent|prod|lan|piggyback|no-snmp", ] F-: The first element is the host name and the tags of the host are listed in the same string, separated via pipe characters. There is no information about the tag group the configured tag is related with. The new structure looks like this: F+:hosts.mk: all_hosts += [ "my-host", ] host_tags["heute"] = { "agent": "cmk-agent", "criticality": "prod", "networking": "lan", "piggyback": "piggyback", "snmp_ds": "no-snmp", } F-: In the <tt>host_tags</tt> dictionary the keys are the tag groups (as defined in WATO) and the values are the tags configured for each group.

5 years, 4 months

Checkmk Werk 7352: Changed format of rules in rules.mk configuration files

by Lars Michelsen

ID: 7352 Title: Changed format of rules in rules.mk configuration files Component: Core & setup Level: 2 Class: Bug fix Version: 1.6.0b1 The internal data format of the Checkmk rules configured via WATO on the "Host- & Service parameters" pages has been changed. If you only use WATO for configuring Checkmk this change will not be relevant for you, since the data format will be changed automatically during update to 1.6x. In case you edit rules.mk (or other .mk) files manually or via script, you will likely have to change your scripts. The format changes was needed to make more flexible rule conditions possible. The new conditions for 1.6 (select multiple choices of a tag group and labels) have not been added yet. They are nearly ready and will be added in one of the next beta releases. The automatic update mentioned before is done using the command <tt>cmk-update-config</tt> in the site. It's invoked during the <tt>omd update</tt> execution and currently simply loads all folder, host, tag and ruleset configuration files, executes the transform logic and saves again, just like you would do when working in WATO. In case your scripts created an "old style" WATO configuration file in an 1.6 site you could execute <tt>cmk-update-config</tt> another time, which would load, convert and save the configuration file. However, a better approach would be to update your scripts to write the configuration files in the new format. In Checkmk a ruleset is represented by a list of rules. In the past these rules were represented by tuples with different elements (depending on the ruleset type). The structure of a rule has now been changed to a dictionary. An example from the sample configuration: Old ruleset: F+:rules.mk host_contactgroups = [ ('all', [], ALL_HOSTS, { 'description': u'Put all hosts into the contact group "all"' } ), ] + host_contactgroups F-: New ruleset: F+:rules.mk host_contactgroups = [ { 'condition': { 'host_folder': '/' + FOLDER_PATH }, 'value': 'all', 'options': { 'description': u'Put all hosts into the contact group "all"' } }, ] + host_contactgroups F-: This shows the rough structure of the new format. Inside the condition dictionary you can have multiple optional keys which trigger different host / service filters in Checkmk. The following examples of the <tt>condition</tt> dictionary are not covering all possible combinations, but should give you and idea of the new condition format. If you want to have a more detailed look, have a look at the tests below <tt>tests/unit/cmk/utils/rulesets/</tt> or create rules with WATO and have a look at the resulting rules.mk. <h2>Explicit host name conditions</h2> If you want to make a rule match on the hosts named <tt>host1</tt> and <tt>host2</tt>, you may use a condition like this: F+:rules.mk "condition": { "host_name": ["host1", "host2"]}, } F-: <h2>Exclude hosts</h2> Match all hosts except <tt>HOST1</tt> and <tt>HOST2</tt>: F+:rules.mk "condition": { "host_name": { "$nor": ["HOST1", "HOST2"] }, }, F-: <h2>Regex on host names</h2> Make a rule match on hosts by using a regular expression: F+:rules.mk "condition": { "host_name": [{ "$regex": "abc[12]" # It's a case sensitive prefix match },] }, F-: <h2>Match using host tags</h2> Match all hosts that are <tt>test</tt> systems connected via <tt>wan</tt> F+:rules.mk "condition": { "host_tags": { "criticality": "test", "networking": "wan", }, } F-: <h2>Combine different conditions<h2> Match test hosts that start with <tt>abc</tt>: F+:rules.mk "condition": { "host_name": [{"$regex": "abc"}], "host_tags": { "criticality": "test", }, } F-: <h2>Service rulesets: Match on the description</h2> Same syntax as <tt>host_name</tt> condition, e.g. match all services starting with <tt>CPU</tt>: F+:rules.mk "condition": { "service_description": [{"$regex": "CPU"}], } F-:

5 years, 4 months

Checkmk Werk 7761: New livestatus columns tags and labels

by Lars Michelsen

ID: 7761 Title: New livestatus columns tags and labels Component: Livestatus Level: 1 Class: New feature Version: 1.6.0b1 The hosts and services tables now have two new columns named <tt>tags</tt> for fetching the configured tags and <tt>labels</tt> for fetching the configured labels. In the past one had to use the columns <tt>custom_variables</tt> to get the TAGS custom variable of a host and parse the value of this variable to get the configured host tags. This approach also had some limitations in terms of filtering by tags. The tag group information was totally missing here. The new <tt>tags</tt> column can be parsed and filtered with less trouble. If you do livestatus queries on the tags we recommend to use these fields. One example for a livestatus query and the resulting data: C+: OMD[heute]:~$ lq "GET hosts\nColumns: tags\nOutputFormat: json" [[{"snmp_ds":"no-snmp","address_family":"no-ip","networking":"lan","tcp":"tcp","site":"heute","piggyback":"piggyback","criticality":"prod","agent":"cmk-agent"}]] C-: The filtering can be done just like for other dictionary style columns.

5 years, 4 months

Checkmk Werk 7762: Aux tag IDs and tag group IDs need to be unique now

by Lars Michelsen

ID: 7762 Title: Aux tag IDs and tag group IDs need to be unique now Component: WATO Level: 1 Class: Bug fix Version: 1.6.0b1 In previous versions it was possible to configure auxiliary tags with an ID that was also used as tag group ID. This resulted in name conflicts and subtile inconsistencies in different situations. To prevent these problems Checkmk now enforces these IDs to be unique.

5 years, 4 months

Checkmk Werk 7763: Introduce labels as host and service properties

by Lars Michelsen

ID: 7763 Title: Introduce labels as host and service properties Component: Core & setup Level: 2 Class: New feature Version: 1.6.0b1 In addition to existing mechanisms like host tags and host custom attributes that can be used to define custom host properties we have now added the labels. The labels are similar to the host tags, but not work exactly in the same way. A major difference is, that tags are based on a predefined collection of tags (tag groups, tag ids) in Check_MK. Labels are more flexible and can be created ad-hoc. The explicit labels attribute is inherited from folders to hosts. Each object may add a set of labels on it's own to the effective labels. A label has the format <tt>key:value</tt>. For example <tt>os:windows</tt>. Each host can have only one value per key. In case folders and hosts define a value for the same key, the value next to the host will win. The rulesets "Host labels" and "Service labels" can be used to assign labels to hosts and services in addition to the labels configured using the host attribute. Thes ruleset make it possible to assign lables to hosts and services based on tags and other host / service conditions. Labels can be created dynamically during runtime. Host labels can be discovered using the HW/SW inventory. To realize this a new HW/SW inventory plugin has been added that works on a generic "<<<labels>>>" section (see #7336). The first agents that produce this section are the Kubernetes, AWS and Azure special agents. They creates the label sections for all kind of objects that are monitored by Checkmk. This makes Checkmk automatically import the labels configured in the target systems. Depending on the source of a label it is now colorized in different ways to make the origin of the label transparent to the user. The effective labels of hosts and service sare currently visible on WATO "Parameters of X" page, mainly for diagnose. The labels are available on the HW/SW inventory page and can be used as painter, sorter and filter in the status views and reports. The painters have been added to the host and service detail views. The labels can currently not be used in rule conditions. This will be added in one of the next beta releases.

5 years, 4 months

Checkmk Werk 7166: Agent Bakery now supports systemd

by Andreas Umbreit

ID: 7166 Title: Agent Bakery now supports systemd Component: agents Level: 1 Class: New feature Version: 1.6.0i1 Until now, it was necessary to have xinetd installed on a host system in order to setup the CheckMK Agent coming from the agent bakery automatically. The baked .rpm and .deb installation packages will now fall back to install the Agent as a systemd-service, if no xinetd is available on the host. With this change, the baked agent package equals the vanilla agent package in its installation behavior.

5 years, 4 months

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 June 2019