Opsview 6.8.x End of Support
With the release of Opsview 6.11.0 on February 2025, versions 6.8.x have reached their End of Support (EOS) status, according to our Support policy. This means that versions 6.8.x will no longer receive code fixes or security updates.
The documentation for version 6.8.9 and earlier versions will remain accessible for the time being, but it will no longer be updated or receive backports. We strongly recommend upgrading to the latest version of Opsview to ensure continued support and access to the latest features and security enhancements.
Results Forwarder
Receives Passive results from outside of the system in 4k Blocks from a separately installed source, such as NRD or NSCA.
- Parses the result and extract the following information out of it.
- Execution type.
- Current state.
- Output.
- Timestamp.
- Hostname.
- Servicecheckname if type of message is service check.
- Sends a message with the above data to the results sender queue for processing.
Dependencies Copied
The Results-Forwarder requires access to the MessageQueue and Registry. Please make sure these packages are installed, configured and running before attempting to start the results forwarder process.
Installation Copied
Refer to Advanced Automated Installation.
Configuration Copied
The user configuration options should be set in /opt/opsview/resultsforwarder/etc/resultsforwarder.yaml. Default values are shown in /opt/opsview/resultsforwarder/etc/resultsforwarder.defaults.yaml, but changes should not be made here since the file will get overwritten on package update.
The following options can be set:
results_fifo: Location of the results FIFO. Default is/opt/opsview/var/results.sock.resultssender_queue: The message-queue configuration to send results.registry: Connection configuration for the Registry.logging: Component logging configuration.
Submitting results Copied
Results and acknowledgements can be submitted into Opsview Monitor by writing into the /opt/opsview/var/results.sock pipe file. This can be used for submitting passive checks.
Entries should be written in the following format:
[<timestamp>] PROCESS_SERVICE_CHECK_RESULT;<host_name>;<svc_description>;<return_code>;<plugin_output>
[<timestamp>] PROCESS_HOST_CHECK_RESULT;<host_name>;<return_code>;<plugin_output>
[<timestamp>] ACKNOWLEDGE_HOST_PROBLEM;<host_name>;<sticky>;<notify>;<persistent>;<author>;<comment>
[<timestamp>] ACKNOWLEDGE_SVC_PROBLEM;<host_name>;<svc_description>;<sticky>;<notify>;<persistent>;<author>;<comment>
Unknown hosts or services will be logged into syslog.
Management Copied
Configuration Copied
DPKGs Copied
Watchdog service files are now managed by the package, doing a remove would leave the watchdog service file behind with a .save extension. Purging the package will remove it. The package managed config files are as follows
/opt/opsview/watchdog/etc/services/opsview-resultsforwarder.conf
RPMs Copied
Watchdog service files are now managed by the package. Any modifications will be saved at upgrade and remove processes with the .rpmnew and .rpmsave extensions correspondingly.
opt/opsview/watchdog/etc/services/opsview-resultsforwarder.conf
Service administration Copied
As root, start, stop and restart the service using:
/opt/opsview/watchdog/bin/opsview-monit <start|stop|restart> opsview-resultsforwarder