SQL Server

What does the SQL Server connector do?

The SQL Server connector attempts to execute a SQL query (select 1) and logs a failure if there is an error during execution. It ensures that the rows returned are closed and returning success or failure, thus updating monitoring.


How to Monitor A SQL Server on the One Platform

To set up monitoring for SQL Server on the platform, follow these steps:

  1. Go to the product application where you want to add SQL Server as a dependency in the platform.

  2. Click on the “Products” menu and select the desired product card.

  3. Then, click on the name of the specific application where you want to configure SQL Server monitoring.

  4. Look for the section called “External Dependencies,” usually located just below the latency graph of the application.

  5. To add an already registered dependency, type the name of the
    dependency in the search field and select it when it appears in the
    list.

  6. If SQL Server is not yet registered as a dependency, click on the green button with a plus (+) symbol to add a new dependency.

 

Click “Add” and a modal will
appear allowing you to name the database and select the Environment. In
the “Check type” field, choose the option “DB,” and in the “Method”
field, select “SQL Server.” After selecting the method, a field for the
Healthcheck URL will appear.

 

Below is an example of string for SQL Server:

ex: sqlserver://USER:PASSWORD@HOST?database=DB

 

Note: For security reasons, it is
not permitted to enter an IP in the healthcheck field. To monitor an IP,
you need to enter it in a secret and use it in healthcheck

What does the SQL Server connector do?

The SQL Server connector attempts to execute a SQL query (select 1) and logs a failure if there is an error during execution. It ensures that the rows returned are closed and returning success or failure, thus updating monitoring.


How to Monitor A SQL Server on the One Platform

To set up monitoring for SQL Server on the platform, follow these steps:

  1. Go to the product application where you want to add SQL Server as a dependency in the platform.

  2. Click on the “Products” menu and select the desired product card.

  3. Then, click on the name of the specific application where you want to configure SQL Server monitoring.

  4. Look for the section called “External Dependencies,” usually located just below the latency graph of the application.

  5. To add an already registered dependency, type the name of the
    dependency in the search field and select it when it appears in the
    list.

  6. If SQL Server is not yet registered as a dependency, click on the green button with a plus (+) symbol to add a new dependency.

 

Click “Add” and a modal will
appear allowing you to name the database and select the Environment. In
the “Check type” field, choose the option “DB,” and in the “Method”
field, select “SQL Server.” After selecting the method, a field for the
Healthcheck URL will appear.

 

Below is an example of string for SQL Server:

ex: sqlserver://USER:PASSWORD@HOST?database=DB

 

Note: For security reasons, it is
not permitted to enter an IP in the healthcheck field. To monitor an IP,
you need to enter it in a secret and use it in healthcheck