- 0 minutes to read

Release Notes

Configuring the Database Monitoring Agent

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 on the 'Configuration' button to open a modal to configure the agent:

RemoteConfiguration
Here's an example of Configuration button available in the Monitoring Agent Configuration administration page

Configurations on the Resource can be adjusted via the Action button if the Monitor View has the Remote Actions feature enabled.

SQL Server Instance

Click on Add button to add a new SQL Server Instance to monitor, repeat as needed. Add SQL Server Monitoring Configuration

SQL Server Configuration Entry

Click the Accordion to expand the connection configuration SQL Server Accordion

SQL Server General Tab

For each SQL Server connection, you need to set the following properties: SQL Server General Tab

  • Enabled - When checked, Monitor the 'SQL Server' configuration, otherwise do not
  • Configuration name - Unique name for this connection (configuration)
  • Description - Logical short description for this configuration
  • Connection String - The connection string in use for this configuration (default is: 'Data Source=localhost;Initial Catalog=MSDB;Trusted_Connection=True;Connection Timeout=10;Encrypt=true;TrustServerCertificate=true;'); see also Connection String .
Server=NODINITE-DEV04;Database=MSDB;Trusted_Connection=True;Connection Timeout=5

Each SQL Server instance can be individually fine-tuned regarding 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 Data and log separately, monitors the size usage Configuration
SQL Jobs Monitor how your SQL Agent jobs perform Configuration
SSIS Options for monitoring SSIS Packages and SSIS Projects Configuration
SQL Statements Run custom SQL statements with your own logic and monitor for example the state of your business data

Add Azure SQL Databases

Click the Add button to add a SQL Azure Database to monitor. You must provide one entry per SQL Database to be monitored. Each entry will be represented as a Resource in Monitor Views.
6

Configure the added server

5

Click the Accordion to expand the content.

  • Enabled - When checked, Monitor the 'SQL Server' configuration, otherwise do not
  • Configuration name - Unique name for this connection (configuration)
  • Description - Logical short description for this configuration
  • Connection String - The connection string in use for this configuration (default is: 'Data Source=localhost;Initial Catalog=MSDB;Trusted_Connection=True;Connection Timeout=10;Encrypt=true;TrustServerCertificate=true;') The connection string used by the Database Monitoring Agent to connect to the Azure SQL database, 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

Each Azure SQL database can be individually fine-tuned regarding different monitoring aspects. The following Categories are available:

PostgreSQL Database Configuration Entry

Click the Add button to add a PostgreSQL Database to monitor. You must provide one entry per Database to be monitored. Each entry will be represented as at least one Resource in Monitor Views.
7

Configure the added PostGresql Database

8

Click the Accordion to expand the content.

  • Enabled - When checked this specific configuration will be monitored
  • Configuration name - The user-friendly name for this configuration
  • Description - (optional) A description of this configuration to monitor
  • Connection String The connection string used by the Database Monitoring Agent to connect to the PostgreSQL database.
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 one of the user-defined ApplicationId's in the Application tab.

PostgreSQL Categories

Each PostgreSQL database can be individually fine-tuned regarding different monitoring aspects. The following Categories are available:

Settings tab

From within the Settings tab, you provide some details that determines the operation behaviour of the Database Monitoring Agent.

Settings tab

Environment

Part of the standard features shared with all Monitoring Agents is an option to set the name of the target environment, for example, TEST, QA, PROD.

Debug

Part of the common features shared with all Monitoring Agents, there is an option to set the Debug flag for additional file logging that can be enabled/disabled as needed. 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

You must click 'Save' or 'Save and close' for changes to persist. The new settings/thresholds are evaluated on the next synchronization.
Save and Close buttons
Here's an 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, save, and close the dialogue.
Cancel, closes the dialogue without saving any changes.

Add Database Monitoring Agent Configuration

After the successful installation of the Database Monitoring Agent you must provide Nodinite with connection details so the Monitoring Service knows there's a new guy in town.

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

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. Detailed at the beginning of this user 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