Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > Use XML and TSQL to create custom charts that cannot be created in the Web Interface

Use XML and TSQL to create custom charts that cannot be created in the Web Interface

Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 767 Votes: 0 Revisions: 6

Creating a Microsoft SQL Server Page Life Expectancy metric example

If you can write XML and T-SQL, you can gather details for specific performance counters that aren't supported by the DPA Custom Metric dialog. Here is an example scenario adding the "Page Life Expectancy" Microsoft SQL Server object into your DPA collection.

  1. Create the folder {install directory}\Ignite PI\iwc\tomcat\ignite_config\idc\metrics
  2. In the metrics folder, create the file custom-metrics-properties_SQLServer.xml
    <metricsProperties name="Page Life Expectancy">
      <displayName>Page Life Expectancy</displayName>
        <description>Number of seconds a page stays in buffer pool.
  3. In the metrics folder, create the file custom-metrics-queries.xml
    <metricsQuery className="com.confio.idc.database.metrics.domain.queries.
            select cntr_value
            from sys.dm_os_performance_counters
            where counter_name = 'Page life expectancy'
            and object_name like '%Buffer Manager%'
      <name>Page Life Expectancy</name>
         <databaseType>SQL Server</databaseType>

Additional Information

The sys.dm_os_performance_counters DMV contains many, but not all, objects found in System Monitor.

So, if you need something not in the DMV (say Avg. Disk sec/Read), one option is to resort to some WMI objects using sp_OA procedures as follows:

<metricsQuery className="com.confio.idc.database.metrics.domain.queries.
        DECLARE @WmiServiceLocator INT ,
                @WmiService INT ,
                @CounterObject INT ,
                @DiskSecPerRead BIGINT ,
                @DiskSecPerRead_Base BIGINT ,
                @DiskSecPerWrite BIGINT ,
                @DiskSecPerWrite_Base BIGINT

        EXEC sp_OACreate 'WbemScripting.SWbemLocator', 
@WmiServiceLocator OUTPUT, 5

        EXEC sp_OAMethod @WmiServiceLocator, 'ConnectServer', 
@WmiService OUTPUT, '.', 'root\cimv2' 

        IF ISNULL(@WmiService, -1) <= 0
              EXEC sp_OADestroy @WmiServiceLocator
                 RAISERROR('Could not access WMI service. 
See:', 16, 1)

        EXEC sp_OAMethod @WmiService, 'Get', @CounterObject OUTPUT, 

        EXEC sp_OAGetProperty @CounterObject, 'AvgDiskSecPerRead', 
@DiskSecPerRead OUTPUT
        EXEC sp_OAGetProperty @CounterObject, 'AvgDiskSecPerRead_Base', 
@DiskSecPerRead_Base OUTPUT
        EXEC sp_OAGetProperty @CounterObject, 'AvgDiskSecPerWrite', 
@DiskSecPerWrite OUTPUT
        EXEC sp_OAGetProperty @CounterObject, 'AvgDiskSecPerWrite_Base', 
@DiskSecPerWrite_Base OUTPUT 

        EXEC sp_OADestroy @CounterObject
        EXEC sp_OADestroy @WmiService
        EXEC sp_OADestroy @WmiServiceLocator   

        IF @DiskSecPerRead IS NULL OR @DiskSecPerWrite IS NULL
              RAISERROR('Could not access WMI counter: 
See:', 16, 1)

        SELECT @DiskSecPerRead, @DiskSecPerRead_Base, @DiskSecPerWrite, 
            <metric name="DiskSecPerRead">
.divide(TEN, BigDecimal.ROUND_HALF_DOWN).divide(args[1], 
            <metric name="DiskSecPerWrite">
.divide(TEN, BigDecimal.ROUND_HALF_DOWN).divide(args[3], 
            <databasetype>SQL Server</databasetype>

The example above should help get anyone started customizing DPA collections, especially if the counter is already available in the sys.dm_os_performance_counters DMV. If you need to get additional counters not in that DMV then you need to resort to other methods to pull the data from the OS. I like to use the WMI Code Creator tool available for free from Microsoft. With that tool, for example, you can locate the code with just a few clicks.

Last modified