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:
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 a new SQL Server monitoring configuration
SQL Server Configuration Entry
Click the Accordion to expand the connection configuration
Expand to configure SQL Server connection details
SQL Server General Tab
For each SQL Server connection, set the following properties:
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 – SQL Server connection string (uses Microsoft.Data.SqlClient with modern TLS defaults)
Data Source=localhost;Initial Catalog=MSDB;Trusted_Connection=True;Connection Timeout=10;Encrypt=True;TrustServerCertificate=True
Dev/test with self-signed certificate
Tip
Need help with connection strings? See the comprehensive SQL Server Connection Strings guide for certificate validation, AOAG configuration, troubleshooting, and security best practices.
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.
Example: Add Azure SQL Database monitoring configuration.
Configure the added server
Next, configure the added Azure SQL server:
Example: Configure Azure SQL Database connection details.
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 – Azure SQL connection string (uses Microsoft.Data.SqlClient with modern TLS defaults)
Azure SQL example with SQL authentication:
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;
Tip
Need help with Azure SQL connection strings? See the comprehensive SQL Server Connection Strings guide, specifically the Azure SQL Managed Instance section for authentication, encryption settings, troubleshooting, and security best practices.
Note
The Connection String is encrypted in the Settings.json file.
Azure SQL Database Configuration Entry
You can fine-tune each Azure SQL database for different monitoring aspects. The following Categories are available:
- Azure SQL Statements – Run custom SQL statements to monitor business data
- Azure - SQL Size Checks – Monitor file usage (data, no transaction log)
PostgreSQL Database Configuration Entry
Configure PostgreSQL database monitoring with connection strings, custom SQL statements, and remote configuration for proactive database health tracking.
Info
For complete PostgreSQL configuration details including connection string parameters, SSL settings, and monitoring categories, see the comprehensive PostgreSQL Configuration guide.
Quick reference:
- PostgreSQL SQL Statements – Run custom SQL statements to monitor business data
Settings tab
Within the Settings tab, provide details that determine the operation of the Database Monitoring Agent.
- Environment
- Debug
- Culture Information - This feature is being deprecated in future releases
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.
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
- Add and configure a new Monitoring Agent Configuration
- Connection information is available in the
README.txtfile in the installation folder
- Connection information is available in the
- Use the Remote Configuration feature to configure the agent. Details are at the beginning of this guide
- Create one or more self-service enabled Monitor Views that include the selected Resources provided by the Database Monitoring Agent according to business needs
- Fine-tune specific settings directly on Resources using Remote Actions
Next Step
Add or manage a Monitoring Agent Configuration
Add or manage Monitor View
Related Topics
Install Database Monitoring Agent
Monitoring Agents
Applications