Hey! These docs are for version 6.4, which is no longer officially supported. Click here for the latest version, 6.7!

# Overview

AutoMonitor allows users to quickly and effortlessly discover and import hosts into their Opsview Monitor environment. The new wizard-based functionality simplifies and automates the scanning and configuration steps providing a fast and reliable way of maintaining continuous monitoring of your changing Enterprise landscape. Discovered hosts will be imported into the `Opsview > AutoMonitor > {Scan Type} > ... ` Host Group Structure.

AutoMonitor currently supports three Express Scan technologies:

  • [Windows Express Scan](🔗)

  • [VMware vSphere Express Scan](🔗)

  • [Azure Express Scan](🔗)

## Pre-Requisites

In order to access the AutoMonitor Application and run an Express Scan, the following permissions are required:

### Opsview User Role:

  • CONFIGUREHOSTS permission defined in your Roles

  • CONFIGUREHOSTGROUPS permissions defined in your Roles

  • Access to the Opsview Host Group when running an AutoMonitor Express Scan to be able to create the Host Group Structure

  • NOT to be a tenant user.

## Host Certificates

AutoMonitor Express scans do not use certificates for host checking. However several of the service checks do use certificates for host identification checks. Refer to the `Host certificates` section of each Technology scan for more information

## Troubleshooting

### Failing Scans

If a scan fails the error will be recorded within the scan log, available via in the UI. The full error will also be recorded within `/var/log/opsview/opsview.log` on the collector performing the scan. You can see these errors by running:

#### `Host group 'Automonitor' could not be created: Parent does not exist`

This error is caused by the topmost Hostgroup having been renamed. The fix is to rename this top group back to the default of `Opsview` and retry the scan.