This component is built using python, which will read opsview netflow stats from the netflow queue and push them on to the database. This package works as follows
The handler will have a single process running continuously reading from the queue. Once it has found a message it will try to add to the database following the rule below.
- Find in the database if the host id and timestamp exist, if not create one
- If the data exist, compare it and the maximum data should be added to the database by doing and update.
Access to the database and opsview-messagequeue. Please make sure Core Utils and Messagequeue are installed, configured and running before attempting to start the
Refer to Advanced Automated Installation.
The config file is located at: /opt/opsview/resultsflow/etc/resultsflow.defaults.yaml
- flow_queue: The message-queue configuration to receive flow messages.
- runtime_database: Configuration for the Opsview runtime database.
- 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 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.
As root, start, stop and restart the service using:
/opt/opsview/watchdog/bin/opsview-monit <start|stop|restart> opsview-resultsflow
Updated almost 4 years ago