Checkmk werks level1 July 2017

checkmk-werks-lvl1@lists.checkmk.com

10 participants
97 discussions

Check_MK Werk 4802: mk_jolokia: Can now be configured to use the local machine's FQDN to access Jolokia

by Konstantin Büttner

ID: 4802 Title: mk_jolokia: Can now be configured to use the local machine's FQDN to access Jolokia Component: Checks & agents Level: 1 Class: New feature Version: 1.5.0i1 Previously, the Jolokia server could be configured via an IP address or an explicit FQDN. When using HTTPS on a large number of devices, configuring "localhost" or 127.0.0.1 would lead to certificate errors unless one configured the FQDN for each host individually. This is unreasonably tedious, and can be avoided using this feature.

6 years, 9 months

Check_MK Werk 5022: Fixed timperiod history calculation

by Sven Panne

ID: 5022 Title: Fixed timperiod history calculation Component: Livestatus Level: 1 Class: Bug fix Version: 1.5.0i1 The parsing of the monitoring history had a bug, expecting an incorrect "TIMEPERIOD_TRANSITION:" instead of the correct "TIMERPERIOD TRANSISION:", which could lead to incorrect availibility calculations later (when the Nagios core is used).

6 years, 9 months

Check_MK Werk 5047: EC views: Fixed "Events of host X" views of unrelated events

by Lars Michelsen

ID: 5047 Title: EC views: Fixed "Events of host X" views of unrelated events Component: Event Console Level: 1 Class: Bug fix Version: 1.5.0i1 When clicking on the host name of an unrelated event (one that has no host in the monitoring core) the target page was not showing any event since Check_MK 1.4. The events are now correctly filtered by the original event host instead of the host name of the found core host.

6 years, 9 months

Check_MK Werk 5046: Site specific globals: Highlight setting icon of sites having modified settings

by Lars Michelsen

ID: 5046 Title: Site specific globals: Highlight setting icon of sites having modified settings Component: WATO Level: 1 Class: New feature Version: 1.5.0i1

6 years, 9 months

Check_MK Werk 5045: Custom icons and actions: Add macros for getting URL encoded values

by Lars Michelsen

ID: 5045 Title: Custom icons and actions: Add macros for getting URL encoded values Component: Multisite Level: 1 Class: Bug fix Version: 1.5.0i1 The macros $HOSTNAME_URL_ENCODED$, $SERVICEDESC_URL_ENCODED$ and $HOSTADDRESS_URL_ENCODED$ have been added to get the values of the existing macros in URL encoded format.

6 years, 9 months

Check_MK Werk 5041: Removed NAGVIS_URLS OMD config option

by Lars Michelsen

ID: 5041 Title: Removed NAGVIS_URLS OMD config option Component: Other Components Level: 1 Class: Bug fix Version: 1.5.0i1 The "omd config" option NAGVIS_URL which could be used to make the NagVis icons link to different GUIs has been removed because all CMK environments use the CMK GUI. A hook for this is not needed. In case you need to customize your NagVis URLs you can still do it with the NagVis configuration.

6 years, 9 months

Check_MK Werk 5044: LDAP: Active Directory connection try to discover the nearest DC now

by Lars Michelsen

ID: 5044 Title: LDAP: Active Directory connection try to discover the nearest DC now Component: Multisite Level: 1 Class: New feature Version: 1.5.0i1 The LDAP connection of the Check_MK GUI is now using the configured LDAP server to detect the nearest Domain Controller of the current domain. Speaking to the nearest domain controller will increase the performance of the LDAP sync. The discovery is done like this: <ol> <li> A connection is established with the configured server. Normally this is the DNS name of the AD domain. For this connection a "random DC" is used. In fact the given name is locally resolved using DNS and one answered IP is picked. </li> <li> The authentication with the default credentials is done. </li> <li> The AD site of the local system is detected. This is done by gathering the local IP subnets and searching the AD sites for these subnets. </li> <li> The first DC of the found AD site is used instead of "server". </li> </ol> In case the detection does not work the "server" that has been handed over to this function is used. When you experience errors with this enable debug logging for LDAP (Global Settings > User Interface > Logging > LDAP) and check out the <tt>var/log/web.log</tt> for details.

6 years, 9 months

Check_MK Werk 5069: Choose correct owner for report schedule entry when creating a new one

by Mathias Kettner

ID: 5069 Title: Choose correct owner for report schedule entry when creating a new one Component: Reporting & Availability Level: 1 Class: Bug fix Version: 1.5.0i1 When you create a new entry for the report scheduler and you are in the <tt>admin</tt> role then you can select the owner of this entry. But the dialog would default to the user name being the first in the alphabet rather then to your own name. This led to confusion and has now been fixed. The problem showed up after adding an <tt>automation</tt> user per default, which starts with the character <tt>a</tt> and this is most times the first in the list.

6 years, 9 months

Check_MK Werk 4984: aix_service_packs: Cleaned up mixture of the latest and all past service packs

by Simon Betz

ID: 4984 Title: aix_service_packs: Cleaned up mixture of the latest and all past service packs Component: Checks & agents Level: 1 Class: Bug fix Version: 1.5.0i1 Previously the latest service pack was displayed as a single row below {{Service Packs}}. Separated the latest service pack from all past ones.

6 years, 9 months

Check_MK Werk 5042: Removed export of WATO folder permissions to NagVis

by Lars Michelsen

ID: 5042 Title: Removed export of WATO folder permissions to NagVis Component: WATO Level: 1 Class: Bug fix Version: 1.5.0i1 In previous versions it was possible to export the WATO folder permissions of each user to NagVis. This was only used for maps that are named exactly like the WATO folder name. If you don't have such NagVis maps you are not affected by this change. This feature has never been documented officially, It was disabled by default and could be enabled with the global setting "Export WATO folder permissions". When having a large amount of users (1000+) and/or a bigger folder hierarchy while having the global setting enabled this lead to a huge performance impact when editing several things in WATO (users, roles, groups, ...) and during activation of changes. In case you really used this feature, you now need to configure the permissions manually e.g. by defining contact groups and giving them permissions on the NagVis maps (via WATO).

6 years, 9 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 July 2017