Release Notes
Configuring the Database Monitoring Agent
This guide teaches how to configure 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:
Example of Configuration button available in the Monitoring Agent Configuration administration page
Many specific configurations can also be made directly on the Resource using the Action button if the Monitor View has the use of Remote Actions feature enabled.
You must be a Nodinite Administrator, to Manage the collection of databases.
Add SQL Server Instance
To monitor and control one or more SQL instances you must provide some basic connection details.
Click on Add button to add a new SQL Server Instance to monitor, repeat as needed.
Configure the connection
Click the Accordion to expand the connection configuration
For each SQL Server connection, the following properties can be set:
- Enabled - When checked this specific configuration will be monitored
- Configuration name - The user-friendly name for this configuration
- Description - (optional) user-friendly short description for this configuration.
- Connection String - The connection string used by the Database Monitoring Agent to connect to the SQL Server, see also Connection String.
Server=NODINITE-DEV04;Database=MSDB;Trusted_Connection=True;Connection Timeout=5
Every database accessible for the service account running will be displayed as a Resource in Monitor Views.
- Application Id - Any one of the user-defined ApplicationId's in the Application tab.
SQL Categories
Each SQL Server instance can be individually fine-tuned regarding different monitoring aspects. The following Categories are available:
- SQL Backups - Monitor your backups
- SQL Jobs - Monitor how your SQL Agent jobs perform
- Size Checks - Data and log separately, monitors the size usage
- SSIS - Options for monitoring SSIS Packages and SSIS Projects
- 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.
Configure the added server
Click the Accordion to expand
- 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 Azure SQL database, see also Connection String.
Server=example.database.windows.net;Database=TestDB01;User ID=user1;Password=3l1t;Trusted_Connection=False;Connection Timeout=30
- Application Id - Any one of the user-defined ApplicationId's in the Application tab.
Azure SQL Database Categories
Each Azure SQL database can be individually fine-tuned regarding different monitoring aspects. The following Categories are available:
- Azure SQL Statements - run custom SQL statements with your own logic and monitor for example the state of your business data
- Azure - SQL Size Checks (data, no transaction log) - monitors file usage
Add PostgreSQL Database
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.
Configure the added server
Click the Accordion to expand
- 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` [Connection String][ConnectionStrings]
- 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:
- PostgreSQL - SQL Statements - run custom SQL statements with your own logic and monitor for example the state of your business data
Applications
Create the appropriate Applications first. There can be any number of Applications and they are further used to group related Resources.
Settings tab
From within the Settings tab, you provide some details that determines the operation behaviour of the Database Monitoring Agent.
- Environment
- Debug
- Culture Information
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 for changes to be written to the agent and take effect.
NOTE: The delay in presenting the new evaluated state depends on the synchronisation interval set for the monitoring agent. Click the Sync Now button to force an immediate synchronisation.
Save and close, save, and close the dialogue.
Cancel, close 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
Add and configure a new Monitoring Agent Configuration
-
Connection information is available in the
README.txtfile in the installation folder
-
Use the Remote Configuration feature to configure the agent. Detailed at the beginning of this user 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
Install Database Monitoring Agent
Monitoring Agents
Applications