Back to Opsview FAQ

Internal documentation only

This page has been marked as draft.

Plugin removal after Apply Changes

After upgrading to Opsview 6.9.7, users may notice that plugins placed in /opt/opsview/monitoringscripts/plugins are deleted every time Apply Changes is executed. This is expected behavior introduced in Opsview 6.8.8+ as part of enhancements to how uploaded scripts are managed. Custom scripts must now be imported through the Opsview UI, which stores them in /opt/opsview/monitoringscripts/uploaded/plugins, the only location preserved across configuration changes.

Problem Copied

Custom monitoring scripts and plugins placed in /opt/opsview/monitoringscripts/plugins are removed each time Apply Changes is triggered post-upgrade to Opsview 6.9.7. This can lead to broken service checks and confusion during post-upgrade validation or monitoring setup.

In the backend, the Opsview controller forcibly synchronizes monitoring scripts and clears the plugins/ directory, which does not retain manually added files. This behavior is by design as of version 6.8.8+.

Possible cause(s) Copied

Root Cause 1: Scripts were manually added to /opt/opsview/monitoringscripts/plugins rather than being imported through the Opsview web UI, which handles placement in the correct persistent directory.

Root Cause 2: Users were unaware of the behavioral change introduced in Opsview 6.8.8 and carried over in 6.9.x, where the plugins/ directory is overwritten during Apply Changes to ensure controller consistency.

Possible solution(s) Copied

Solution Root Cause 1: Use the Import Plugin option in the Opsview web UI to add any custom scripts. This ensures they are stored in /opt/opsview/monitoringscripts/uploaded/plugins/, which is preserved during Apply Changes. Re-run Apply Changes to validate retention.

❗Avoid placing scripts manually via the command line into the plugins/ directory, as these will not persist and are removed by design.

Solution Root Cause 2: Review the Opsview 6.8.x release notes and Apply Changes documentation to understand the new script management behavior. Update any relevant SOPs, deployment automation, or internal tooling to align with this change.

["Geneos"] ["FAQ"]

Was this topic helpful?