ID: 15470
Title: sap_hana_instance_status: Fix crash during discovery
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
SAP HANA Instance Status check crashed during discovery if process
didn't have all the data required.
Now, processes with incomplete data are ignored.
ID: 15489
Title: Fix error message if limit for combined graphs is exceeded
Component: metrics
Level: 1
Class: Bug fix
Version: 2.1.0p28
If the object or metric limit of a combined graph was reached, an error like
"Problem while rendering dashboard element 4 of type combined_graph: Failed to
calculate a graph recipe." was shown.
You will now only see the information that a limit was reached.
ID: 15534
Title: Discovery service details: include host labels
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.3.0b1
The service details of the discovery check now feature a full list of new and vanished host lables.
This is consistent with the way the vanished/new services are listed.
ID: 15731
Title: Agent controller auto-registration rules: Avoid error when updating remote sites with active configuration replication
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.3.0b1
When updating the Checkmk version of a remote site with active configuration replication whose
central site had configured rules from the ruleset
<a href="https://docs.checkmk.com/master/en/hosts_autoregister.html#rule_autoregiste…">Agent controller auto-registration (Cloud Edition)</a>,
users might have ecountered errors such as
C+:
-| Exception: The configured site is not known to this site. You can only register to sites known to the central site, because the controller will only trust certificates signed by the central sites CA.
C-:
during the update. These errors can be safely ignored and will not occur anymore.
ID: 15673
Title: Logfile pattern analyzer: improve rule overview
Component: setup
Level: 1
Class: New feature
Version: 2.3.0b1
The "Logfile pattern analyzer" shows the configured "Logifle patterns" rules,
but ordered them based on the rule number. This could make it difficult to spot
for which folder the corresponding rule had been configured.
The rules are now grouped and foldable by folder, similar to other rule
overviews.
ID: 15484
Title: Fix encoding of special characters in "Move to other folder"
Component: Setup
Level: 1
Class: Bug fix
Version: 2.2.0b7
Special characters were wrongly displayed in the "Move to other folder"
dropdown. E.g. "&" as "&".
ID: 15468
Title: aws_lambda, aws_sns: Rename Lambda and SNS services
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0b7
The werk is incompatible for users that used AWS Lambda and AWS SNS services
in versions from 2.2.0b1 to 2.2.0b6.
Affected users have to rediscover services and will lose metric data of the
renamed services.
The following services have been renamed:
LI: AWS/Lambda Concurrency REGION NAME -> AWS/Lambda NAME [REGION] Concurrency
LI: AWS/Lambda Memory REGION NAME -> AWS/Lambda NAME [REGION] Memory
LI: AWS/Lambda Performance REGION NAME -> AWS/Lambda NAME [REGION] Performance
LI: AWS/SNS REGION NAME Message Number -> AWS/SNS NAME [REGION] Message Number
ID: 15467
Title: sap_hana: Enable clustering of active and passive nodes
Component: agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
Previously, we collected data only for databases in primary and
logreplay_readaccess replication modes. For other replication modes
only SAP HANA Status service was shown.
In order to enable clustering of active and passive nodes,
we now try to collect data for all replication modes and if the database
cannot be accessed, the services of that host will go to STALE.
ID: 15665
Title: OMD configuration: Avoid duplicate port allocations
Component: Site Management
Level: 1
Class: Bug fix
Version: 2.2.0b6
When creating a new site or when changing the port configurations of an existing site via <tt>omd
config</tt>, Checkmk was supposed to check for duplicate port allocations (also across multiple
sites). This mechanism was broken, which means that ports could be allocated multiple times.
Specifically, the following port settings were affected:
LI: <tt>APACHE_TCP_PORT</tt>
LI: <tt>AGENT_RECEIVER_PORT</tt>
LI: <tt>LIVESTATUS_TCP_PORT</tt>
As of this werk, when attempting to configure an already allocated port, Checkmk will increment the
port number until a free port is found.