Connecting to Veeam Availability Console (VAC)

We now have a connection to the Veeam Availability Console (VAC) API as a featured integration within BrightGauge so you can create dashboards and reports. Here is a quick document to help you get set up with BrightGauge and Veeam VAC.

We recommend (but do not require) that a separate, dedicated user is created for use in BrightGauge. A separate user will ensure the integration continues to function normally when individual user accounts are deactivated or edited.


Step 1 - Add Veeam VAC datasource to your account

Log in to your BrightGauge account

If you have not created an account yet, go here to get started.


Once you have logged in:

New Accounts

From the Overview page, a popup will show up to help you with setting up your account. Click on the "Add a Datasource" button:


Existing Accounts

Go to the Overview page (to access click on the BrightGauge logo on the top left-hand corner).


Click on the green "Add a new Datasource" button towards the bottom right of the page (next to the list of your existing datasources):


Or, click on the "Data" menu on the top right-hand corner of the screen, and select "Datasources" from the drop-down menu:


Click on the “Backup” category and then click on the "Veeam VAC" icon:



Step 2 - Authorize Veeam VAC in BrightGauge

You now need to provide the URL, port, username and password for your Veeam admin account to provide BrightGauge a way to retrieve data on your behalf.

  1. Enter the API subdomain and port of your VAC server.

  2. Enter the username and password for the account that will retrieve data.

    Again, we recommend (but do not require) that a separate, dedicated account be created for use with the BrightGauge integration. This should ensure the integration continues to function normally when normal user accounts are deactivated.



Step 3 - Test connection

  1. Click the Test Connection button.


  2. If you see the Test succeeded banner message, click Save.

    Important Note: Be careful to verify that the username or password field inputs were not overwritten by a password manager with the wrong credentials after the Test connection step.

If you have any trouble with authentication or have any other questions, please reach out to support. For additional information, please check out our support forums at

Was this article helpful?
0 out of 0 found this helpful