Database Visibility extends monitoring by specifying SQL queries to run on the monitored database and the queries run during normal database activity. You can schedule these custom queries to run on regular intervals and collect the results in a custom metric. See Database Custom Metrics Window.

To specify custom queries to run:

1. Navigate to Configuration > Custom Metrics > New. 
2. Complete the following fields:
   1. Name: The name you want to name your custom metric. Once you create a custom metric/event, you cannot change its name.
   2. Custom Query Metric Type: The type of result that you want from the query. 

      1. 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.

      2. Select the Event Data type to generate custom events whenever the custom query output is non-empty. If you want to be notified when a custom event occurs, you can create a policy that is triggered by that custom event. Custom events are displayed in the Events tab. If the custom query outputs multiple rows, the first 40 rows will be included in the event details. Each row displays a maximum of 5000 characters, including the column separators (|).
   3. Database Type: The database platform that you want to run the metric on.
   4. 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 specific database instances you specify. However, in the case of a cluster, you cannot run the metric on a specific database instance.

   5. 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.
      The timeout for configured custom metric depends on the frequency of running the query. This table provides the timeout details based on the time interval:

      Interval (minutes)	Timeout (seconds)
      1	10
      5	15
      10	30
      30	60
      60	120
      360	180
      720	300
      1440	300

       

   6. 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:

      1. Positive integer. For example, the query below returns a positive integer.

         SELECT COUNT(*) FROM employees

      2. String and positive integer. For example, the query below returns a string and a positive integer.
         

         SELECT name, salary FROM employees

Custom queries appear for all collectors, but the 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 following points provide information about using limits when configuring custom metrics:

• Up to 150 custom metrics can be reported per collector per minute.
• You can increase the custom metrics limit from the agent configuration properties by using the key, dbagent.custom.metric.reportable.per.server and the Max value 150. See Database Agent Configuration Properties for information about the key value.
• The maximum limit configured in the agent takes precedence and overrides the maximum limit configured at the account level and Controller level. Therefore, the priority order is as following:
  • Agent-level configuration
  • Account-level configuration
  • Controller-level configuration

Custom metrics are supported for all relational databases: MySQL, Microsoft SQL Server, Microsoft Azure SQL, Oracle, PostgreSQL, DB2, SAP HANA, and Sybase.

View Custom Metrics

You can view your custom metrics in the following locations:

• In Databases > Metric Browser, expand the database that you want to view custom metrics for.
  
• In Databases, open a database instance and click the Custom Metrics tab.