- 5 minutes to read

Configuring the Database Monitoring Agent

Empower your monitoring strategy with the Nodinite Database Monitoring Agent. This guide walks you through every step of configuration, from initial setup to advanced tuning for SQL Server, Azure SQL, and PostgreSQL databases.

✅ Centralized configuration for all your database monitoring needs
✅ Effortless remote management and fine-tuning
✅ Support for SQL Server, Azure SQL, and PostgreSQL
✅ Granular control with categories and settings

Info

This guide provides instructions for configuring the Nodinite Database Monitoring Agent.

Note

The Monitoring and the remote configuration is available if you first install and create the initial Monitoring Agent Configuration for the Database Monitoring Agent. First-time users start here.

Remote Configuration

As a Nodinite Administrator, click the 'Configuration' button to open a modal and configure the agent:
RemoteConfiguration
Example: The Configuration button in the Monitoring Agent Configuration administration page

You can adjust configurations on the Resource via the Action button if the Monitor View has the Remote Actions feature enabled.

SQL Server Instance

Click the Add button to add a new SQL Server Instance to monitor. Repeat as needed for each instance.
Add SQL Server Monitoring Configuration
Add a new SQL Server monitoring configuration

SQL Server Configuration Entry

Click the Accordion to expand the connection configuration
SQL Server Accordion
Expand to configure SQL Server connection details

SQL Server General Tab

For each SQL Server connection, set the following properties:
SQL Server General Tab
General tab for SQL Server configuration

  • Enabled – Enable monitoring for this SQL Server configuration
  • Configuration name – Unique name for this connection
  • Description – Short description for this configuration
  • Connection String – The connection string for this configuration (default: 'Data Source=localhost;Initial Catalog=MSDB;Trusted_Connection=True;Connection Timeout=10;Encrypt=true;TrustServerCertificate=true;'). See also Connection String.
Data Source=localhost;Initial Catalog=MSDB;Trusted_Connection=True;Connection Timeout=10;Encrypt=true;TrustServerCertificate=true

You can fine-tune each SQL Server instance for different monitoring aspects. The following Categories are available:

Category Description Configuration
SQL Backups Monitor your backups Configuration
SQL Blocking Monitor SQL for blocking processes Configuration
Size Checks Monitor data and log file size usage Configuration
SQL Jobs Monitor SQL Agent job performance Configuration
SSIS Monitor SSIS Packages and Projects Configuration
SQL Statements Run custom SQL statements to monitor business data

Add Azure SQL Databases

Click the Add button to add a SQL Azure Database to monitor. Provide one entry per SQL Database. Each entry appears as a Resource in Monitor Views.
6
Add a new Azure SQL Database configuration

Configure the added server

5
Configure the added Azure SQL server

Click the Accordion to expand the content.

  • Enabled – Enable monitoring for this configuration
  • Configuration name – Unique name for this connection
  • Description – Short description for this configuration
  • Connection String – The connection string for this configuration (default: 'Data Source=localhost;Initial Catalog=MSDB;Trusted_Connection=True;Connection Timeout=10;Encrypt=true;TrustServerCertificate=true;'). The Database Monitoring Agent uses this to connect to Azure SQL. See also Connection String.

Below is an example using a SQL User. The Connection String is encrypted in the Settings.json file.

Server=tcp:example.database.windows.net,1433;Persist Security Info=False;User ID=sqlusr-admin;Password={your_password};MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=False;Connection Timeout=30;

Azure SQL Database Configuration Entry

You can fine-tune each Azure SQL database for different monitoring aspects. The following Categories are available:

PostgreSQL Database Configuration Entry

Click the Add button to add a PostgreSQL Database to monitor. Provide one entry per Database. Each entry appears as at least one Resource in Monitor Views.
7
Add a new PostgreSQL Database configuration

Configure the added PostgreSQL Database

8
Configure the added PostgreSQL Database

Click the Accordion to expand the content.

  • Enabled – Enable monitoring for this configuration
  • Configuration name – User-friendly name for this configuration
  • Description – (Optional) Description of this configuration
  • Connection String – The Database Monitoring Agent uses this to connect to PostgreSQL.
Server=123.databases.appdomain.cloud;Port=31902;Database=ibmclouddb;User Id=ibm_cloud_456;Password=789;SSLMode=Prefer;Trust Server Certificate=true;
  • Application ID – Any user-defined ApplicationId from the Application tab.

PostgreSQL Categories

You can fine-tune each PostgreSQL database for different monitoring aspects. The following Categories are available:

Settings tab

Within the Settings tab, provide details that determine the operation of the Database Monitoring Agent.

Settings tab
Settings tab for advanced configuration

Environment

Set the name of the target environment (e.g., TEST, QA, PROD). This is a standard feature shared with all Monitoring Agents.

Debug

Enable or disable the Debug flag for additional file logging as needed. This is a common feature shared with all Monitoring Agents. Default is unchecked.

Culture Information

The Culture Information setting determines how time-based data from this agent is presented in the Web Client/Web API.

Save

Click 'Save' or 'Save and close' to persist your changes. The new settings and thresholds are evaluated on the next synchronization.
Save and Close buttons
Example of the Save options

Note

The delay in presenting the new evaluated state depends on the synchronization interval set for the monitoring agent. Click the Sync Now button to force an immediate synchronization.

Save and close saves and closes the dialogue.
Cancel closes the dialogue without saving changes.

Add Database Monitoring Agent Configuration

After you install the Database Monitoring Agent, provide Nodinite with connection details so the Monitoring Service can start monitoring.

No monitoring or other configuration of the Database Monitoring Agent can be performed before the steps outlined below have been completed.

Configuration Steps

  1. Add and configure a new Monitoring Agent Configuration
    • Connection information is available in the README.txt file in the installation folder
  2. Use the Remote Configuration feature to configure the agent. Details are at the beginning of this guide.
  3. Create one or more self-service enabled Monitor Views that include the selected Resources provided by the Database Monitoring Agent according to business needs.
  4. Fine-tune specific settings directly on Resources using Remote Actions.

Next Step

Add or manage a Monitoring Agent Configuration
Add or manage Monitor View

Install Database Monitoring Agent
Monitoring Agents
Applications