How do I manage my collectors?

Note:The network map has been removed from this page to provide additional space during administrative tasks such as managing alerts, users, settings, and integrations. To return to your network map, simply click Home Dashboard or All Sites in the Auvik side navigation.

The Auvik Collectors page allows you to manage collectors that are responsible for discovering, monitoring, and collecting data from your networks.

From this page, you can:

• Download and deploy a new collector
• Approve a collector
• Reject a collector
• Edit collector details
• Delete collectors

You can also filter the collector list to locate specific collectors. For more information, see How to filter data in Auvik.

Best Practices

Before deploying a collector:

• Assign the collector a static IP address or DHCP reservation.
• Ensure the collector has reliable connectivity to both the monitored network and the Auvik cloud.
• Deploy collectors on stable infrastructure with adequate resources.
• Consider deploying additional collectors for redundancy or to monitor isolated network segments.

Download a New Collector

If a collector becomes unavailable due to hardware failure, operating system issues, or migration to new infrastructure, you can deploy a replacement collector.

To download a new collector:

1. Navigate to Auvik Collectors.
2. Click Add Auvik Collector.
3. Select the appropriate deployment method:

Windows

Select:

Install Collector on a Windows Device

See: How to install the Auvik collector using the Windows service

VMware Virtual Appliance

Select:

Set up Collector as a Virtual Appliance on VMware

The VMware appliance includes VMware Tools and is the recommended deployment method for VMware environments.

See: How to install the Auvik Collector using the OVA file

Linux

Select:

Create a New Virtual Machine to Run the Collector

See: How to install the Auvik collector from a bash script

Docker

Select:

Set up Collector Using a Docker Image

See: Installing the Auvik Collector as a Docker Image

Note: After deployment, newly installed collectors must be approved before they can begin monitoring.

Approve Collectors

Collectors must be approved before they can communicate with the Auvik cloud and begin monitoring networks.

To approve one or more collectors:

1. Navigate to Auvik Collectors.
2. Select the collector or collectors you want to approve.
3. Click Approve.
4. Confirm the action.

Once approved, the collector will begin discovery and monitoring activities.

Reject Collectors

Rejecting a collector prevents it from monitoring your environment.

To reject a collector:

1. Navigate to Auvik Collectors.
2. Select the collector or collectors you want to reject.
3. Click Reject.
4. Confirm the action.

Important: If the collector is still running, power it down after rejecting it. Otherwise, it may continue attempting to reconnect.

Common reasons for rejecting a collector include:

• Collector replacement
• Lab or test deployments
• Incorrect site assignment
• Retired infrastructure

Edit Collector Details

Descriptions can help identify collectors by location, purpose, or deployment type.

To edit a collector:

1. Navigate to Auvik Collectors.
2. Select the collector.
3. Click Edit.
4. Update the desired fields.
5. Click Save.

Examples of useful descriptions include:

• Calgary Datacenter Collector
• Head Office VMware Collector
• Backup Collector
• DR Site Collector

Delete Collectors

Delete collectors only when they are permanently retired and will not be reconnected.

To delete a collector:

1. Navigate to Auvik Collectors.
2. Select the collector or collectors you want to delete.
3. Click Delete.
4. Confirm the action.

Important: If a deleted collector is still powered on and connected to the network, it will automatically reappear in Auvik and require approval.

We recommend deleting only collectors that:

• Have been decommissioned
• Have been replaced by another collector
• Are permanently disconnected
• Were created accidentally

Collector Lifecycle Recommendations

When replacing a collector:

1. Deploy and approve the replacement collector.
2. Verify monitoring and discovery are functioning normally.
3. Power down the old collector.
4. Reject or delete the retired collector.

Following this process helps prevent gaps in monitoring and discovery.

Additional Information

If a collector becomes disconnected:

• Discovery stops for networks assigned to that collector.
• Device status information stops updating.
• Configuration backups stop running.
• TrafficInsights, Syslog, and other collector-based services stop receiving new data.

Monitoring resumes automatically once a collector reconnects or an alternate collector assumes responsibility for the network.