The Opsview Freshness Checker purpose is to calculate if a servicecheck result is stale, then to mark it as stale and act according to the servicecheck configuration. If the the freshness type option is set to set stale the results are also sent to the results exchange via the message queue. This process run once a minute.
This component requires access to the opsview and runtime MySQL database and to the Message Queue. Please make sure that these components are configured install and running before starting the freshness-checker.
You will also need to ensure the
mysql client binary is installed.
Refer to Advanced Automated Installation.
We ship the opsview-freshchecker with its default configuration, which can be modified or overridden by the user.
- default setting:
- custom setting example:
- user settings:
Default settings are restored on upgrade/installation, user settings are left as defined by the user. The setting files follow the YAML file format, setting are stored on a <setting_name>:
The custom setting example contains an example on how to override default value.
master_database_connection: The connection to the master database server.
opsview_database_name: The name of the Opsview configuration database.
runtime_database_name: The name of the Opsview runtime database.
dispatcher_queue: The message-queue configuration to send freshness messages.
registry: Connection configuration for the Registry.
logging: Component logging configuration.
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:
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.
As root, start, stop and restart the service using:
/opt/opsview/watchdog/bin/opsview-monit <start|stop|restart> opsview-freshnesschecker