Configuration Files section is where the user can view all the servers that have been registered to be monitored whenever there is a configuration file change. The servers listed shall consist of its database configuration files including all those files that are affected by its directive.
This section is where you can learn what you can do with
Configuration Files and the database that is supported for configuration file management.
Here you should see a tree view of all configuration files from all servers as seen by the ConfigFiles agents:
When a configuration file is selected on the left-side navigation tree, all of the configuration lines can be visualized in two modes:
- Visual Mode – A more modern guided approach with the variable name, description, value and delete button for every configuration entry.
- Text Mode – Standard text editor view with syntax highlighting.
Option Group Management
To add a MySQL option group, click on
mariabackup, etc. This basically translates to a group name enclosed with square brackets as in MySQL configuration, for example:
[mysql] ... [mysqld] ... [client] ... [mysqladmin] ...
You can always switch to the Text Mode to check if the group addition is in the right place. Click on the
To delete the whole MySQL option group, click on the
Configuration Option Management
In MySQL, a configuration option must belong to a configuration group. For example, the
max_connections configuration option should be under the
[mysqld] group, while the
socket configuration option can co-exist in multiple configuration groups like
[client] and so on. It is important to specify the right configuration option under the right option group to get it loaded properly. To manage the option group, see Option Group Management.
By default, ConfigFiles will parse all existing configuration files on the host and visualize them here. To add a new configuration option, click on the
Click on the
Whenever ConfigFiles has detected a new version of a configuration file, you will see the
ConfigFiles tracks changes of the corresponding configuration file every time it is written. For every tracked change, you can perform two optional actions:
- Revert to this version – Activates this version of the configuration file.
- Compare with current version – Shows a summary of changes between two versions in a side-by-side comparison style. Green lines indicate new addition while the red lines indicate the last removal.