About Commit Operation
Any change made within Nagios Monitoring is not effective and does not become part of your monitoring system production environment until the change is committed with the Commit option. Other components of the Commit process include Pre flight test and Backup.
Committing Configuration Changes
Pre Flight Test
Before performing a Commit operation your are advised to run a Pre flight test to check if there are any warnings you might want to fix before putting the configuration changes into production. No changes are made to the production setup when running a Pre flight test and any warnings or errors will be listed in the Nagios Pre flight test window.
From the Configuration menu option, choose Nagios Monitoring > Control > Pre flight test.
Select Continue to complete. Pre flight test data is stored in the
/usr/local/groundwork/monarch/workspacedirectory. See Docker Commands for the
execto execute a command running in a specific container.
Example workspace directory files:
Commit and Backup Operations
A Commit operation is used to update configuration changes to the Nagios configuration files which are stored in the
/usr/local/nagios/etc directory. This operation will overwrite the active Nagios configuration and restart Nagios. A Backup of the Nagios configuration files (.cfg) and a database dump of the monarch configuration database (.tar) will automatically be initiated every time a successful commit operation takes place. Backup configuration files are stored in a
/usr/local/groundwork/monarch/backup/<timestamp> directory. In addition to the Nagios configuration files and the database file the backup directory also contains the monarch annotation (.annotation) file which holds an optional backup description added at the time of backup.
- From the Configuration menu option, choose Nagios Monitoring > Control > Commit.
- In the Nagios Commit screen, you have the option to add an Annotation describing what the backup represents (which is typically either a save point before a set of changes or a full final set of changes).
- It is strongly encouraged to be very descriptive when you enter annotations which can be very helpful if you need to restore a configuration.
- Next, you have the option to Lock the backup which allows it to be saved indefinitely.
- Unlocked backups are subject to being automatically deleted when too many accumulate.
- Select Commit to overwrite the active Nagios configuration, restart Nagios, and create a backup.
Select Abort if you do not want to follow through with the commit process.
Example Nagios configuration files:
Example backup <timestamp> directory files: