Do I need to update the Auvik collector?

For both the Windows and virtual collectors, Auvik automatically updates the collector software on a regular basis. These updates are completed during the periodic maintenance windows.

Auvik also automatically upgrades and patches the underlying Ubuntu OS (operating system) on Ubuntu-based OVA and BASH versions of the collector. If a restart is required to complete the upgrade, it will be executed on the next programmed maintenance window.

No further action is required on the end users’ part to keep the Auvik collector up to date, unless you’re explicitly instructed by Auvik Support to take action.

How do I know which version my collector is running?

If you’d like to confirm which version the collector is currently on, you can do so by following the steps below:

Virtual Collector

• Connect to the virtual collector VM to bring up the collector console
• The current collector version will be displayed near the top of the screen next to Version:

Windows Collector

• Open a command prompt as administrator
• Navigate to the folder where the Auvik service was installed (e.g. C:\auvik)
• Open the collector console using the command AuvikAgentService -console
• The current collector version will be displayed near the top of the screen next to Version:

Docker Collector

To check whether a Docker-based Auvik collector is running, you’re basically verifying two things: (1) the container is up, and (2) it’s actually connected to Auvik.

1. Check if the container is running

On the host where you deployed the collector:

docker ps

Look for a container with a name/image related to Auvik (often something like auvik-collector).

• If you see it listed → it’s running
• If not, check stopped containers:

docker ps -a

2. Inspect container status

Get more detail:

docker inspect <container_name_or_id>

Look for:

• "Status": "running"
• "Restarting": false

3. Check logs for activity

Even if it’s “running,” it might not be healthy:

docker logs <container_name_or_id>

You want to see:

• Successful startup messages
• No repeated errors
• Evidence it’s communicating outbound

4. Verify in Auvik UI (most important)

Log into Auvik and go to:

Admin → Collectors

Check:

• Collector shows as online
• Last check-in time is recent
• No alerts about collector offline

If it’s not showing:

• It may not be registered correctly
• Networking/firewall could be blocking it

5. Quick network sanity check

Collectors need outbound connectivity. From the host:

curl https://api.auvik.com

If that fails, the collector won’t connect.

Common pitfalls

• Container running but not registered → wrong activation key
• Running but offline in Auvik → firewall/DNS issue
• Constant restarts → config or resource issue (docker logs will show this)

To view current and previous Product Releases, see Product News and Updates.