Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15912 discussions

Check_MK Werk 2678: LDAP: New sync plugin: Groups to custom user attributes

by Lars Michelsen

ID: 2678 Title: LDAP: New sync plugin: Groups to custom user attributes Component: Multisite Level: 1 Class: New Feature Version: 1.2.7i3 The new LDAP sync plugin can be used to set custom user attributes based on the group memberships in LDAP. This plugin can be used to set custom user attributes to specified values for all users which are member of a group in LDAP. If a user is not a member of a group, the attribute will be left at it's default value. When a single attribute is set by multiple groups and a user is member of multiple of these groups, the later plugin in the list will override the others.

8 years, 11 months

Check_MK Werk 2677: Fixed duplicate Event Console reload in distributed setups

by Lars Michelsen

ID: 2677 Title: Fixed duplicate Event Console reload in distributed setups Component: Event Console Level: 1 Class: Bug Fix Version: 1.2.7i3 When activating WATO changes, Check_MK was trying to reload Event Consoles running on remote sites twice which lead to errors like this: Error: Internal automation error: Cannot connect to event daemon via /omd/sites/AAA/tmp/run/mkeventd/status: [Errno 104] Connection reset by peer

8 years, 11 months

Check_MK Werk 2658: logwatch: unacknowledged messages exceeding the max size are now dropped, even if they were already stored due to a previous bug

by Sebastian Herbord

ID: 2658 Title: logwatch: unacknowledged messages exceeding the max size are now dropped, even if they were already stored due to a previous bug Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.2.7i3 A previous modification to the logwatch check caused the internal message buffer (var/check_mk/logwatch) to become bloated, causing high cpu load and memory usage. This change now auto-corrects those files for those affected.

8 years, 11 months

Check_MK Werk 2621: check_http: Can now be configured to check via IPv6

by Lars Michelsen

ID: 2621 Title: check_http: Can now be configured to check via IPv6 Component: Checks & Agents Level: 1 Class: New Feature Version: 1.2.7i3

8 years, 11 months

Check_MK Werk 2674: Added native support for monitoring via IPv6

by Lars Michelsen

ID: 2674 Title: Added native support for monitoring via IPv6 Component: Core & Setup Level: 2 Class: New Feature Version: 1.2.7i3 Check_MK is now providing native support for monitoring IPv6 and even dual-stack hosts. This has been implemented in a clean and straight forward way. For each host you can choose which address family shal be used for communication with this host. By default Check_MK is still using only IPv4, but now you can change it to IPv6 for monitoring IPv6 only hosts. In WATO this is done by configuring the host attribute <i>IP Address Family</i>. You can even configure one host to be monitored via IPv4 and IPv6 at the same time. In this situation you need to decide which of the both address families is the primary one. The primary address family is the one which is used for regular monitoring tasks (communication with the agent or SNMP). The secondary address family is only being pinged by default. For the secondary address family a dedicated PING service named (PING v4 or PING v6) is added to the dual-stack hosts. By default the primary address family is IPv4 for all dual-stack hosts. In WATO this can be changed by configuring the rule set <i>Primary IP address family of dual-stack hosts</i>. In some cases you want to perform active checks to check the avilability of a service, e.g. HTTP, using both IPv4 and IPv6. For this case you can add two active checks to the dual-stack host, one having IPv6 enabled and one without having it enabled for using IPv4. But each active check needs to support IPv6 on its own. For the moment the only check working vith IPv6 is <tt>check_http</tt>. This is the default and recommended way for monitoring dual-stack hosts. You use one address family for monitoring the whole system and the other one is just being pinged. Note: If you use the Check_MK Enterprise Edition togehter with the Micro Core, the Smart PING mechanism is not used for IPv6 hosts at the moment. This mechanism has a slightly slower performance, but if you don't have too many IPv6 hosts, this should be OK for the beginning. The basic implementation for IPv6 monitoring has been done. But there are several components in the Check_MK environment left which need to be extended to be fully compatible with IPv6. Some of them are: LI: Parent scanning (check_mk --scan-parents) LI: WATO - Host-Diagnose LI: WATO - Most active checks LI: Event Console LI: Notification Forwarding LI: Livestatus Proxy LI: Several active checks LI: Most special agents LI: The Check_MK Appliance

8 years, 11 months

Check_MK Werk 2676: cisco_asa_failover: Failover state is not treated as warning state anymore

by Lars Michelsen

ID: 2676 Title: cisco_asa_failover: Failover state is not treated as warning state anymore Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.2.7i3 The Cisco ASA cluster is operating as expected and in practice, it does not really matter which of the cluster members is the primary one. So the failover state, where the secondary device is the active one, is not treated as warning anymore.

8 years, 11 months

Check_MK Werk 2657: windows agent: fixed failure to resolve named performance counters

by Sebastian Herbord

ID: 2657 Title: windows agent: fixed failure to resolve named performance counters Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.2.7i3 The problem occured when there were very many performance counters on the system.

8 years, 11 months

Check_MK Werk 2675: checkpoint_connections checkpoint_packets: Fixed wrong discovered services on non checkpoint devices

by Lars Michelsen

ID: 2675 Title: checkpoint_connections checkpoint_packets: Fixed wrong discovered services on non checkpoint devices Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.2.7i3

8 years, 11 months

Check_MK Werk 2673: SNMP-Traps: Fixed translation of OIDs which are parts of trap values

by Lars Michelsen

ID: 2673 Title: SNMP-Traps: Fixed translation of OIDs which are parts of trap values Component: Event Console Level: 1 Class: Bug Fix Version: 1.2.7i3 Some traps send SNMP OIDs as values of traps which were not translated correctly in the past. For example default SNMPv2 traps had a non-translated numeric OID in the "Application" field of the events. This has now been changed to be translated too. Please note: If you already have created rules which refer to the numeric OIDs while having trap translation enabled, you will need to update the rules.

8 years, 11 months

Check_MK Werk 2622: postfix_mailq: Fixed exception when postfix is installed but not configured properly

by Lars Michelsen

ID: 2622 Title: postfix_mailq: Fixed exception when postfix is installed but not configured properly Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.2.7i3

8 years, 11 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1