Knowledge Base

IPCheck Custom Sensor: Reading Windows Performance Counters from local or remote computer

Cette page n’existe pas en français en ce moment. Nous vous prions de nous excuser.

This custom sensor for IPCheck Server Monitor reads performance counters from a Windows machine using WMI. You can find the files of this sensor in the following sub folder of your IPCheck Server Monitor installation:

\custom\sample\dot net\read windows performance counters

It was created using .NET. The .NET framework must be installed. The source can be found in "ClassMain.cs".

Prerequisites:

  • .NET framework 1.1 must be installed on the machine running IPCheck Server Monitor.
  • the machine being queried must run Win2k or later

Instructions:

  • Copy EXE and PDB into your CUSTOM directory
  • Restart the IPCheck web server process (to scan the folder for new files)
  • Create a new CUSTOM sensor
  • For the Sensor setting choose CollectWinPerfData.exe
  • For Parameters set the following values in the webinterface:
    "categoryName" "counterName" "instanceName" "machineName" "ScalingFactor"

Examples:

  • "Processor" "% Processor Time" "_Total" "DEVIL" "1"
  • "Network Interface" "Bytes Total/sec" "Intel[R] Pro Adapter" 
    "10.1.1.30" "100"
  • "SQLServer:General Statistics" "User Connections" "" "10.1.1.30" "1"

The parameters are:

  • categoryName: The name of the performance counter category (performance object) with which this performance counter is associated.
  • counterName: The name of the performance counter.
  • instanceName: The name of the performance counter category instance, or an empty string (""), if the category contains a single instance.
  • machineName: The computer on which the performance counter and its associated category exist. This can be also an ip address. Note that the account from which CollectWinPerfData runs (which is the account that IPCheck's webserver runs on, see service settings) must have Administrator or PowerUser rights to access the remote performance registry hives!
  • ScalingFactor: needed because IPCheck only accepts integer values; correct values would be: 100 or 10 or 1 or 0,1 or 0,01 etc.

Sample Code was created by Torsten Sturm

By Category