Connecting to Kaseya On Premise

This document is a step by step guide for setting up the Kaseya On Premise integration within BrightGauge.

 

Step 1 - Log in to your BrightGauge Account  

If you haven’t created an account yet, go here to get started.

 

If you are logged in with a New Account:

From the account Overview page, click on the "Add a Datasource" button:

If you are logged in with an Existing Account:

Click on the "Data" menu at the top righthand corner of the screen, and select "Datasources" from the drop down menu:

AddingANewDatasource.gif

Find the Kaseya datasource under "All" or under the appropriate category:

FindDatasource.gif

 

Whether a new or existing account, you'll come to datasource settings screen below. Leave this page open as it will be used in Step 4. You can now proceed onto the next steps.

scn_datasources_addnew_onprem_database.png

  

Step 2 - Download and Install BrightGauge Agent

Since Kaseya runs off a SQL database, you’ll need to download and configure the BrightGauge Agent. Click Download to download the agent. Documentation to help setup configure the BrightGauge Agent can be found here.  Make sure to install the BrightGauge agent on a machine somewhere within the same network as your MS-SQL database for Kaseya.  If you have issues, there are some known issues here or email support@brightgauge.com for assistance.

 

Step 3 - Create a SQL user within Kaseya database

Once the agent is up and running, you’ll now need to create a SQL user within the Kaseya database. Kaseya runs off of MS-SQL, so here’s a guide on how to do that.  Make sure to enable the user to log into the Kaseya database. The default database name should be ksubscribers.  You’ll also need to put this database name for the following step.

 

Step 4 - Configure the Datasource Settings

scn_datasources_addnew_onprem_database.png

Refer to the screenshot above and match the corresponding numbered fields:

  1. Name: A name for the connection.
  2. Agent Host: The computer on which the agent is installed.
  3. Database Internal IP/Hostname: Internal IP address or hostname for the database server (if using multiple SQL instances, use the IP or machine name followed by a backslash and then the instance name: 192.168.1.100\instance or SQLServer\instance).
  4. Database Name: The database name (e.g., cwwebapp_brightgauge).
  5. Database Internal Port: This field is for advanced SQL setups not using the default SQL port (1433). Enter the non-default port in this field. Leave BLANK if using the default SQL port (1433).
  6. Database Username: Your database username.
  7. Database Password: Your database password.

 

Step 5 - Test Connection

Once you've filled out all of the fields, make sure to test the connection.  If successful, save the connection.

Please note, a common issue we have seen clients experience is with the "AutoFill" feature in web browsers inputting the wrong the credentials for the database user field. When a test connection is successful, the page is refreshed and the autofill takes effect automatically without the user realizing. The user then selects save, accidentally saving the autofilled credentials which are incorrect. A way to prevent this issue is to open a private browsing window (or incognito window) to fill out the datasource configuration page, or simply retyping the credentials after the test connection and clicking "Save".

 

Dashboards, reports, datasets, and gauges will be added to your account after the datasource is saved. They will start syncing immediately and typically complete syncing after 20-30 minutes. 

Your Default Dashboards

  • AV Information
  • BGS - Machine Monitoring

Your Default Reports

  • Kaseya Executive Summary Report
  • Monthly Downtime Report
  • Weekly Machine Report

 

For a list of all default gauges, please visit the "Gauges" section of your account, sort by the Datasource you'd like to see and select for Default.  

For additional information, please check out our support forums at support.brightgauge.com

 

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

Comments

0 comments