We use cookies to ensure that we give you the best experience on our website.  Visit our Privacy Policy to learn more. If you continue to use this site, we will assume that you are okay with it.

Your choices regarding cookies on this site.
Your preferences have been updated.
In order for the changes to take effect completely please clear your browser cookies and cache. Then reload the page.

Werk #7482: mk_mysql: More consistent naming of instances

ComponentChecks & Agents
Titlemk_mysql: More consistent naming of instances
Date2019-05-22 14:59:29
Checkmk EditionCheckmk Raw Edition (CRE)
Checkmk Version1.6.0b1
LevelTrivial Change
ClassBug Fix
CompatibilityIncompatible - Manual interaction might be required

The naming of different mysql instances has been simplified. The item names of the monitored instances are now given by the corresponding sockets (e.g. an instance using the socket "/var/run/mysql.sock" will be called "/var/run/mysql.sock"). If no socket can be determined, only one instance will be monitored, using the default name "mysql".

Previously as a third attempt the --user= option found in the output of ps -fww -C mysqld has been used as instance name. This is not longer considered.

The determination of the sockets themselves is unchanged: If no sockets are listed in the config file, the socket is determined by the --socket= option found in ps -fww -C mysqld.

If you are monitoring mysql instances that do not use the default item name "mysql", a rediscovery is required.