Partager via


Jetstress: How to include your counters in performance log.

Months ago, I got a storage vender's feedback that his job will become a lot easier if he can define additional performance counters for his storage hardware to the performance log. I decided to provide him with a convenient way to add new performance counters (but, no way to suppress existing performance counters).

When you save your configuration to an xml file that has a list of performance counters as follows:

<PerfLibs>

  <Include Name="host">

    <CounterPath>\LogicalDisk(*)\*</CounterPath>

    <CounterPath>\Memory\*</CounterPath>

    <CounterPath>\Processor(*)\*</CounterPath>

    <CounterPath>\Process(*)\*</CounterPath>

    <CounterPath>\System\*</CounterPath>

    <CounterPath>\PhysicalDisk(*)\*</CounterPath>

    <CounterPath>\Network Interface(*)\*</CounterPath>

  </Include>

</PerfLibs>

You can define additional performance counters in an xml config file from which you will open the configuration later on. The following example shows how to add .NET CLR Memory counters for JetstressWin process and all Windows Kernel objects.

<PerfLibs>

  <Include Name="host">

    <CounterPath>\LogicalDisk(*)\*</CounterPath>

    <CounterPath>\Memory\*</CounterPath>

    <CounterPath>\Processor(*)\*</CounterPath>

    <CounterPath>\Process(*)\*</CounterPath>

    <CounterPath>\System\*</CounterPath>

    <CounterPath>\PhysicalDisk(*)\*</CounterPath>

    <CounterPath>\Network Interface(*)\*</CounterPath>

    <CounterPath>\.NET CLR Memory(JetstressWin)\*</CounterPath>

    <CounterPath>\Objects\*</CounterPath>

  </Include>

</PerfLibs>

NOTE: This feature is so un-documented and no fully supported. But, it can help you quite a bit sometimes. I believe customer interaction lead to effective designs and quality improvements.

This posting is provided "AS IS" with no warranties, and confers no rights.