ID: 7335
Title: Fixed broken regex based hostname translation in EC
Component: Event Console
Level: 1
Class: Bug fix
Version: 1.6.0i1
The hostname translation of the EC was broken since release of
Check_MK 1.4.0 (caused by #3687). This issue lead to dropped events
once the translation has been condifgured. The problem was visible
in the mkeventd.log in the following form:
C+:
2019-04-04 11:36:24,286 [40] [cmk.mkeventd.EventServer] Unable to parse host "HOST" ('tuple' object has no attribute 'endswith')
Traceback (most recent call last):
File "/omd/sites/snmp/lib/python/cmk/ec/main.py", line 2787, in do_translate_hostname
event["host"] = self.translate_hostname(event["host"])
File "/omd/sites/snmp/lib/python/cmk/ec/main.py", line 2768, in translate_hostname
if not regex.endswith('$'):
AttributeError: 'tuple' object has no attribute 'endswith'
C-:
ID: 7434
Title: winperf_phydisk: Optional configuration of disk io operations
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0i1
This werk adds support for the configuration of Levels for disk I/O operations
for Windows in WATO rule "Levels on disk IO (old style checks)".
CMK-1780
ID: 7122
Title: aws_ec2_limits: New check which monitors AWS/EC2 limits
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0i1
The following limits and their default levels are monitored:
<ul>
<li>VPC Elastic IP Addresses, 5</li>
<li>Elastic IP Addresses, 5</li>
<li>Rules of VPC security group, 50</li>
<li>Security Groups of VPC, 500</li>
<li>VPC security groups of elastic network interface, 5</li>
<li>Spot Instance Requests, 20</li>
<li>Active Spot Fleet Requests, 1000</li>
<li>Spot Fleet Requests Total Target Capacity, 5000</li>
<li>Total Running On-Demand Instances, 20</li>
<li>Running On-Demand Instances of different types, 20</li>
</ul>
ID: 7393
Title: mongodb_collections: New WATO rule and fixed output
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
The storage size is no longer wrongly treated as total available space,
which led to a {CRIT} state.
Users who had a rule configured for Mongo DB collections need to set
up a new one.
ID: 7254
Title: Background Jobs: Fixed bug on several job detail pages, stating the job is stuck in "initialized" phase
Component: WATO
Level: 1
Class: Bug fix
Version: 1.6.0i1
The <tt>Bake agents</tt> or <tt>Download agent output</tt> background job details pages incorrectly showed the jobstatus as initialized.
This error solely was a display bug and was caused by invalid parsing of the jobs statefile.
The actual background job was running fine.
ID: 7048
Title: mem.linux: Optional levels for corrupted memory configurable
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0i1
Previously the check status was either OK in case no RAM was corrupted or a
custom check status (default: CRIT) in case RAM was corrupted dependent on the
configuration of WATO rule Memory Swap usage on Linux, value Handle Hardware
Corrupted Error. Now it is possible to configure the WARN and CRIT levels
for the corrupted memory with the renamed WATO value Hardware Corrupted.
Existing configurations of WATO rule value Handle Hardware Corrupted Error are
converted to WATO rule value Hardware Corrupted (1, 1) for consistent behaviour.
ID: 7362
Title: AWS/RDS services: Use DB identifier instead of DB name as item; DB name may be missing or not set
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
You have to perform a re-discovery in order to create new items
and remove old items. Configured rules for these services must
also be adapted.
ID: 7253
Title: Service Discovery: No longer query data for disabled snmp checks
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
Even if a snmp check type was disabled, its relevant data was still queried from the host and discarded shortly after.
This has been fixed.