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".
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.
ID: 11186
Title: Fixed some wrong displayed parameters for hosts if cmc is used
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
If cmc is used as core, the default host check command is smart ping, not ping as shown before.
Also the normal and retry check interval for host checks is 6 seconds, not 1 minute.
Note: This was only a display error and didn't affect correct execution.
ID: 11037
Title: Fixed NoneType error in case of missing permissions
Component: Notifications
Level: 1
Class: Bug fix
Version: 1.7.0i1
If the user, used for login, has to few permissions in servicenow, the
notification could fail with:
"TypeError: 'NoneType' object has no attribute '__getitem__'".
>From now on, a better error message will be shown.
Details about the needed permissions where added to the help text
of the notification plugin and werk #7201.
ID: 10993
Title: Diagnostics: New WATO mode for diagnostic analysis purposes
Component: WATO
Level: 2
Class: New feature
Version: 1.7.0i1
In order to improve error analysis there's a new WATO mode {{Diagnostics}}.
With this new mode you can collection some general information about the
Checkmk server and version. Details can be found on the {{Diagnostics}} page.
In the future this mode will be extended with specific diagnostics elements,
eg. information about local files.
This mode will help you to analyse error situations. Another purpose is to have
an interface for collecting information for our support, your customers or
simply for your own analysis.
The diagnostics information are stored within tar files in the folder
{{var/check_mk/diagnostics}}. At the moment maximal five of these tar files are
stored. This number is not configurable.
There's also a command line option for collecting diagnostics information and
collects information about the Checkmk site where it's executed.
C+:
cmk --create-diagnostics-dump [OPTIONS]
C-:
Note: The {{Diagnostics}} mode does not solve any problems. It's just a data
collection which consolidates some commands and therefore facilitates error
analysis.
ID: 11161
Title: df check returns separate sub-results in order to provide distinct WARN/CRIT marker
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
The df check returned one monolithic check result containing usage, trend and
inode information but only containing one WARN/CRIT marker for all elements.
This change breaks the df result into separate sub-results each providing
WARN/CRIT markers.
ID: 10538
Title: Improved livestatus query performance on some gui pages/features
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.7.0i1
The following performance improvements are only noticable on systems with 10k+ hosts.
<ul>
<li>The Agent Bakery "Automatic updates" overview page is now renderered faster</li>
<li>The hostname autocompletion feature now udpates faster</li>
<li>Using Host- and Servicecheck command filters now costs less CPU time</li>
</ul>
ID: 11077
Title: Web API: Fix set_hosttags call when any rule uses "one of" or "none of" tag conditions
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
It was not possible to set_hosttags via WEBAPI call in case any rule uses the
operators "one of" or "none of" in host tag conditions. This caused an
"Unhandled exception: ... NotImplementedError" when trying to execute the
"set_hosttags" API call.
ID: 11032
Title: Fixed consideration of local 'old style' perfometer customizations
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
If a perfometer definition like:
<b>perfometers["check_mk-mem.linux"] = my_perfometer</b>
is set in '~/local/share/check_mk/web/plugins/perfometer" and the
key is already present within the builtin perfometers, the local definition had
no effect.
>From now on, such local customizations are taken into account.
ID: 11157
Title: AWS EC2 Limits
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
This werk fixes some small bugs in the monitoring of AWS EC2 limits (check
aws_ec2_limits). Before this werk, depending on the configuration, the
corresponding service might have been discovered for both the host running
the special agent and for one of the EC2 instances. Now, the service is
only discovered for the host running the special agent and all limits are
consistently reported there. Also, some default upper levels have been
adjusted to the latest AWS defaults.
This werk is incompatible. Users have to re-discover the services of affected
hosts.