Results SNMP

Description

Stores snmptraps exceptions and snmptraps traces into the runtime database.
Update trace statuses in the snmptrapstrace table in the opsview database.
Needs access to the Mysql Database to store data.
Can be run independently or on the orchestrator server
Input is from snmp-traps-exception-queue, which then inserts data into the runtime and opsview database.

Dependencies

What is required to run:

Access to Database and opsview-messagequeue. Please make sure core-utils and Messagequeue are installed, configured and running before attempting to run the results-snmp process.

You will also need to ensure the mysql client binary is installed.

Installation

Refer to Advanced Automated Installation.

Configuration

Config file location is /opt/opsview/resultssnmp/etc/resultssnmp.defaults.yaml

snmp_traps_exception_queue: The message-queue configuration to receive SNMP trap messages.
runtime_database: Configuration for the Opsview runtime database.
opsview_database: Configuration for the Opsview configuration database.
registry: Connection configuration for the Registry.
logging: Component logging configuration.

Management

Configuration

DPKGs

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-resultssnmp.conf

RPMs

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-resultssnmp.conf

Service Administration

As root, start, stop and restart the service using:

/opt/opsview/watchdog/bin/opsview-monit <start|stop|restart> opsview-resultssnmp