Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15874 discussions

Check_MK Werk 1855: esx_systeminfo: new inventory check to retrieve info about the host operating system for ESX servers

by Goetz Golla

ID: 1855 Title: esx_systeminfo: new inventory check to retrieve info about the host operating system for ESX servers Component: HW/SW-Inventory Level: 1 Class: New Feature Version: 1.2.7i1

9 years, 8 months

Check_MK Werk 1854: netscaler_tcp_conns: new check to monitor tcp connections on Citrix Netscaler Loadbalancer Appliances

by Goetz Golla

ID: 1854 Title: netscaler_tcp_conns: new check to monitor tcp connections on Citrix Netscaler Loadbalancer Appliances Component: Checks & Agents Level: 1 Class: New Feature Version: 1.2.7i1

9 years, 8 months

Check_MK Werk 1673: netapp_volumes: now able to configure levels by magic factor

by Andreas Boesl

ID: 1673 Title: netapp_volumes: now able to configure levels by magic factor Component: Checks & Agents Level: 1 Class: New Feature Version: 1.2.7i1

9 years, 8 months

Check_MK Werk 1672: Now able reclassify logwatch messages before forwarding them to the event console

by Andreas Boesl

ID: 1672 Title: Now able reclassify logwatch messages before forwarding them to the event console Component: Event Console Level: 2 Class: New Feature Version: 1.2.7i1 You are now able to apply already existing logwatch patterns to the messages which are sent to the event console. Each message can be reclassified to a different alert level and even set to IGNORED, which causes a message not to be sent to the event console. This pre-sorting might reduce the load of the event console. Keep in mind that the logwatch pattern are configured by host and the logfile name. These restrictions do also apply to the messages intented for the event console. So you can configure a logwatch pattern specifially designed for a message from a certain logfile. For example, you can reclassify any messages from a logfile access.log containing "C Login error" to "I Login error". Any message of access.log containing the "Login error" pattern will therefore get ignored and not sent to the event console.

9 years, 8 months

Check_MK Werk 1846: Keep track of changes of software and hardware

by Mathias Kettner

ID: 1846 Title: Keep track of changes of software and hardware Component: HW/SW-Inventory Level: 1 Class: New Feature Version: 1.2.7i1 The HW/SW-Inventory module now keeps tracks of changes of the hardware and software on a system: Each time an inventory is being done the outcome is being compared with the data from the last time. If a change has been detected, a copy of the previous inventory data is being stored for later reference (in <tt>var/check_mk/inventory_archive</tt>). The check <tt>HW/SW Inventory</tt> can be configured with the WATO ruleset Do hardware/software Inventory to report a WARN or CRIT state if one of hardware or software has changed. Secondly - if you are viewing details of a host - a button Inventory History brings you to a new view of the historic development of the host's hardware and software. At the beginning this button is hidden behind the [...]-button (as usual). The history shows you each point of time where at least one item of the inventory data has changed. That way you can easily keep track of new installed software, exchanged hard disks, BIOS updates and much more.

9 years, 8 months

Check_MK Werk 1525: viprinet_temp: Now uses new Temperature WATO rule

by Konstantin Büttner

ID: 1525 Title: viprinet_temp: Now uses new Temperature WATO rule Component: Checks & Agents Level: 1 Class: New Feature Version: 1.2.7i1 This check is no longer in the room_temperature group, but in the temperature group. Old rules will therefore no longer apply.

9 years, 8 months

Check_MK Werk 1671: windows agent: fixed gaps in eventlog monitoring after agent restart

by Andreas Boesl

ID: 1671 Title: windows agent: fixed gaps in eventlog monitoring after agent restart Component: Checks & Agents Level: 2 Class: Bug Fix Version: 1.2.7i1 The windows eventlog monitoring was not entirely continuous. After the agent started it determined determined the initial record number for each eventlog. Per default the start number was the last record. Thus resulted in monitoring gaps as long as the windows was not running, e.g. windows startup. With this fix, the windows agent now uses a statefile (<tt>eventstate.txt</tt>) which contains the last processed eventrecord ids for each eventlog. On startup the statefile is read and the record numbers are set accordingly.

9 years, 8 months

Check_MK Werk 1524: kentix_temp: Now supports setting levels

by Konstantin Büttner

ID: 1524 Title: kentix_temp: Now supports setting levels Component: Checks & Agents Level: 1 Class: New Feature Version: 1.2.7i1 Previously, this check only used the levels configured in the device. Now, setting own levels is possible, as well as specifying which levels have priority. As the service description and the item name has changed, re-inventory is required

9 years, 8 months

Check_MK Werk 1853: cisco_power, cisco_fan, cisco_temp_perf: fixed algorithm to determine check item for some special cases

by Goetz Golla

ID: 1853 Title: cisco_power, cisco_fan, cisco_temp_perf: fixed algorithm to determine check item for some special cases Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.2.7i1 For some Cisco switches the item name of sensors was incorrectly determined from the snmp oid "ciscoEnvMonSupplyStatusDescr". When the status description contains "Status is ..." or "PS1 ..." in the second field, this field was incorrectly included in the item name. The problem is fixed. Since the item name changes due to this fix, you need to redo a service discovery. To our knowledge this problem only affects the cisco_power check. cisco_fan and cisco_temp_perf may theorectically be affected since the same algorithm is used, but the status descriptions for these checks are different. Example: status description: "Sw1, PS1 Normal, RPS Normal", old item name: "Sw1 PS1 Normal 3036", new item name: "Sw1"

9 years, 8 months

Check_MK Werk 1873: Escaping event text of event console messages correctly in views

by Lars Michelsen

ID: 1873 Title: Escaping event text of event console messages correctly in views Component: Event Console Level: 1 Class: Security Fix Version: 1.2.7i1 Event texts of messages which have been processed by the event console and resulted in a event might contain HTML code which is now escaped correctly to prevent XSS attacks when shown in the event console views.

9 years, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1