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.
Servicecheckname if type of message is service check.
Sends a message with the above data to the results sender queue for processing.
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.
Refer to [Advanced Automated Installation](🔗).
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
Results and acknowledgements can be submitted into Opsview Monitor by writing into the `
/opt/opsview/var/results.sock` pipe file in the following format:
Unknown hosts or services will be logged into syslog.
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
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.
### Service Administration
As root, start, stop and restart the service using: