Checkmk werks level2

checkmk-werks-lvl2@lists.checkmk.com

1 participants
1349 discussions

Check_MK Werk 8655: Changing global setting for alert handler event types is now effective

by Lars Michelsen

ID: 8655 Title: Changing global setting for alert handler event types is now effective Component: alerts Level: 2 Class: Bug fix Version: 1.4.0b2 The bug was that changing the global setting for the handled event types would not be activated by {{Activate Changes}}. The configuration for the core was not generated newly until some other settings was changed also. This has been fixed.

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

Check_MK Werk 8622: Agent Bakery: Fix broken deployment of automatic agent updater for Windows

by Lars Michelsen

ID: 8622 Title: Agent Bakery: Fix broken deployment of automatic agent updater for Windows Component: agents Level: 2 Class: Bug fix Version: 1.4.0i2 This bug affected builds of the 1.2.8 branch after 2016-09-14, including the releases 1.2.8p11 and 1.2.8p12. Agents deployed with the agent bakery of these versions do not update automatically. Redeployment to affected hosts is required.

7 years, 7 months

Check_MK Werk 8618: Fix vanished service matching criteria in alert handler rules

by Lars Michelsen

ID: 8618 Title: Fix vanished service matching criteria in alert handler rules Component: alerts Level: 2 Class: Bug fix Version: 1.4.0i2

7 years, 7 months

Check_MK Werk 8613: Fix exception when signing agent and a host once had an agent but now don't

by Lars Michelsen

ID: 8613 Title: Fix exception when signing agent and a host once had an agent but now don't Component: agents Level: 2 Class: Bug fix Version: 1.4.0i1

7 years, 7 months

Check_MK Werk 8611: Alert handlers now log success or failure to monitoring history

by Lars Michelsen

ID: 8611 Title: Alert handlers now log success or failure to monitoring history Component: alerts Level: 2 Class: New feature Version: 1.4.0i1 Alert handlers to send feedback to the monitoring core. The history of the affected host or service now gets two log entries: one for the launch of the handler, one for the termination. Also two identical alert handlers will not be allowed any longer to run in parallel. This will avoid flooding processes in case of hanging handlers.

7 years, 7 months

Check_MK Werk 8587: Do not longer put baked agents and agent update status into WATO snapshots

by Lars Michelsen

ID: 8587 Title: Do not longer put baked agents and agent update status into WATO snapshots Component: WATO Level: 2 Class: Bug fix Version: 1.4.0i1 The snapshots that WATO automatically creates on {{Activate changes}} do no longer contain the baked agents and information about the agent update status. This was considered a bug, since a replay of a WATO snapshot would also reset the update status. And the baked agent can be very large and produce large snapshots. This made {{Activate changes}} quite slow in some situations. Note: The WATO snapshots are considered to be configuration snapshots - not a replacement for a real backup!

7 years, 7 months

Check_MK Werk 8588: deb-packages: Do not remove /var/lib/check_mk_agent on package update

by Lars Michelsen

ID: 8588 Title: deb-packages: Do not remove /var/lib/check_mk_agent on package update Component: agents Level: 2 Class: Bug fix Version: 1.4.0i1 The Debian packages created by the agent bakery now no longer delete the directory <tt>/var/lib/check_mk_agent</tt> when the package is updated. It is still removed when the package is finally uninstalled.

7 years, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level2