Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15953 discussions

Check_MK Werk 8647: cmk-update-agent: Fixed certificate verification issues in case openssl tools are not available

by Lars Michelsen

ID: 8647 Title: cmk-update-agent: Fixed certificate verification issues in case openssl tools are not available Component: agents Level: 1 Class: Bug fix Version: 1.4.0i3 When communicating via HTTPS with the update server, the cmk-update-agent script needs to verify the certificates of the server. The allowed certificates are stored at <tt>/var/lib/check_mk_agent/cas</tt>. In this directory there need to be the certificates (.pem files) and symlinks named with the "subject hashes" of the certificates. In previous versions these symlinks were created by the <tt>c_rehash</tt> command which is not available on all plaftforms. We have changed that now to use the python OpenSSL bindings (if available) and fallback to the c_rehash command only in case they are not available.

7 years, 7 months

Check_MK Werk 8648: PDF exports of graph collections show host/service in graph titles

by Lars Michelsen

ID: 8648 Title: PDF exports of graph collections show host/service in graph titles Component: Reporting & Availability Level: 1 Class: Bug fix Version: 1.4.0b1

7 years, 7 months

Check_MK Werk 8639: Fixed broken agent update status view

by Lars Michelsen

ID: 8639 Title: Fixed broken agent update status view Component: agents Level: 1 Class: Bug fix Version: 1.4.0i3 The agent update status view was unusable (Failed with the error "TypeError (%d format: a number is required, not NoneType)").

7 years, 7 months

Check_MK Werk 8640: Graph collection: PDF exports respect the choosen time range now

by Lars Michelsen

ID: 8640 Title: Graph collection: PDF exports respect the choosen time range now Component: metrics Level: 1 Class: Bug fix Version: 1.4.0i3 In previous versions the PDF exports of graph collections did always output PDFs with a 4 hour time range.

7 years, 7 months

Check_MK Werk 8641: Views: Time range selected by panning is respected in PDF exports now

by Lars Michelsen

ID: 8641 Title: Views: Time range selected by panning is respected in PDF exports now Component: metrics Level: 1 Class: New feature Version: 1.4.0i3

7 years, 7 months

Check_MK Werk 8642: Reworked logging configuration of the Check_MK Microcore

by Lars Michelsen

ID: 8642 Title: Reworked logging configuration of the Check_MK Microcore Component: cmc Level: 1 Class: New feature Version: 1.4.0i3 The logging configuration of the Check_MK Microcore has been reworked to be configured in a single setting. The log levels have been unified for all these log domains. Thes configuration options have been deprecated: <ul> <li><tt>cmc_log_level</tt>: Logging</li> <li><tt>cmc_livestatus_debug</tt>: Logging of Livestatus queries</li> <li><tt>cmc_debug_alerts</tt>: Logging of the alert processing in the core</li> </ul> The attribute <tt>log_level</tt> has been removed from <tt>cmc_log_cmk_helpers</tt> which is now only used to toggle the debug mode of the Check_MK helpers. The new option is <tt>cmc_log_levels</tt> (Logging of the core). The incompatibility is that, if you have configured custom log leves with the options mentioned above before, they are not effective anymore. You will have to set the log levels again using the new option. In most cases it should be no problem that the log levels are reset, because they are mostly only used for a short time during debugging actions.

7 years, 7 months

Check_MK Werk 8643: Web API: New API for fetching graph data

by Lars Michelsen

ID: 8643 Title: Web API: New API for fetching graph data Component: metrics Level: 1 Class: New feature Version: 1.4.0i3 The raw data of the Check_MK graphs can now be fetched via the Web API. The new action is named <tt>get_graph</tt>. The request object is structured like this: C+: { "specification": [..., ...], "data_range": { "time_range" : [..., ...], } } C-: The specification is using the Check_MK internal graph specification format. The first element is the specification type (<tt>template</tt>, <tt>custom</tt> or <tt>explicit</tt>. The structure of the second element depends on the type. Please take a look at the examples below to get an idea of it. The time range is given in two unix timestamps, the start time and the end time. For example this command can be used to fetch the first graph of the Check_MK service of the host myhost123: C+: # curl "http://mycmkserver/mysite/check_mk/webapi.py?action=get_graph&_username=aut…" -d 'request={"specification": ["template", {"service_description": "Check_MK", "site": "mysite", "graph_index": 0, "host_name": "myhost123" }], "data_range": {"time_range": [1480653120, 1480667520]}}' C-: The answer may look like this: C+: { "result": { "step": 60, "start_time": 1480653120, "end_time": 1480667520, "curves": [ { "color": "#87f058", "rrddata": [null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, 0.05, 0.059, 0.0423333, 0.0488333, 0.0413333, 0.0573333, 0.0515, 0.05, 0.05, 0.05, 0.05, 0.058, 0.052, 0.0578333, 0.0365, 0.0453333, 0.0576667, 0.0525, 0.05, 0.0573333, 0.0526667, 0.0428333, 0.0471667, 0.05, 0.05, 0.05, 0.05, 0.05, 0.05, 0.05, 0.05, 0.0436667, 0.0526667, 0.06, 0.06, 0.054, 0.05, 0.0558333, 0.0541667, 0.0556667, 0.049, 0.0455, 0.0553333, 0.0493333, 0.04, 0.0451667, 0.05, 0.05, 0.05], "line_type": "stack", "title": "CPU time in user space" }, ] }, "result_code": 0 } C-: This command is used to fetch the data of a custom graph named <tt>custom_graph_1</tt>: C+: # curl "http://mycmkserver/mysite/check_mk/webapi.py?action=get_graph&_username=aut…" -d 'request={"specification": ["custom", "custom_graph_1"], "data_range": {"time_range": [1480653120, 1480667520]}}' C-:

7 years, 7 months

Check_MK Werk 8637: Check_MK Notification Spooler is now always enabled

by Lars Michelsen

ID: 8637 Title: Check_MK Notification Spooler is now always enabled Component: Notifications Level: 2 Class: New feature Version: 1.4.0i3 The notification spooller will be enabled on all sites and can not be disabled anymore via "omd config".

7 years, 7 months

Check_MK Werk 8638: Fixed broken notifications when Check_MK notification spooler not enabled (regression since 1.4.0i2)

by Lars Michelsen

ID: 8638 Title: Fixed broken notifications when Check_MK notification spooler not enabled (regression since 1.4.0i2) Component: Notifications Level: 3 Class: Bug fix Version: 1.4.0i3 When updating an existing site to 1.4.0i2 or 1.4.0i2p2 while not having the "Check_MK notification spooler" enabled via "omd config", the notification system stopped sending notifications. The background is that the default notification mechanism had been changed from direct delivery to asynchronous delivery. And this was done even when the notification spooler, which is responsible for delivering the asynchronous notification, was disabled. The notifications are not lost, they have simply not been processed. In case you are affected, there should exist one file for each notification that has been created but was not delivered below <tt>var/check_mk/notify/spool/</tt>. To fix this issue just install the new version. After the update all notification will be sent out. In case you want to supress the stuck notifications, you can go to the directory mentioned above and remove the <tt>.mk</tt> files in this directory before starting the site again. To make it work for you with the existing versions, you can execute "omd config" and go to "Distributed Monitoring > MKNOTIFYD" and enable this option. After starting the site again, all your notifications will be processed and are sent to the users.

7 years, 7 months

Check_MK Werk 8634: Fixed broken config when configuring "Parameters for linux_remote" ruleset

by Lars Michelsen

ID: 8634 Title: Fixed broken config when configuring "Parameters for linux_remote" ruleset Component: alerts Level: 2 Class: Bug fix Version: 1.4.0i2 This fixes this error after configuring a rule for this ruleset when executing Check_MK commands: Cannot read in configuration file /omd/sites/heute/etc/check_mk/conf.d/wato/rules.mk: name 'alert_handler_parameters' is not defined

7 years, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1