ITRS Opsview Cloud Documentation

SNMP Traps

SNMP Traps will:

Dependencies Copied

No dependencies.

Installation Copied

This is deployed when installing Opsview Monitor.

See MIBs for SNMP Traps and Gets to add your MIBs that are required for translating SNMP Traps.

Management Copied

Configuration Copied

DPKGs Copied

Watchdog service files are now managed by the package manager, removing the package would leave the watchdog service file behind with a .save extension. Purging the package will remove it. The package manager managed config file:


RPMs Copied

Watchdog service files are now managed by the package manager. When removing the package, if the files listed have been modified by the user before; they will be left behind after rpmsave extension has been added to them. When upgrading the package, if the files listed have been modifed by the user before; the modified file on the disk will remain and the new config file from the upgrading package will be written to the disk with the rpmnew extension. Users will have to:

  1. Manually restore the file with the rpmsave extension.
  2. Rename the rpmnew to the config file name if they want to use the new config for the package.

Service administration Copied

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

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

Known limitations Copied

snmptrapd not monitored by watchdog Copied

Even though the snmpd is monitored by opsview-watchdog and will be restarted when that process unexpectedly dies, the snmptrapd process is not monitored. This means it is possible for snmptrapd to have an exceptional failure that is not automatically recoverable. This is a limitation in the opsview-watchdog software and is a rare event.

Trap handling within clustered nodes Copied

See Known issues for a manual workaround using the opsview_collector_enable_snmp parameter.

["Opsview On-premises"] ["User Guide"]

Was this topic helpful?