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 Sender
The Results-Sender forwards results on from the collector to the Orchestrator. It also provides a backup ability to store durable messages in case the connection to the Orchestrator is down.
Dependencies Copied
The Results-Sender requires access to the MessageQueue and Registry. Please make sure these packages are installed, configured and running before attempting to start the opsview-resultssender process.
Installation Copied
Refer to Advanced Automated Installation.
Configuration Copied
The user configuration options should be set in /opt/opsview/resultssender/etc/resultssender.yaml. Default values are shown in /opt/opsview/resultssender/etc/resultssender.defaults.yaml, but changes should not be made here since the file will get overwritten on package update.
The following options can be set:
messages_ttl: Messages older than this will be discarded by the results sender.results_in_queue: The message-queue configuration to receive results.results_cache_queue: The message-queue configuration to send/receive messages when the out queue connection is down.results_out_queue: The message-queue configuration to send results.results_live_queue: The message-queue configuration to send messages to results-live (Acknowledgements and Downtime messages).results_dispatcher_out_queue: The message-queue configuration to send messages to results-dispatcher for populating additional information.registry: Connection configuration for the Registry.logging: Component logging configuration.
Additional configuration Copied
The results-cache-queue is defined to have an additional messages_ttl_secs setting that will remove messages from that queue.
This is set using the queue additional params (for example, params: message_ttl_secs=1800)
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-resultssender.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-resultssender.conf
Service administration Copied
As root, start, stop and restart the service using:
/opt/opsview/watchdog/bin/opsview-monit <start|stop|restart> opsview-resultssender