Configuring PostgreSQL Database Monitoring
Understanding PostgreSQL Monitoring Configuration
Before configuring PostgreSQL monitoring, understand how Nodinite connects to and monitors your PostgreSQL databases. The Database Monitoring Agent uses the Npgsql driver to establish secure connections and execute custom SQL statements for business data validation.
Tip
For general remote configuration guidance, setup steps, and initial agent configuration, see the main Configuration guide.
PostgreSQL Monitoring Architecture
The Database Monitoring Agent actively monitors your configured PostgreSQL Databases. Each configured database connection is represented in Nodinite as one or more Resources, providing real-time state evaluation.
Diagram: PostgreSQL monitoring architecture showing secure connection flow from database server to Nodinite Web Client with alert capabilities.
PostgreSQL database configurations are grouped by the Category PostgreSQL - SQL Statements:

Example of a Nodinite Monitor View showing PostgreSQL Resources.
Key points:
- Your PostgreSQL Databases are listed in Nodinite as resources, where the name of the Configuration becomes the Resource name prefix
- Each configuration can include multiple SQL statements for business data monitoring
- Monitor database status using Monitor Views and trigger external alerts through any installed Alarm Plugins
What are the key features for PostgreSQL Configuration?
- Remote Configuration – Configure PostgreSQL connections directly from the Nodinite Web Client
- Secure Connection Strings – Encrypted storage of database credentials
- Custom SQL Statements – Execute your own PostgreSQL queries for business data monitoring
How do I configure a PostgreSQL Database?
PostgreSQL database monitoring is configured through the Remote Configuration dialogue for the Database Monitoring Agent. For general setup and initial configuration steps, see:
There are different configuration areas for PostgreSQL databases:
Add PostgreSQL Database
Click the Add button to add a new PostgreSQL Database to monitor. Provide one entry per Database. Each entry appears as at least one Resource in Monitor Views.

Add a new PostgreSQL Database configuration
Configure the PostgreSQL Database Entry

Configure the PostgreSQL Database connection
Click the Accordion to expand the configuration section.
- Enabled – Enable monitoring for this configuration
- Configuration name – User-friendly name for this configuration (becomes the Resource name prefix)
- Description – Optional description of this configuration
- Connection String – The Database Monitoring Agent uses this to connect to PostgreSQL
- Application ID – Any user-defined ApplicationId from the Applications tab
Connection String Format
The PostgreSQL connection string uses Npgsql format. Here's an example:
Server=123.databases.appdomain.cloud;Port=31902;Database=ibmclouddb;User Id=ibm_cloud_456;Password=789;SSLMode=Prefer;Trust Server Certificate=true;
Connection String Parameters
| Parameter | Description | Example Values |
|---|---|---|
| Server | PostgreSQL server hostname or IP address | localhost, db.example.com |
| Port | PostgreSQL server port | 5432 (default), 31902 |
| Database | Name of the PostgreSQL database to connect to | production_db, ibmclouddb |
| User Id | PostgreSQL username for authentication | postgres, nodinite_monitor |
| Password | PostgreSQL password for authentication | Encrypted credential |
| SSLMode | SSL/TLS connection mode | Disable, Prefer, Require, VerifyFull |
| Trust Server Certificate | Whether to trust self-signed certificates | true, false |
Tip
For production environments, use
SSLMode=RequireorSSLMode=VerifyFulland setTrust Server Certificate=falseto enforce certificate validation.
Note
The Connection String is encrypted in the Settings.json file for security.
PostgreSQL Categories
You can configure different monitoring aspects for each PostgreSQL database. The following Categories are available:
| Category | Description | Configuration |
|---|---|---|
| PostgreSQL - SQL Statements | Run custom SQL statements to monitor business data | Configuration |
Settings
The Settings tab configures operational parameters for the Database Monitoring Agent. For detailed configuration of all settings including Environment, Debug mode, and Culture Information, see the main configuration guide:
Key settings relevant to PostgreSQL monitoring:
- Environment – Set environment name (DEV, TEST, PROD)
- Debug – Enable detailed logging for troubleshooting connection issues
- Culture Information – Configure time-based data presentation
Actions
The Database Monitoring Agent PostgreSQL configurations support the following Remote Actions:
- Edit Configuration – Modify connection settings and SQL statements
- Test Connection – Verify database connectivity
Save
For details on saving your configuration changes and synchronization behavior, see:
Next Step
PostgreSQL - SQL Statements
Add or manage Monitor View
Related Topics
Install Database Monitoring Agent
Configure Database Monitoring Agent
Monitoring Agents
Applications
Database Monitoring Agent