Checkmk werks level1 June 2020

checkmk-werks-lvl1@lists.checkmk.com

9 participants
64 discussions

Checkmk Werk 11188: Fixed non functional "discovery state" filter

by Ronny Bruska

ID: 11188 Title: Fixed non functional "discovery state" filter Component: Multisite Level: 1 Class: Bug fix Version: 1.7.0i1 The filter "discovery state", used in views like "Unmonitored services", had no effect. From now on, the selected values are filtered correctly.

4 years, 2 months

Checkmk Werk 11191: Fixed misleading snmp error message

by Ronny Bruska

ID: 11191 Title: Fixed misleading snmp error message Component: Multisite Level: 1 Class: Bug fix Version: 1.7.0i1 In most cases, the reason for errors is not a missing system description OID but missing firewall policies, misconfigured SNMP, wrong community, etc.

4 years, 2 months

Checkmk Werk 11082: jobs: Exit codes of jobs can now be mapped to states

by Lars Michelsen

ID: 11082 Title: jobs: Exit codes of jobs can now be mapped to states Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 In previous versions, all exit codes except 0 were evaluated as CRITICAL. Now it is possible to determine the evaluation of the exit codes in the check parameters.

4 years, 2 months

Checkmk Werk 11189: if.include: Better visualization of unicast and non-unicast packets

by Ronny Bruska

ID: 11189 Title: if.include: Better visualization of unicast and non-unicast packets Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 The graph "Packets" was showing unicast/non_unicast packets as area and stacked. This way the non-unicast traffic was difficult to identify. From now on unicast and non-unicast packets are shown as line.

4 years, 2 months

Checkmk Werk 11190: if.include: Fixed description and help text for average option for used bandwidth

by Ronny Bruska

ID: 11190 Title: if.include: Fixed description and help text for average option for used bandwidth Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 The option "Average values" in ruleset "Network interfaces and switch ports" was renamed to "Average values for used bandwidth" and moved under the related option. Also the help text was adjusted.

4 years, 2 months

Checkmk Werk 11187: if.include: Added broad- and multicast packet rate monitoring

by Ronny Bruska

ID: 11187 Title: if.include: Added broad- and multicast packet rate monitoring Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 Broadcast and multicast packet rates can now be monitored. You can define levels within the WATO rule "Network interfaces and switch ports". To react only on long-time changes also averaging can be set.

4 years, 3 months

Checkmk Werk 11215: Extension of the monitoring of UCS C-Series Rack Servers

by Joerg Herbel

ID: 11215 Title: Extension of the monitoring of UCS C-Series Rack Servers Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 This werk extends the special agent for monitoring UCS C-Series Rack Servers to output information about LEDs and fault objects. It also adds two new checks which monitor this data. The check ucs_c_rack_server_led monitors the colors of all found LEDs and also provides their names and operational states. The check ucs_c_rack_server_faultinst monitors fault objects such as degraded batteries. It provides both a summary of all faults as well as detailed information about each fault.

4 years, 3 months

Checkmk Werk 11153: Averaging of single-core CPU utilization

by Joerg Herbel

ID: 11153 Title: Averaging of single-core CPU utilization Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 This werk extends the following checks by an option to compute averaged single-core CPU utilizations (previously, this was only possible for the total CPU utilization): hr_cpu, huawei_switch_cpu, kernel.util, tplink_cpu, winperf_processor.util. In particular, this option is now available for Linux/UNIX (kernel.util) and Windows systems (winperf_processor.util). To activate the averaging, use the option "Averaging for single cores" of the rules "CPU utilization on Linux/UNIX" or "CPU utilization for simple devices" (depending on the check). Note that, as described in the documentations of these rules, this option only has an effect when used together with the sub-options "Apply single-core levels" or "Graphs for averaged single-core utilizations".

4 years, 3 months

Checkmk Werk 11156: Monitoring of AWS RDS DBs

by Joerg Herbel

ID: 11156 Title: Monitoring of AWS RDS DBs Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 This werk fixes some issues with the monitoring of AWS RDS DBs: <ul> <li>The checks aws_rds.network_io and aws_rds.disk_io now yield correct rates.</li> <li>The services produced by the checks aws_rds.transaction_logs_usage, aws_rds.replication_slot_usage and aws_rds.agent_jobs are now discoverable, which wasn't the case before due to a bug in the AWS special agent.</li> <li>For PostgreSQL databases, the check aws_rds.replica_lag now additionally reports the Cloudwatch metric OldestReplicationSlotLag, which wasn't the case before due to a bug in the AWS special agent.</li> <li>The rule "AWS/RDS Replica lag" for the check aws_rds.replica_lag has been adjusted to allow for setting levels smaller than one second on the replication lag.</li> This werk is incompatible. Depending on the used configuration, users should delete and re-create the rules "AWS/RDS Replica lag".

4 years, 3 months

Checkmk Werk 11155: Monitoring of AWS EC2 instances

by Joerg Herbel

ID: 11155 Title: Monitoring of AWS EC2 instances Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 The checks aws_ec2, aws_ec2.cpu_credits, aws_ec2.cpu_util, aws_ec2.disk_io and aws_ec2.network_io now go stale instead of to UNKN if the corresponding EC2 instance is turned off.

4 years, 3 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 June 2020