#PROCESS MONITOR LINUX UPDATE#

Update port_num bind-address username password Prints out an easy to read MySQL OMI authentication file. The password field should be entered in plain text - the password in the MySQL OMI authentication file will be Base 64 encoded.ĭeletes the specified instance by either default or by port number. Sets the default instance in the MySQL OMI authentication file. Sets whether or not the authentication file will be automatically updated on restart or update. The following table provides details on the syntax for using mycimprovauth. Running the mycimprovauth command as omsgent is recommended. The credentials file must be readable by the omsagent account. opt/microsoft/mysql-cimprov/bin/mycimprovauth The authentication file program can be found at the following location. Included with the installation of the MySQL OMI provider is a MySQL OMI authentication file program which can be used to edit the MySQL OMI Authentication file. The following table has example instance settings Descriptionĭefault instance and instance with port 3308.ĭefault instance and instance with port 3308 and different user name and password. If the instance on 3308 is bound to another address and uses the same MySQL username and password pair only the bind-address is needed, and the other properties will be inherited. For example, if MySQL instance listening on port ‘3308’ is added, the default instance’s bind-address, username, and Base64 encoded password will be used to try and monitor the instance listening on 3308. All additional instances will inherit properties set from the default instance unless they specify different values. The default instance is denoted by an instance with port 0. The MySQL OMI authentication file can define a default instance and port number to make managing multiple MySQL instances on one Linux host easier. Specifies whether to rescan for changes in the my.cnf file and overwrite the MySQL OMI Authentication file when the MySQL OMI Provider is upgraded. Password of the MySQL monitoring user encoded in Base64. MySQL user used to use to monitor the MySQL server instance. Port 0 specifies that the properties following are used for default instance.

Represents the current port the MySQL instance is listening on. The entries in the authentication file are described in the following table. (Port)=(Bind-Address), (username), (Base64 encoded Password) Authentication file formatįollowing is the format for the MySQL OMI authentication file The MySQL authentication file is stored at /var/opt/microsoft/mysql-cimprov/auth/omsagent/mysql-auth. The authentication file specifies what bind-address and port the MySQL instance is listening on and what credentials to use to gather metrics.ĭuring installation of the Log Analytics agent for Linux the MySQL OMI provider will scan MySQL my.cnf configuration files (default locations) for bind-address and port and partially set the MySQL OMI authentication file. These credentials are stored in an authentication file that's stored on the Linux agent. The MySQL OMI provider requires a preconfigured MySQL user and installed MySQL client libraries in order to query the performance and health information from the MySQL instance. MySQL user credentials must be configured so that the provider can access the MySQL Server. This provider connects to the local MySQL/MariaDB server to expose performance statistics.

If MySQL Server or MariaDB Server is detected on the computer when the Log Analytics agent is installed, a performance monitoring provider for MySQL Server will be automatically installed. Migrate to Azure Monitor agent before August 2024 to continue ingesting data. The legacy Log Analytics agent will be deprecated by August 2024.

Process monitor linux