'Apply Changes' is an important feature in Opsview Monitor as it will need to be run to put configuration changes into production.
This is the process where Opsview Monitor takes the updates to the configuration and updates the running system to include the changes made since the last time the configuration files were loaded. For example, the addition of a new Host is not made active until the Apply Changes occurs. After this process, the changes will be visible in the user interface, dashboards and more.
The Apply Changes functionality is available as a modal window anywhere in Opsview Monitor. Users with RELOADACCESS permission will be able to view a badge in the navigation bar, as shown below, if there are pending changes:
The badge will signify the number of changes pending. If the number is over 10,000, a truncated value will be shown:
You can click on the APPLY CHANGES tile or the BADGE to open the Apply Changes modal window:
This modal window will display:
the last time configuration changes were applied ('Configuration last updated:').
the number of pending changes and the users that have made them. If there are no changes to be applied, the number will be '0'. This means that no changes have been made to the Opsview Monitor software that requires a configuration file change. If there are changes to be applied, this number will be a clickable hyperlink. This clickable link will load the Audit Log and filter it so that it only shows the category 'CONFIG' from the last 'Apply Changes':
This allows you to see why changes need to be applied. By having this functionality, you can ensure that only a few users have the ability to perform this action and thus apply the changes. This is great for an ITIL environment where you want to ensure that changes are being done in a controlled manner, i.e. through the change control process and only applied on a Saturday evening within a downtime period.
You can click on the Apply changes button to start the reload process.
NOTE: if the change log system setting is enabled, you will first be asked to enter a change log message before the reload process can begin:
After entering the change log message, click on 'Save'.
A progress bar will appear to signify the number of stages left to run and display a text of what the current stage is doing, as shown below:
The progress bar is calculated based on the size of your system and the number of collectors. If the process looks like it is going to take a while, you can close the window to continue using Opsview Monitor while the Apply changes process is running.
While Opsview Monitor is applying your changes, the badge will turn into a spinning icon and you can hover over it to get more information:
If other users visit the 'Apply Changes' page while the process in progress, they will see the progress bar too.
It is impossible for two 'Apply Changes' to be triggered simultaneously.
Once the changes are successfully applied, all users with this modal window open will be presented with a screen similar to the one below:
After successfully applying changes, the page in the background behind the modal will update if appropriate.
NOTE: If you are a multi-tenant user, the views will not contain user name information.
Once the changes are applied, a backup of the Opsview Monitor configuration database is automatically stored. A Restore button will be available so you can revert back to the previous configuration should the new one be inadequate.
You may wish to 'Apply Changes' to Opsview Monitor, even if no changes are pending, in order to have the software detect that a newly added Service Check is generating graph data. By default, a Service Check that is generating graph data requires two 'Apply Changes'. The first 'Apply Changes' applies the Service Check to a Host, at which point it is executed and begins storing performance data on the file system. The second 'Apply Changes' is then required to ensure that Opsview Monitor detects these new files and begins displaying the data within graph configuration windows, and also within investigate modes, sparkline graphs and more.
If there is a failure with the Apply Changes process, the screen will show error messages for the administrator to resolve:
Also, the badge will display an error:
If the error is temporary (such as a component not running), resolve the error and then invoke Apply changes again.
NOTE: You may need to re-log into Opsview Monitor to get the appropriate session information for the badge to appear.
If your web browser is not connected to Opsview's web server, a message will appear in the Apply Changes window
Opsview Monitor will retry to connect and when successful, this message will disappear.
Note: The message may be different or it may not show at all, depending on your browser and OS, although it should always reconnect.
Symptom: Warning message: "IP 192.168.10.22 has more than 1 host associated with it: host1, host2".
Solution: This occurs because there is more than one host that resolves to the same IP address. This is allowed in normal circumstances, except when SNMP Trap type Service Checks are associated with it. The reason is that an SNMP trap will be emitted from an IP address, and if that IP is associated to multiple Hosts, then a result will be sent to all Hosts associated to that IP address. The best way to resolve is that Host-specific Service Checks (such as SNMP Trap or other hardware Service Checks) are assigned to only one Host based on that IP address.
Updated 2 years ago