Internal documentation only
This page has been marked as draft.
Expected Behavior of Service Check with a New Custom Plugin
The error encountered below during the service check test is expected, as the check is not yet in use by any host. In the latest version of Opsview, this is the expected behavior.
After assigning the updated check with your recent script to a host and applying the changes, the check now works as expected and no longer throws any errors.
-
In this case, I disregarded the initial error since the service check had not yet been assigned to the host. I then selected the check to be used by the host, submitted the changes, and apply changes again on UI.
-
After performing the above step, the service check no longer throws an error—either during testing or in the UI Troubleshoot tab—since it is already assigned to the host.
In conclusion, since you updated the script to be compatible base on this documention: https://docs.itrsgroup.com/docs/opsview/current/configuration/service-checks-and-host/active-checks/index.html#administering-plugins-in-opsview-monitor, it is now expected to work.