With Database Visibility, you can extend monitoring by specifying SQL queries that you want to run on the monitored database in addition to the queries run during normal database activity. You can schedule these custom queries to run at regular intervals and collect the results in a custom metric.
To specify custom queries to run:
Name: The name you want to name your custom metric. Once you create a custom metric/event, you cannot change its name.
Custom Query Metric Type: The type of result that you want from the query.
Select the Metric type to generate metrics for which health rules can be defined. Metrics of this type are displayed in the metric browser or in the Custom Metrics tab of each collector.
Database Type: The database platform that you want to run the metric on.
Databases: The database instances that you want to run the metric on. You can run the metric on all database instances of the specified database type, or on specific database instances that you specify.
Schedule: The time interval at which you want to run the query. For metric type custom queries, the metric value reported in between the specified intervals is the value observed in the previous query execution.
Query Text: The query that you want to execute. If you are creating a custom metric of Metric type, its query must have one of the following return types:
Positive integer. For example, the query below returns a positive integer.
SELECT COUNT(*) FROM employees
String and positive integer. For example, the query below returns a string and a positive integer.
SELECT name, salary FROM employees
When you create a custom query, it appears for all collectors, but its data only reflects the collector that you created it for.
You can test the semantics of the query and also validate the results by clicking the Test Query button.
The results are validated only if the database agent version is greater than 4.5.5.
The following points provide information about using limits when configuring custom metrics:
total number of Collectorsand
dbmon.config.max.custommetric.By default, the value of
dbmon.config.max.custommetricis 40. You can adjust the limit up to 150 using the
dbmon.config.max.custommetricproperty in the Controller settings.
Maxvalue 150. For more information about including the key value, see Database Agent Configuration Properties.
Custom metrics are supported for all relational databases: MySQL, Microsoft SQL Server, Oracle, PostgreSQL, DB2, and Sybase.
You can view your custom metrics in the following locations: