Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15940 discussions

Checkmk Werk 15960: permissions: allow guest users Host read access on monitoring endpoints

by Checkmk werks level 1

ID: 15960 Title: permissions: allow guest users Host read access on monitoring endpoints Component: REST API Level: 1 Class: Bug fix Version: 2.3.0b1 After some security updates to the REST-API, guest users were no longer able to view host data on monitoring endpoints due to insufficient permissions. There is a differentiation between 'monitoring' and 'setup' endpoints with regards to permissions which was previously not taken into account. This werk addresses this issue by allowing monitoring read access for guest users.

1 year, 2 months

Checkmk Werk 13270: agent_ibmsvc: option -i/--modules not recognized without --accept-any-hostkey

by Checkmk werks level 1

ID: 13270 Title: agent_ibmsvc: option -i/--modules not recognized without --accept-any-hostkey Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0p8 The information regarding 'Retrieve information about...' provided for the `ibmsvc` special agent would be ignored if 'Accept any SSH Host Key' was unchecked. This change makes the information about modules be used unconditionally.

1 year, 2 months

Checkmk Werk 15258: Removed StatsGroupBy header from Livestatus protocol

by Checkmk werks level 1

ID: 15258 Title: Removed StatsGroupBy header from Livestatus protocol Component: Livestatus Level: 1 Class: New feature Version: 2.3.0b1 The StatsGroupBy header has been deprecated for almost 13 years now, just use the Columns instead.

1 year, 2 months

Checkmk Werk 15704: check_mkevents: Display of last log line configurable

by Checkmk werks level 1

ID: 15704 Title: check_mkevents: Display of last log line configurable Component: Event Console Level: 1 Class: New feature Version: 2.3.0b1 * Adapted ruleset and argument thingy

1 year, 2 months

Checkmk Werk 15831: Windows agent provides cached info for local check in piggyback

by Checkmk werks level 1

ID: 15831 Title: Windows agent provides cached info for local check in piggyback Component: Checks & agents Level: 1 Class: Bug fix Version: 2.3.0b1

1 year, 2 months

Checkmk Werk 15930: Fix warning state "password input may be echoed"

by Checkmk werks level 1

ID: 15930 Title: Fix warning state "password input may be echoed" Component: Core & setup Level: 1 Class: Bug fix Version: 2.3.0b1

1 year, 2 months

Checkmk Werk 15929: Fix wrong creation of topics on update

by Checkmk werks level 1

ID: 15929 Title: Fix wrong creation of topics on update Component: Multisite Level: 1 Class: Bug fix Version: 2.1.0p31

1 year, 2 months

Checkmk Werk 15928: Fix visibility of cloned view, dashboard and report extensions

by Checkmk werks level 1

ID: 15928 Title: Fix visibility of cloned view, dashboard and report extensions Component: Multisite Level: 1 Class: Bug fix Version: 2.3.0b1 Werk #15135 introduced the possibility to share views, dashboards and report definitions. If you cloned an installed extension and changed the configuration of the clone, opening the view, dashboard or report always showed the configuration of the extension. This has been fixed, please review your shared views, dashboards and reports if you used extensions.

1 year, 2 months

Checkmk Werk 15969: cisco_temperature: Correct warning threshold for environment temperature

by Checkmk werks level 1

ID: 15969 Title: cisco_temperature: Correct warning threshold for environment temperature Component: Checks & agents Level: 1 Class: Bug fix Version: 2.3.0b1 Currently only the threshold specified by OID 1.3.6.1.4.1.9.9.13.1.3.1.4 (ciscoEnvMonTemperatureThreshold) is considered when checking the temperature of a Cisco switch. As only one threshold is given here, it is used as both WARN and CRIT threshold, causing confusion when the device itself reports a warning state based on a warning threshold not given via this OID. Now the upper thresholds specified in OID 1.3.6.1.4.1.9.9.91.1.2.1.1 (entSensorThresholdTable) will be used as WARN and CRIT thresholds if an entry for the relevant switch can be found. For this, the threshold relation and severity will be used to determine if the threshold can be applied in Checkmk, otherwise the threshold will be ignored. If no thresholds from the entSensorThresholdTable apply, the ciscoEnvMonTemperatureThreshold is used as a fallback.

1 year, 2 months

Checkmk Werk 15903: cisco_temperature, cisco_temperature_dom: Improved check state and summary if sensor status not ok

by Checkmk werks level 1

ID: 15903 Title: cisco_temperature, cisco_temperature_dom: Improved check state and summary if sensor status not ok Component: Checks & agents Level: 1 Class: Bug fix Version: 2.3.0b1 The cisco_temperature and cisco_temperature_dom checks currently only consider sensors with the state "ok". If a sensor becomes "unavailable" or "non-operational", the check becomes "UNKNOWN" with the summary "Item not found in monitoring data". With this werk, the summary will now report the status of the sensor instead. For the "unavailable" sensor status, the check state will still change to "UNKNOWN", for "non-operational" status it will be CRIT. The discovery is not affected by this and will still only discover "ok" sensors.

1 year, 2 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1