These docs are for v6.6. Click to read the latest docs for v6.7.


## Description

The Opsview AutoMonitor Manager is used for discovering devices set up on your network for more easily adding monitoring of devices into Opsview

## Dependencies

It uses the python binary provided in `opsview-python3`.

## Installation

This component is deployed alongside the Scheduler component when installing Opsview Monitor.

## Configuration

The user configuration options should be set in `/opt/opsview/automonitormanager/etc/automonitormanager.yaml`. Default values are shown in `/opt/opsview/automonitormanager/etc/automonitormanager.defaults.yaml`, but changes should not be made here since the file will get overwritten on package update.

The following options can be set:

  • scan_timeout: The maximum time allowed for a complete scan (seconds).

  • master_probe_weighting: The AutoMonitor Manager asks each collector to assess its suitability for performing a scan. If the collector is able to connect to the target, it reports the time taken to connect. In order to favour running scans on collectors, this weighting is added to the time reported by the Master Monitoring Server (milliseconds).

  • logging: General logging config.

## Management

### Configuration

#### DPKGs

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 files are as follows

  • /opt/opsview/watchdog/etc/services/opsview-automonitormanager.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-automonitormanger.conf

### Service Administration

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