Collect SQL Server Custom Metrics

By default the Datadog-SQL server Check only captures some of the metrics available in the sys.dm_os_performance_counters table. Add additional metrics by following the custom_metrics structure.

Collecting metrics from DMV

Find below an example for a basic custom metric collection. There is no instance associated with this counter. Note: You can specify optional tags to be sent with your metrics:

  - name: sqlserver.clr.execution
    counter_name: CLR Execution
      - tag_name:value

Parameter descriptions:

nameName of your metric inside Datadog.
counter_nameThe counter name of SQL server database objects.

If a counter has multiple instances associated with it, you can choose to fetch a single instance with the instance_name parameter name:

  - name: sqlserver.exec.in_progress
    counter_name: OLEDB calls
    instance_name: Cumulative execution time (ms) per second

For finer granularity, query by the object_name :

- name: sqlserver.cache.hit_ratio
  counter_name: Cache Hit Ratio
  instance_name: SQL Plans
  object_name: SQLServer:Plan Cache

To collect all instances of a counter with multiple instances use the special, case-sensitive value ALL for the instance_name parameter which requires a value for the tag_by parameter. This example gets metrics tagged as db:mydb1, db:mydb2:

- name: sqlserver.db.commit_table_entries
  counter_name: Commit table entries
  instance_name: ALL
  tag_by: db

The default table from which counters are drawn is the sys.dm_os_performance_counters table. The Datadog-SQL server check also supports sys.dm_os_wait_stats, sys.dm_os_memory_clerks, and sys.dm_io_virtual_file_stats.

To report a metric drawn from one of the additional tables, specify the table in the counter definition with the table parameter, as well as the counter columns to be reported with the columns parameter:

  - name: sqlserver.LCK_M_S
    table: sys.dm_os_wait_stats
    counter_name: LCK_M_S
      - max_wait_time_ms
      - signal_wait_time_ms

The above example reports two metrics, and sqlserver.LCK_M_S.signal_wait_time_ms.

Note: If metrics like sys.dm_io_virtual_file_stats and sys.dm_os_memory_clerks are not associated with a counter_name only the columns need to be specified:

  - name: sqlserver.io_file_stats
    table: sys.dm_io_virtual_file_stats
      - num_of_reads
      - num_of_writes

The above example reports two metrics, sqlserver.io_file_stats.num_of_reads and sqlserver.io_file_stats.num_of_writes each tagged with the database ID and file ID.

Collecting metrics from a custom procedure

Collecting metrics from a custom procedure produces a large amount of custom metrics that may affect your billing.

Note: If you are using Agent < 6.11, you need to have set up the adodbapi driver in order for this to work.

Setup a stored procedure

A temporary table must be setup to collect the custom metrics for reporting to Datadog. The table needs the following columns:

metricThe name of the metric as it appears in Datadog.
typeThe metric type (gauge, rate, or histogram).
valueThe value of the metric (must be convertible to a float).
tagsThe tags that appear in Datadog separated by a comma.

The following stored procedure is created within the master database:

-- Create a stored procedure with the name <PROCEDURE_NAME>

  -- Create a temporary table per integration instructions
    [metric] varchar(255) not null,
    [type] varchar(50) not null,
    [value] float not null,
    [tags] varchar(255)

  -- Remove row counts from result sets

  -- Create variable count and set it equal to the number of User Connections
  DECLARE @count float;
  SET @count = (select cntr_value from sys.dm_os_performance_counters where counter_name = 'User Connections');

  -- Insert custom metrics into the table #Datadog
  INSERT INTO #Datadog (metric, type, value, tags)
  VALUES ('sql.test.test', 'gauge', @count, 'db:master,env:staging')
        ,('sql.test.gauge', 'gauge', FLOOR(RAND()*20), 'tag:test')
        ,('sql.test.rate', 'rate', FLOOR(RAND()*20), 'metric:gauge')
        ,('sql.test.histogram', 'histogram', FLOOR(RAND()*20), 'metric:histogram')
  SELECT * from #DataDog

-- Grant permission to run the stored procedure

The stored procedure outputs the following custom metrics:

  • sql.test.test
  • sql.test.gauge
  • sql.test.rate
  • sql.test.histogram.95percentile
  • sql.test.histogram.avg
  • sql.test.histogram.count
  • sql.test.histogram.max
  • sql.test.histogram.median

Update the SQL Server integration configuration

To collect metrics from a custom procedure, create a new instance definition inside your sqlserver.d/conf.yaml file with the procedure to execute. A separate instance is required for any existing configuration. Instances with a stored procedure do not process anything but the stored procedure, for example:

  - host:,1433
    username: datadog
    password: "<PASSWORD>"
    database: master
  - host:,1433
    username: datadog
    password: "<PASSWORD>"
    stored_procedure: "<PROCEDURE_NAME>"
    database: master

You can also specify:

ignore_missing_databaseIf the DB specified doesn’t exist on the server then don’t do the check.False
proc_only_ifRun this SQL before each call to stored_procedure. If it returns 1, call the procedure.
proc_only_if_databaseThe database to run the proc_only_if SQL in.database attribute

Note: The proc_only_if guard condition is useful for HA scenarios where a database can move between servers.


If your custom metrics are not appearing in Datadog, check the Agent log file. If you see the following error: Could not call procedure <PROCEDURE_NAME>: You must supply -1 parameters for this stored procedure, it could be one of the following issues:

  • The <PROCEDURE_NAME> is typed incorrectly.
  • The database username specified in the configuration may not have permission to run the stored procedure.

Further Reading