VMware View PAL Connection Server Sample Report

1 comment

Analysis of “PAL_VMWare_View_Connection_Server_Performance.blg”

Report Generated at: 9/25/2012 11:43:21 AM

PALv2

On This Page

  • Cache
  • LogicalDisk
  • Memory
  • Network Interface
  • Paging File
  • PhysicalDisk
  • Process
  • Processor
  • Processor Information
  • Server
  • System
  • TCPv4
  • VM Memory
  • VM Processor
  • Vmware View Connection Server
  • VMware View Connection Server
  • Disclaimer
  • Back to the top

    Tool Parameters:


    NameValue
    Log Time Range: 9/25/2012 11:29:51 AM – 9/25/2012 11:34:06 AM
    Log(s): C:\Users\josh.townsend\Desktop\PAL_VMWare_View_Connection_Server_Performance.blg
    AnalysisInterval: 8 second(s)
    Threshold File: C:\Program Files\PAL\PAL\PAL_VMwareView_VDM.xml
    AllCounterStats: False
    NumberOfProcessors:4
    vRAMSize:2
    ViewParentSixtyFourBit:False
    LinnkedClone:True
    SixtyFourBit:False
    NumberOfVirtualCPUs:1
    TotalMemory:4
    RAID5Drives:NULL
    RAID1Drives:NULL
    ThreeGBSwitch:False

    Back to the top

    Alerts by Chronological Order


    Description: This section displays all of the alerts in chronological order.

    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.

    Time Range
    9/25/2012 11:29:51 AM – 9/25/2012 11:30:06 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,939,367,4242,939,367,4242,939,367,4240
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,620,615,1681,620,615,1681,620,615,1680
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    9/25/2012 11:30:06 AM – 9/25/2012 11:30:21 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,939,367,4242,939,367,4242,939,367,4240
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,618,518,0161,618,518,0161,618,518,016-943,718,400
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    9/25/2012 11:30:21 AM – 9/25/2012 11:30:36 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,939,367,4242,939,367,4242,939,367,4240
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,618,518,0161,618,518,0161,618,518,016-471,859,200
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures631631631225
    9/25/2012 11:30:36 AM – 9/25/2012 11:30:51 AMConditionCounterMinAvgMaxHourly Trend
    Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour\\VIEWCS1\Process(_Total)\Handle Count22,05822,05822,05816,200
    The working set of all processes combined is increasing at a rate greater than 100MBs per hour\\VIEWCS1\Process(_Total)\Working Set1,671,376,8961,671,376,8961,671,376,896556,646,400
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,943,561,7282,943,561,7282,943,561,728629,145,600
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,619,566,5921,619,566,5921,619,566,592-157,286,400
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures631631631150
    9/25/2012 11:30:51 AM – 9/25/2012 11:31:06 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,943,561,7282,943,561,7282,943,561,728471,859,200
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,619,566,5921,619,566,5921,619,566,592-117,964,800
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures631631631112
    9/25/2012 11:31:06 AM – 9/25/2012 11:31:21 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,943,561,7282,943,561,7282,943,561,728377,487,360
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,619,566,5921,619,566,5921,619,566,592-94,371,840
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures63163163190
    9/25/2012 11:31:21 AM – 9/25/2012 11:31:36 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,943,561,7282,943,561,7282,943,561,728314,572,800
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,619,566,5921,619,566,5921,619,566,592-78,643,200
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures63163163175
    9/25/2012 11:31:36 AM – 9/25/2012 11:31:51 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,943,561,7282,943,561,7282,943,561,728269,633,829
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,617,469,4401,617,469,4401,617,469,440-202,225,371
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures63163163164
    9/25/2012 11:31:51 AM – 9/25/2012 11:32:06 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,941,464,5762,941,464,5762,941,464,576117,964,800
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,617,469,4401,617,469,4401,617,469,440-176,947,200
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures632632632112
    9/25/2012 11:32:06 AM – 9/25/2012 11:32:21 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,942,513,1522,942,513,1522,942,513,152157,286,400
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,619,566,5921,619,566,5921,619,566,592-52,428,800
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures632632632100
    9/25/2012 11:32:21 AM – 9/25/2012 11:32:36 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,942,513,1522,942,513,1522,942,513,152141,557,760
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,619,566,5921,619,566,5921,619,566,592-47,185,920
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures63263263290
    9/25/2012 11:32:36 AM – 9/25/2012 11:32:51 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,941,464,5762,941,464,5762,941,464,57685,792,582
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,619,566,5921,619,566,5921,619,566,592-42,896,291
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures63263263282
    9/25/2012 11:32:51 AM – 9/25/2012 11:33:06 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,939,367,4242,939,367,4242,939,367,4240
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,616,420,8641,616,420,8641,616,420,864-157,286,400
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures63263263275
    9/25/2012 11:33:06 AM – 9/25/2012 11:33:21 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,939,367,4242,939,367,4242,939,367,4240
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,614,323,7121,614,323,7121,614,323,712-217,781,169
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures633633633104
    9/25/2012 11:33:21 AM – 9/25/2012 11:33:36 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,937,270,2722,937,270,2722,937,270,272-67,408,457
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,614,323,7121,614,323,7121,614,323,712-202,225,371
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures63363363396
    9/25/2012 11:33:36 AM – 9/25/2012 11:33:51 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,939,367,4242,939,367,4242,939,367,4240
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,616,420,8641,616,420,8641,616,420,864-125,829,120
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures63363363390
    9/25/2012 11:33:51 AM – 9/25/2012 11:33:59 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,938,318,8482,938,318,8482,938,318,848-29,491,200
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,625,858,0481,625,858,0481,625,858,048147,456,000
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures63363363384

    Cache


    Cache Lazy Write Flushes/sec

    Description: Lazy Write Flushes/sec is the rate at which the Lazy Writer thread has written to disk. Lazy Writing is the process of updating the disk after the page has been changed in memory, so that the application that changed the file does not have to wait for the disk write to be complete before proceeding. More than one page can be transferred by each write operation.

    The lazy writer writes 20% of the dirty pages every second, but increases the number of lazy write flushes if it is unable to keep up with the rate of dirty pages.

    This analysis checks for more than 100 lazy write flushes/second which might indicate that the lazy writer is falling behind in writing to the disk.

    \Cache\Lazy Write Flushes/sec

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Cache\Lazy Write Flushes/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS112301222



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Cache Dirty Pages

    Description: Total number of dirty pages on the system cache

    \Cache\Dirty Pages

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Cache\Dirty PagesMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1335477-70312524948



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    LogicalDisk


    LogicalDisk % Free Space

    Description: % Free Space is the percentage of total usable space on the selected logical disk drive that was free. Low to no free disk space can cause severe disk performance problems.This analysis checks for less than 10% free disk space (Warning alert) and less than 5% free disk space (Critical alert).

    \LogicalDisk(*)\% Free Space<br /> Warning Range: 5 to 10<br
/> Critical Range: 0 to 5

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\LogicalDisk(*)\% Free SpaceMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/C:44444400444444
    OKVIEWCS1/HarddiskVolume172727200727272



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    LogicalDisk Read Latency Analysis

    Description: Avg. Disk sec/Read is the average time, in seconds, of a read of data to the disk. This analysis determines if any of the physical disks are responding slowly.

    If the response times are less than .015 (15 milliseconds), then the disk subsystem is keeping up with demand, but does not have much overhead left.

    If the response times are greater than .025 (25 milliseconds), then noticeable slow downs and performance issues affecting users may be occurring.

    Reference:
    Ruling Out Disk-Bound Problems
    http://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx

    \LogicalDisk(*)\Avg. Disk sec/Read<br /> Warning Range: .015 to .025<br
/> Critical Range: .025 to .029999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\LogicalDisk(*)\Avg. Disk sec/ReadMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/C:00000000
    OKVIEWCS1/HarddiskVolume100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    LogicalDisk Write Latency Analysis

    Description: Avg. Disk sec/Write is the average time, in seconds, of a write of data to the disk. This analysis determines if any of the physical disks are responding slowly.

    If the response times are greater than .015 (15 milliseconds), then the disk subsystem is keeping up with demand, but does not have much overhead left.

    If the response times are greater than .025 (25 milliseconds), then noticeable slow downs and performance issues affecting users may be occurring.

    Reference:
    Ruling Out Disk-Bound Problems
    http://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx

    \LogicalDisk(*)\Avg. Disk sec/Write<br /> Warning Range: .015 to .025<br
/> Critical Range: .025 to .029999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\LogicalDisk(*)\Avg. Disk sec/WriteMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/C:.001.001.00100.001.001.001
    OKVIEWCS1/HarddiskVolume100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    LogicalDisk % Idle Time

    Description: % Idle Time reports the percentage of time during the sample interval that the disk was idle.

    This analysis checks for a % Idle Time of less than 10. Zero (0) indicates that the disk contstanly has at least 1 outstanding I/O in the queue.

    Reference:

    \LogicalDisk(*)\% Idle Time<br /> Warning Range: 0 to 10

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\LogicalDisk(*)\% Idle TimeMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/C:9910010000100100100
    OKVIEWCS1/HarddiskVolume110010010000100100100



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    LogicalDisk Disk Transfers/sec

    Description: Disk Transfers/sec is the rate of read and write operations on the disk.

    \LogicalDisk(*)\Disk Transfers/sec

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\LogicalDisk(*)\Disk Transfers/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/C:249-842433
    No ThresholdsVIEWCS1/HarddiskVolume100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    LogicalDisk Read/Write Ratio

    Description:
    This analysis shows the ratio of reads to writes for each logical disk. For example, a value of 25 means 25 percent of all of the I/O per second is read I/O and 75 percent is write I/O.

    \LogicalDisk(*)\Read Write Ratio

    \LogicalDisk(*)\Disk Reads/sec

    \LogicalDisk(*)\Disk Writes/sec

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\LogicalDisk(*)\Read Write RatioMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/HarddiskVolume100000000
    No ThresholdsVIEWCS1/C:012205000

    Condition\LogicalDisk(*)\Disk Reads/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/C:00201000
    No ThresholdsVIEWCS1/HarddiskVolume100000000

    Condition\LogicalDisk(*)\Disk Writes/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/C:247-841433
    No ThresholdsVIEWCS1/HarddiskVolume100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    LogicalDisk Bytes/Read

    Description: This analysis shows the size of logical disk reads per second. The size of an I/O request packets (IRP) can have a direct affect on the average response times from the disk. This analysis checks for I/O request sizes of 64 KB or larger. Correlate this analysis with the Avg. Disk Sec/Read and Avg. Disk Sec/Write analyses.

    References:

    \LogicalDisk(*)\Avg. Disk Bytes/Read

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\LogicalDisk(*)\Avg. Disk Bytes/ReadMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/C:02,43441,376010,035000
    OKVIEWCS1/HarddiskVolume100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    LogicalDisk Bytes/Write

    Description: This analysis shows the size of logical disk writes per second. The size of an I/O request packets (IRP) can have a direct affect on the average response times from the disk. This analysis checks for I/O request sizes of 64 KB or larger. Correlate this analysis with the Avg. Disk Sec/Read and Avg. Disk Sec/Write analyses.

    Reference:

    \LogicalDisk(*)\Avg. Disk Bytes/Write

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\LogicalDisk(*)\Avg. Disk Bytes/WriteMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/C:4,0965,9248,25263,2531,1235,6525,5635,400
    OKVIEWCS1/HarddiskVolume100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    LogicalDisk Avg. Disk Queue Length

    Description: Avg. Disk Queue Length is the average number of both read and write requests that were queued or “in-flight” for the selected disk during the sample interval.

    This counter typically has a threshold of number of spindles + 2. Due to high end disk virtualization, it is difficult to determine the true number of physical spindles behind the logical disk or LUN. Therefore, this threshold will generically throw a Warning alert for an average disk queue length greater than 2.

    References:

    \LogicalDisk(*)\Avg. Disk Queue Length<br /> Warning Range: 2 to 9.999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\LogicalDisk(*)\Avg. Disk Queue LengthMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/C:00000000
    OKVIEWCS1/HarddiskVolume100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    LogicalDisk Current Disk Queue Length

    Description: Current Disk Queue Length is the number of requests outstanding on the disk at the time the performance data is collected. It also includes requests in service at the time of the collection. This is a instantaneous snapshot, not an average over the time interval. Multi-spindle disk devices can have multiple requests that are active at one time, but other concurrent requests are awaiting service. This counter might reflect a transitory high or low queue length, but if there is a sustained load on the disk drive, it is likely that this will be consistently high. Requests experience delays proportional to the length of this queue minus the number of spindles on the disks.

    This analysis checks if the number of I/O request packets (IRPs) in the disk queue are at 32 or higher. Many SAN vendors use 32 as a default setting for the Host Bus Adapter (HBA) which interfaces into the fibre channel network to connect to one or more SANs. If the queue depth (simultaneous in-flight I/O) is reached frequently, then the queue depth might need to be increased.

    Reference:

    \LogicalDisk(*)\Current Disk Queue Length

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\LogicalDisk(*)\Current Disk Queue LengthMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/C:00100000
    OKVIEWCS1/HarddiskVolume100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    LogicalDisk Disk Bytes/sec

    Description: Disk Bytes/sec is the rate bytes are transferred to or from the disk during write or read operations. A mirror pair (RAID1) 7200 RPM disk drives can deliver roughly 20 MB per second throughput.

    \LogicalDisk(*)\Disk Bytes/sec

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\LogicalDisk(*)\Disk Bytes/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/C:11,46327,750124,785-187,70625,65321,06120,50619,212
    No ThresholdsVIEWCS1/HarddiskVolume100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    LogicalDisk Free Megabytes

    Description: Free Megabytes displays the unallocated space, in megabytes, on the disk drive in megabytes. One megabyte is equal to 1,048,576 bytes.

    \LogicalDisk(*)\Free Megabytes

    \LogicalDisk(*)\Free Megabytes

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\LogicalDisk(*)\Free MegabytesMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/_Total22,38122,38122,3810022,38122,38122,381
    OKVIEWCS1/C:22,31022,31022,3100022,31022,31022,310
    Less than 500 MB of free disk spaceVIEWCS1/HarddiskVolume171717100717171



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    Time Range
    9/25/2012 11:29:51 AM – 9/25/2012 11:30:06 AMConditionCounterMinAvgMaxHourly Trend
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    9/25/2012 11:30:06 AM – 9/25/2012 11:30:21 AMConditionCounterMinAvgMaxHourly Trend
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    9/25/2012 11:30:21 AM – 9/25/2012 11:30:36 AMConditionCounterMinAvgMaxHourly Trend
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    9/25/2012 11:30:36 AM – 9/25/2012 11:30:51 AMConditionCounterMinAvgMaxHourly Trend
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    9/25/2012 11:30:51 AM – 9/25/2012 11:31:06 AMConditionCounterMinAvgMaxHourly Trend
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    9/25/2012 11:31:06 AM – 9/25/2012 11:31:21 AMConditionCounterMinAvgMaxHourly Trend
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    9/25/2012 11:31:21 AM – 9/25/2012 11:31:36 AMConditionCounterMinAvgMaxHourly Trend
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    9/25/2012 11:31:36 AM – 9/25/2012 11:31:51 AMConditionCounterMinAvgMaxHourly Trend
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    9/25/2012 11:31:51 AM – 9/25/2012 11:32:06 AMConditionCounterMinAvgMaxHourly Trend
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    9/25/2012 11:32:06 AM – 9/25/2012 11:32:21 AMConditionCounterMinAvgMaxHourly Trend
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    9/25/2012 11:32:21 AM – 9/25/2012 11:32:36 AMConditionCounterMinAvgMaxHourly Trend
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    9/25/2012 11:32:36 AM – 9/25/2012 11:32:51 AMConditionCounterMinAvgMaxHourly Trend
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    9/25/2012 11:32:51 AM – 9/25/2012 11:33:06 AMConditionCounterMinAvgMaxHourly Trend
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    9/25/2012 11:33:06 AM – 9/25/2012 11:33:21 AMConditionCounterMinAvgMaxHourly Trend
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    9/25/2012 11:33:21 AM – 9/25/2012 11:33:36 AMConditionCounterMinAvgMaxHourly Trend
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    9/25/2012 11:33:36 AM – 9/25/2012 11:33:51 AMConditionCounterMinAvgMaxHourly Trend
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710
    9/25/2012 11:33:51 AM – 9/25/2012 11:33:59 AMConditionCounterMinAvgMaxHourly Trend
    Less than 500 MB of free disk space\\VIEWCS1\LogicalDisk(HarddiskVolume1)\Free Megabytes7171710


    Back to the top

    Memory


    Memory Available MBytes

    Description:
    Available MBytes is the amount of physical RAM, in Megabytes, immediately available for allocation to a process or for system use. It is equal to the sum of memory assigned to the standby (cached), free and zero page lists. If this counter is low, then the computer is running low on physical RAM.
    This analysis will alert a Warning if this counter’s value is less than 10% of the RAM installed and will alert a critical if this counter’s value is less than 100MB’s. When Windows Server 2003 and newer has less then 100MBs of available RAM, it will go into a low memory condition and alert processes of this condition. If in a low memory condition the operating system will be more aggressive at working set trimming which pages out the physical RAM used by processes to the pagefile on the disk.

    References:

    \Memory\Available MBytes<br /> Warning Range: 204.8 to 409.6<br
/> Critical Range: .001 to 204.8

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Memory\Available MBytesMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS14,3494,3554,36025334,3554,3544,354



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Free System Page Table Entries

    Description: Free System Page Table Entries is the number of page table entries not currently in used by the system. This analysis determines if the system is running out of free system page table entries (PTEs) by checking if there is less than 20,000 free PTE’s as a Warning and critical if there is less than 8,000 free PTEs. Lack of enough PTEs can result in system wide hangs. Also note that the /3GB switch will lower the amount of free PTEs significantly.

    The Performance Monitor Memory\Free System Page Table Entries counter is inaccurate on installations of Windows Server 2003 without Service Pack 1. For more information about this counter, see Microsoft Knowledge Base article 894067. The Performance tool does not accurately show the available Free System Page Table entries in Windows Server 2003 http://go.microsoft.com/fwlink/?linkid=3052&kbid=894067

    Fix for Win2003 SP1 systems with /3GB and low on PTE’s: If the system is low on PTE’s, running Windows 2003, and using /3GB switch, then consider using the /USERVA switch to give back some of the memory to the kernel. Note, this only works for Free System PTE issues.

    For more information on the USERVA switch, go to:
    How to use the /userva switch with the /3GB switch to tune the User-mode space to a value between 2 GB and 3 GB

    Reference:

    Ruling Out Memory-Bound Problems

    Microsoft Knowledge Base article 894067 The Performance tool does not accurately show the available Free System Page Table entries in Windows Server 2003

    How to use the /userva switch with the /3GB switch to tune the User-mode space to a value between 2 GB and 3 GB

    How to determine the appropriate page file size for 64-bit versions of Windows Server 2003 or Windows XP
    http://support.microsoft.com/kb/889654

    \Memory\Free System Page Table Entries<br /> Warning Range: 8,000 to 20,000<br
/> Critical Range: 0 to 8,000

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Memory\Free System Page Table EntriesMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS133,555,26333,555,46433,555,777025733,555,42533,555,37433,555,343



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Pool Non-Paged Bytes

    Description: Pool Nonpaged Bytes is the size, in bytes, of the nonpaged pool, an area of system memory (physical memory used by the operating system) for objects that cannot be written to disk, but must remain in physical memory as long as they are allocated.

    This analysis checks to see if the system is becoming close to the maximum Pool Nonpaged memory size. It does this by estimating the pool sizes taking into consideration /3GB, physical memory size, and 32-bit/64-bit, then determining if the value is higher than 60% of the estimated pool size. If the system becomes close to the maximum size, then the system could experience system wide hangs. Checks both 32-bit and 64-bit memory pools. Warning: The /3GB switch option in the boot.ini file significantly reduces the size of this memory pool.

    If the system is low on Paged Pool or non-Paged pool memory, then it is recommended to open a support case with Microsoft to address this. Alternatively, you can use a free and public tool called Poolmon.exe to see what DLL’s are using kernel memory (see the article below). Most kernel memory leaks can be tracked back to a usermode process. To identify which user mode process is responsible, reboot the system (so you start off with a clean system), start a performance monitor log intending to run for a week or more capturing the Memory and Process objects, then analyze the perfmon log looking for memory leaks and/or handle leaks in one or more of the processes. In any case, migrating to a 64-bit version of Windows should alleviate this issue.

    References
    How to Use Memory Pool Monitor (Poolmon.exe) to Troubleshoot Kernel Mode Memory Leaks
    http://support.microsoft.com/kb/177415

    Ruling Out Memory-Bound Problems
    http://technet.microsoft.com/en-us/library/7a44b064-8872-4edf-aac7-36b2a17f662a.aspx

    How to determine the appropriate page file size for 64-bit versions of Windows Server 2003 or Windows XP
    http://support.microsoft.com/kb/889654

    \Memory\Pool Nonpaged Bytes<br /> Warning Range: 161,061,273.6 to 214,748,364.799<br
/> Critical Range: 214,748,364.8 to 268,435,456

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Memory\Pool Nonpaged BytesMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS139,096,32039,222,61339,251,9684,032,00046,00439,219,20039,215,10439,212,583



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Pool Paged Bytes

    Description: This analysis checks to see if the system is becoming close to the maximum Pool paged memory size. Pool Paged Bytes is the size, in bytes, of the paged pool, an area of system memory (physical memory used by the operating system) for objects that can be written to disk when they are not being used.

    This analysis checks to see if the system is becoming close to the maximum Pool Paged memory size. It does this by estimating the pool sizes taking into consideration /3GB, physical memory size, and 32-bit/64-bit, then determining if the value is higher than 60% of the estimated pool size. If the system becomes close to the maximum size, then the system could experience system wide hangs. Checks both 32-bit and 64-bit memory pools. Warning: The /3GB switch option in the boot.ini file significantly reduces the size of this memory pool.

    If the system is low on Paged Pool or non-Paged pool memory, then it is recommended to open a support case with Microsoft to address this. Alternatively, you can use a free and public tool called Poolmon.exe to see what DLL’s are using kernel memory (see the article below). Most kernel memory leaks can be tracked back to a usermode process. To identify which user mode process is responsible, reboot the system (so you start off with a clean system), start a performance monitor log intending to run for a week or more capturing the Memory and Process objects, then analyze the perfmon log looking for memory leaks and/or handle leaks in one or more of the processes. In any case, migrating to a 64-bit version of Windows should alleviate this issue.

    Reference:
    How to Use Memory Pool Monitor (Poolmon.exe) to Troubleshoot Kernel Mode Memory Leaks
    http://support.microsoft.com/kb/177415

    Ruling Out Memory-Bound Problems
    http://technet.microsoft.com/en-us/library/7a44b064-8872-4edf-aac7-36b2a17f662a.aspx

    How to determine the appropriate page file size for 64-bit versions of Windows Server 2003 or Windows XP
    http://support.microsoft.com/kb/889654

    \Memory\Pool Paged Bytes<br /> Warning Range: 158,544,691.2 to 211,392,921.599<br
/> Critical Range: 211,392,921.6 to 264,241,152

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Memory\Pool Paged BytesMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS195,801,34495,851,63495,891,456576,00021,34495,848,19295,846,10795,845,140



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Pages/sec

    Description: This analysis checks to see if the Pages/sec is high while the system is in a low memory condition. If it is sustained at a high amount, then the system is might be running out of memory by trying to page the memory to the disk. Keep in mind that all hard page faults are counted in the pages/sec counter such as hard page faults caused by memory mapped files instead of page file hits.
    According to Wikipedia, memory-mapped files are a segment of virtual memory which has been assigned a direct byte-for-byte correlation with some portion of a file or file-like resource. This resource is typically a file that is physically present on-disk, but can also be a device, shared memory object, or other resource that the operating system can reference through a file descriptor.
    In other words, applications like Microsoft Word and Microsoft PowerPoint will not load entire documents into RAM. Instead, they memory map the file, so that when you navigate through the document, it loads portions of the document as needed. The act of loading portions of the document from disk to RAM as a memory mapped file causes a hard page fault which is counted in the pages/sec counter. See the article The Case of the Phantom Hard Page Faults. To determine if the hard page faults are actually hitting the page file, use Process Monitor with Advanced Ouput enabled to see how often the page file(s) are hit.

    Pages/sec is the rate at which pages are read from or written to disk to resolve hard page faults. It is the sum of Memory\Pages Input/sec and Memory\Pages Output/sec. It is counted in numbers of pages, so it can be compared to other counts of pages, such as Memory\Page Faults/sec, without conversion. It includes pages retrieved to satisfy faults in the file system cache (usually requested by applications) non-cached mapped memory files.

    This counter should always be below 1000, therefore this analysis checks for values above 1000. Use this analysis in correlation with Available Memory Analysis and Memory Leak Analysis. If all are throwing alerts at the same time, then this may indicate the system is running out of memory and the suspected processes involved and follow analysis steps mentioned in the Memory Leak analysis.

    Reference

    \Memory\Pages/sec<br /> Warning Range: 1,000 to 1,999.999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Memory\Pages/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1019282000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory System Cache Resident Bytes

    Description: System Cache Resident Bytes is the size, in bytes, of the pageable operating system code in the file system cache. This value includes only current physical pages and does not include any virtual memory pages not currently resident. It does equal the System Cache value shown in Task Manager. As a result, this value may be smaller than the actual amount of virtual memory in use by the file system cache. This value is a component of Memory\\System Code Resident Bytes which represents all pageable operating system code that is currently in physical memory. This counter displays the last observed value only; it is not an average.

    This analysis checks if System Cache Resident Bytes is consuming more than 50 percent of RAM. Under load, a server might use the System Cache in order to cache I/O activity such as disk. Use in correlation with Process IO Data Operations/sec and Process IO Other Operations/sec Analyses.

    References
    File Cache Performance and Tuning http://technet.microsoft.com/en-us/library/bb742613.aspx

    \Memory\System Cache Resident Bytes<br /> Warning Range: 2,147,483,648 to 3,865,470,566.4<br
/> Critical Range: 3,865,470,566.4 to 4,294,967,296

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Memory\System Cache Resident BytesMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS163,119,36063,626,58164,258,048-27,532,800368,45363,554,30463,478,05363,436,958



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Cache Bytes

    Description: Cache Bytes is the sum of the Memory\\System Cache Resident Bytes, Memory\\System Driver Resident Bytes, Memory\\System Code Resident Bytes, and Memory\\Pool Paged Resident Bytes counters. This counter displays the last observed value only; it is not an average.

    \Memory\Cache Bytes<br /> Warning Range: 3,221,225,472 to 3,865,470,566.4<br
/> Critical Range: 3,865,470,566.4 to 4,294,967,296

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Memory\Cache BytesMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS163,119,36063,626,58164,258,048-27,532,800368,45363,554,30463,478,05363,436,958



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory % Committed Bytes In Use

    Description: % Committed Bytes In Use is the ratio of Memory\Committed Bytes to the Memory\Commit Limit. Committed memory is the physical memory (RAM plus all of the page files) in use for which space has been reserved in the paging file should it need to be written to disk. The commit limit is the sum of physical RAM and the size of all of the paging files. If the paging file is enlarged, the commit limit increases, and the ratio is reduced). This counter displays the current percentage value only; it is not an average.

    This analysis checks if the amount of Commited memory is becoming close to the Commit Limit (RAM plus total page file sizes), If so, then identify if you have a memory leak. If no memory leak is identified, then consider adding more physical RAM or increase the size of your page files.

    \Memory\% Committed Bytes In Use<br /> Warning Range: 70 to 90<br
/> Critical Range: 90 to 99.999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Memory\% Committed Bytes In UseMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS118181800181818



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Pages Output/sec

    Description: Pages Output/sec is the rate at which pages are written to disk to free up space in physical memory. Pages are written back to disk only if they are changed in physical memory, so they are likely to hold data, not code. A high rate of pages output might indicate a memory shortage. Windows writes more pages back to disk to free up space when physical memory is in short supply. This counter shows the number of pages, and can be compared to other counts of pages, without conversion.

    \Memory\Pages Output/sec

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Memory\Pages Output/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Transition Pages RePurposed/sec

    Description: Transition Pages RePurposed is the rate at which the number of transition cache pages were reused for a different purpose. These pages would have otherwise remained in the page cache to provide a (fast) soft fault (instead of retrieving it from backing store) in the event the page was accessed in the future. Note these pages can contain private or sharable memory.

    \Memory\Transition Pages RePurposed/sec

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Memory\Transition Pages RePurposed/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Committed Bytes

    Description: Committed Bytes is the amount of committed virtual memory, in bytes. Committed memory is the memory which has space reserved in RAM and on the disk paging file(s). There can be one or more paging files on each physical drive. This counter displays the last observed value only; it is not an average.
    This analysis checks if the amount of total committed memory (Commit Charge) exceeds the amount of physical RAM installed. If so, the page file needs to be used to help store the committed memory and performance might degrade. To alleviate this, try to identify which process is consuming the most committed memory by looking at process Private Bytes and looking for a potential memory leak (the consumption of memory over a long period of time without releasing it). Adding more RAM to the computer will help alleviate this issue, but if it is a memory leak, then the problem might return.

    \Memory\Committed Bytes

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Memory\Committed BytesMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS12,323,709,9522,330,340,2382,339,000,320-195,264,0004,917,5262,329,307,3922,328,385,2432,328,101,179



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Commit Limit

    Description: Commit Limit is the amount of virtual memory that can be committed without having to extend the paging file(s). It is measured in bytes. Committed memory is the physical memory which has space reserved on the disk paging files. There can be one paging file on each logical drive). If the paging file(s) are be expanded, this limit increases accordingly. This counter displays the last observed value only; it is not an average.

    \Memory\Commit Limit

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Memory\Commit LimitMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS112,881,948,67212,881,948,67212,881,948,6720012,881,948,67212,881,948,67212,881,948,672



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Pages Input/sec

    Description: Pages Input/sec is the rate at which pages are read from disk to resolve hard page faults. Hard page faults occur when a process refers to a page in virtual memory that is not in its working set or elsewhere in physical memory, and must be retrieved from disk. When a page is faulted, the system tries to read multiple contiguous pages into memory to maximize the benefit of the read operation. Compare the value of Memory\\Pages Input/sec to the value of Memory\\Page Reads/sec to determine the average number of pages read into memory during each read operation.

    This analysis checks for more than 1000 page inputs per second. If there is a lot of page inputs per second, then it could be normal file I/O reading from the disk as memory mapped files, or it could be reading from the page file. This counter is not an indicator of a lack of memory condition unless there is a lot of memory pressure corresponding to this alert.

    \Memory\Pages Input/sec

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Memory\Pages Input/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1019282000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Free & Zero Page List Bytes

    Description: Free & Zero Page List Bytes is the amount of physical memory, in bytes, that is assigned to the free and zero page lists. This memory does not contain cached data. It is immediately available for allocation to a process or for system use. For a full explanation of the memory manager, refer to MSDN and/or the System Performance and Troubleshooting Guide chapter in the Windows Server 2003 Resource Kit.

    If the size of the Free and Zero page list is large, then it is a good indicator of too much RAM installed on the computer. A large amount of Free and Zero page list size is normal for computers that have been recently powered on or booted. As the system accesses the hard disk placing pages of memory into the working sets of processes, eventually many of those pages of memory will be discarded or paged out. When that happens, the memory is often placed on the Standby list. A large Standby list is preferable because it uses the extra RAM as a disk cache. Available memory is the sum of the Free, Zero, and Standby page lists, so a high amount of available memory with a low amount of Zero and Free is preferred because the system is using the extra RAM as disk cache.

    \Memory\Free & Zero Page List Bytes

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Memory\Free & Zero Page List BytesMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS13,517,157,3763,522,989,1703,526,610,944187,430,4002,804,9793,522,536,7043,521,994,4593,521,793,733



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Network Interface


    Network Interface % Network Utilization

    Description: % Network Utilization doesn’t exist as a normal performance counter, so this analysis uses multiplies \Network Interface(*)\Bytes Total/sec by 8 (to convert it to bits total/sec), divides it by \Network Interface(*)\Current Bandwidth, and multiplies the result by 100 to create a percentage. This analysis throws a warning alert when greater than 50 and throws a critical alert when greater than 80.

    % Network Utilization<br /> Warning Range: 50 to 80<br
/> Critical Range: 80 to 99.999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Network Interface(*)\% Network UtilizationMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/isatap.{F235FC61-062F-4875-A6FB-D9FEB057A7BB}00000000
    OKVIEWCS1/Local Area Connection* 1100000000
    OKVIEWCS1/vmxnet3 Ethernet Adapter _200000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Network Interface Output Queue Length

    Description:

    \Network Interface(*)\Output Queue Length<br /> Warning Range: 1 to 1.999<br
/> Critical Range: 2 to 2.999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Network Interface(*)\Output Queue LengthMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/isatap.{F235FC61-062F-4875-A6FB-D9FEB057A7BB}00000000
    OKVIEWCS1/Local Area Connection* 1100000000
    OKVIEWCS1/vmxnet3 Ethernet Adapter _200000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Network Interface % Network Utilization Sent

    Description: % Network Utilization Sent doesn’t exist as a normal performance counter, so this analysis uses multiplies \Network Interface(*)\Bytes Sent/sec by 8 (to convert it to bits total/sec), divides it by \Network Interface(*)\Current Bandwidth, and multiplies the result by 100 to create a percentage. This analysis throws a warning alert when greater than 50 and throws a critical alert when greater than 80.

    % Network Utilization Sent<br /> Warning Range: 50 to 80<br
/> Critical Range: 80 to 99.999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Network Interface(*)\% Network Utilization SentMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/vmxnet3 Ethernet Adapter _200000000
    OKVIEWCS1/Local Area Connection* 1100000000
    OKVIEWCS1/isatap.{F235FC61-062F-4875-A6FB-D9FEB057A7BB}00000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Network Interface % Network Utilization Received

    Description: % Network Utilization Received doesn’t exist as a normal performance counter, so this analysis uses multiplies \Network Interface(*)\Bytes Received/sec by 8 (to convert it to bits total/sec), divides it by \Network Interface(*)\Current Bandwidth, and multiplies the result by 100 to create a percentage. This analysis throws a warning alert when greater than 50 and throws a critical alert when greater than 80.

    % Network Utilization Received<br /> Warning Range: 50 to 80<br
/> Critical Range: 80 to 99.999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Network Interface(*)\% Network Utilization ReceivedMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/isatap.{F235FC61-062F-4875-A6FB-D9FEB057A7BB}00000000
    OKVIEWCS1/Local Area Connection* 1100000000
    OKVIEWCS1/vmxnet3 Ethernet Adapter _200000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Network Interface Packets Outbound Errors

    Description: Packets Outbound Errors is the number of outbound packets that could not be transmitted because of errors.

    If errors are occuring during this analysis, network connectivity could be affected with a potential for random Outlook RPC dialog boxes. See http://technet.microsoft.com/en-us/library/aa997363.aspx and http://technet.microsoft.com/en-us/library/aa995850.asp for more information

    \Network Interface(*)\Packets Outbound Errors<br /> Critical Range: 1 to 1.999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Network Interface(*)\Packets Outbound ErrorsMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/isatap.{F235FC61-062F-4875-A6FB-D9FEB057A7BB}00000000
    OKVIEWCS1/Local Area Connection* 1100000000
    OKVIEWCS1/vmxnet3 Ethernet Adapter _200000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Network Interface Bytes Total/sec

    Description: Bytes Total/sec is the rate at which bytes are sent and received over each network adapter, including framing characters. Network Interface\Bytes Total/sec is a sum of Network Interface\Bytes Received/sec and Network Interface\Bytes Sent/sec.

    \Network Interface(*)\Bytes Total/sec

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Network Interface(*)\Bytes Total/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/isatap.{F235FC61-062F-4875-A6FB-D9FEB057A7BB}00000000
    No ThresholdsVIEWCS1/Local Area Connection* 1100000000
    No ThresholdsVIEWCS1/vmxnet3 Ethernet Adapter _25,76611,48525,417467,4945,6869,8889,1338,526



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Network Interface Current Bandwidth

    Description: Current Bandwidth is an estimate of the current bandwidth of the network interface in bits per second (BPS). For interfaces that do not vary in bandwidth or for those where no accurate estimation can be made, this value is the nominal bandwidth.

    \Network Interface(*)\Current Bandwidth

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Network Interface(*)\Current BandwidthMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/isatap.{F235FC61-062F-4875-A6FB-D9FEB057A7BB}100,000100,000100,00000100,000100,000100,000
    No ThresholdsVIEWCS1/Local Area Connection* 11100,000100,000100,00000100,000100,000100,000
    No ThresholdsVIEWCS1/vmxnet3 Ethernet Adapter _210,000,000,00010,000,000,00010,000,000,0000010,000,000,00010,000,000,00010,000,000,000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Network Interface Packets/sec

    Description: Packets/sec is the rate at which packets are sent and received on the network interface.

    \Network Interface(*)\Packets/sec

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Network Interface(*)\Packets/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/isatap.{F235FC61-062F-4875-A6FB-D9FEB057A7BB}00000000
    No ThresholdsVIEWCS1/Local Area Connection* 1100000000
    No ThresholdsVIEWCS1/vmxnet3 Ethernet Adapter _23248811,06917444139



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Network Interface Packets Sent/sec

    Description: Packets Sent/sec is the rate at which packets are sent on the network interface.

    \Network Interface(*)\Packets Sent/sec

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Network Interface(*)\Packets Sent/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/isatap.{F235FC61-062F-4875-A6FB-D9FEB057A7BB}00000000
    No ThresholdsVIEWCS1/Local Area Connection* 1100000000
    No ThresholdsVIEWCS1/vmxnet3 Ethernet Adapter _21422404788201918



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Network Interface Packets Received/sec

    Description: Packets Received/sec is the rate at which packets are received on the network interface.

    \Network Interface(*)\Packets Received/sec

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Network Interface(*)\Packets Received/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/isatap.{F235FC61-062F-4875-A6FB-D9FEB057A7BB}00000000
    No ThresholdsVIEWCS1/Local Area Connection* 1100000000
    No ThresholdsVIEWCS1/vmxnet3 Ethernet Adapter _21726446198242221



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Paging File


    Paging File % Usage

    Description: The amount of the Page File instance in use in percent. See also Process\\Page File Bytes.

    This analysis checks if the percentage of usage is greater than 70%.

    Reference
    How to determine the appropriate page file size for 64-bit versions of Windows Server 2003 or Windows XP
    http://support.microsoft.com/kb/889654

    \Paging File(*)\% Usage<br /> Warning Range: 70 to 90<br
/> Critical Range: 90 to 99.999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Paging File(*)\% UsageMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/\??\C:\pagefile.sys00000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    PhysicalDisk


    PhysicalDisk Read Latency Analysis

    Description: Avg. Disk sec/Read is the average time, in seconds, of a read of data to the disk. This analysis determines if any of the physical disks are responding slowly.

    If the response times are greater than .015 (15 milliseconds), then the disk subsystem is keeping up with demand, but does not have much overhead left.

    If the response times are greater than .025 (25 milliseconds), then noticeable slow downs and performance issues affecting users may be occurring.

    Reference:
    Ruling Out Disk-Bound Problems
    http://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx

    \PhysicalDisk(*)\Avg. Disk sec/Read<br /> Warning Range: .015 to .025<br
/> Critical Range: .025 to .029999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\PhysicalDisk(*)\Avg. Disk sec/ReadMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/0 C:00000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    PhysicalDisk Write Latency Analysis

    Description: Avg. Disk sec/Write is the average time, in seconds, of a write of data to the disk. This analysis determines if any of the physical disks are responding slowly.

    If the response times are greater than .015 (15 milliseconds), then the disk subsystem is keeping up with demand, but does not have much overhead left.

    If the response times are greater than .025 (25 milliseconds), then noticeable slow downs and performance issues affecting users may be occurring.

    Reference:
    Ruling Out Disk-Bound Problems
    http://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx

    \PhysicalDisk(*)\Avg. Disk sec/Write<br /> Warning Range: .015 to .025<br
/> Critical Range: .025 to .029999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\PhysicalDisk(*)\Avg. Disk sec/WriteMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/0 C:.001.001.00100.001.001.001



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    PhysicalDisk Current Disk Queue Length

    Description: Current Disk Queue Length is the number of requests outstanding on the disk at the time the performance data is collected. It also includes requests in service at the time of the collection. This is a instantaneous snapshot, not an average over the time interval. Multi-spindle disk devices can have multiple requests that are active at one time, but other concurrent requests are awaiting service. This counter might reflect a transitory high or low queue length, but if there is a sustained load on the disk drive, it is likely that this will be consistently high. Requests experience delays proportional to the length of this queue minus the number of spindles on the disks. For good performance, this difference should average less than two.

    If the server is using an HBA (Host Bus Adapter: This is used to connect to a Storage Area Network SAN) and if the Current Disk Queue Length goes up to 32 frequently, then consider increasing the queue depth on the HBA to allow more concurrent I/O to the SAN. Please consult your SAN administrator before making any changes.

    \PhysicalDisk(*)\Current Disk Queue Length

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\PhysicalDisk(*)\Current Disk Queue LengthMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/0 C:00100000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    PhysicalDisk Avg. Disk Queue Length

    Description: Avg. Disk Queue Length is the average number of both read and write requests that were queued for the selected disk during the sample interval.

    \PhysicalDisk(*)\Avg. Disk Queue Length<br /> Warning Range: 2 to 4

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\PhysicalDisk(*)\Avg. Disk Queue LengthMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/0 C:00000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    PhysicalDisk Disk Bytes/sec

    Description: Disk Bytes/sec is the rate bytes are transferred to or from the disk during write or read operations.

    \PhysicalDisk(*)\Disk Bytes/sec

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\PhysicalDisk(*)\Disk Bytes/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/0 C:11,46327,750124,785-187,70625,65321,06120,50619,212



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    PhysicalDisk Calculated IOPS

    Description: Disk Reads/sec is the rate of read operations on the disk.

    \PhysicalDisk(*)\Disk Reads/sec

    \PhysicalDisk(*)\Disk Writes/sec

    \PhysicalDisk(*)\Calculated IOPS

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\PhysicalDisk(*)\Disk Reads/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/0 C:00201000

    Condition\PhysicalDisk(*)\Disk Writes/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/0 C:247-841433

    Condition\PhysicalDisk(*)\Calculated IOPSMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/0 C:00902000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Process


    Process Private Bytes

    Description: This analysis determines if the system leaking memory over time. A process consuming large portions of memory is okay as long as the process returns the memory back to the system. Look for increasing trends in the chart. An increasing trend over a long period of time could indicate a memory leak. Private Bytes is the current size, in bytes, of memory that this process has allocated that cannot be shared with other processes. This analysis checks for a 10 MB per hour and 5 MB per hour increasing trends. Use this analysis in correlation with the Available Memory analysis.

    Use this analysis in correlation with the Available Memory analysis. If you suspect a memory leak condition, then install and use the Debug Diag tool. For more information on the Debug Diag Tool, see the references section.

    References:

    Debug Diagnostic Tool v1.1 http://www.microsoft.com/downloads/details.aspx?FamilyID=28bd5941-c458-46f1-b24d-f60151d875a3&displaylang=en

    \Process(*)\Private Bytes

    \Process(*)\Private Bytes

    \Process(*)\Private Bytes

    \Process(*)\Private Bytes

    \Process(*)\Private Bytes

    \Process(*)\Private Bytes

    \Process(*)\Private Bytes

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Process(*)\Private BytesMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/_Total1,772,036,0961,779,402,7521,787,330,560-9,561,6004,606,3451,778,440,9601,777,529,7101,777,154,206
    OKVIEWCS1/avagent6,139,9046,346,9806,430,7207,372,800108,3636,336,5126,325,1026,318,868
    OKVIEWCS1/avscc7,184,3847,184,3847,184,384007,184,3847,184,3847,184,384
    OKVIEWCS1/csrss#17,987,2007,987,2007,987,200007,987,2007,987,2007,987,200
    OKVIEWCS1/csrss#22,076,6722,076,6722,076,672002,076,6722,076,6722,076,672
    OKVIEWCS1/csrss2,191,3602,191,3602,191,360002,191,3602,191,3602,191,360
    OKVIEWCS1/dllhost#11,921,0241,921,0241,921,024001,921,0241,921,0241,921,024
    OKVIEWCS1/dllhost4,349,9524,349,9524,349,952004,349,9524,349,9524,349,952
    OKVIEWCS1/dsamain36,261,88836,301,93836,339,7121,612,80028,18836,297,72836,294,07136,291,820
    OKVIEWCS1/dwm1,589,2481,589,2481,589,248001,589,2481,589,2481,589,248
    OKVIEWCS1/explorer14,254,08014,453,41914,954,496-17,510,400234,37314,391,80814,356,48014,334,740
    OKVIEWCS1/FlashUtil32_11_4_402_278_ActiveX2,469,8882,469,8882,469,888002,469,8882,469,8882,469,888
    OKVIEWCS1/Idle00000000
    OKVIEWCS1/iexplore#182,227,20082,227,20082,227,2000082,227,20082,227,20082,227,200
    OKVIEWCS1/iexplore#215,691,77615,728,18515,835,1361,036,80052,65915,714,81615,702,30915,700,283
    OKVIEWCS1/iexplore#358,568,70458,568,70458,568,7040058,568,70458,568,70458,568,704
    OKVIEWCS1/iexplore9,064,4489,167,5319,175,040025,8399,166,5929,165,3859,164,642
    OKVIEWCS1/LogonUI8,704,0008,704,0008,704,000008,704,0008,704,0008,704,000
    OKVIEWCS1/lsass7,303,1687,314,7737,372,800-1,958,40026,7037,307,5207,303,1687,303,168
    OKVIEWCS1/lsm3,104,7683,187,5983,219,456-3,225,60052,8583,183,6163,178,4963,175,345
    OKVIEWCS1/Microsoft.ActiveDirectory.WebServices45,813,76045,930,26846,862,3360339,08945,813,76045,813,76045,813,760
    OKVIEWCS1/mmc#152,240,38452,240,38452,240,3840052,240,38452,240,38452,240,384
    OKVIEWCS1/mmc#228,495,87228,665,85629,446,144-26,726,400287,54928,568,32028,563,45628,560,463
    OKVIEWCS1/mmc11,980,80011,980,80011,980,8000011,980,80011,980,80011,980,800
    OKVIEWCS1/msdtc3,461,1203,461,1203,461,120003,461,1203,461,1203,461,120
    OKVIEWCS1/rdpclip1,843,2001,868,6861,904,640-115,20026,3421,864,1921,858,4141,854,858
    OKVIEWCS1/rundll327,716,8648,052,0538,155,13612,326,400140,7258,039,1688,022,6018,012,406
    OKVIEWCS1/SecurityGateway2,699,2642,731,8042,834,4321,497,60044,7702,718,9762,714,1852,711,237
    OKVIEWCS1/services4,673,5364,717,9094,726,784020,4204,716,8004,715,3744,714,496
    OKVIEWCS1/smss466,944466,944466,94400466,944466,944466,944
    OKVIEWCS1/spoolsv7,368,7047,374,6207,421,952-1,497,60017,2197,368,7047,368,7047,368,704
    OKVIEWCS1/svchost#13,809,2803,905,7644,009,984-460,80069,5003,892,7363,875,9863,866,939
    OKVIEWCS1/svchost#101,900,5441,900,5441,900,544001,900,5441,900,5441,900,544
    OKVIEWCS1/svchost#111,478,6561,478,6561,478,656001,478,6561,478,6561,478,656
    OKVIEWCS1/svchost#210,346,49610,358,32910,399,744-1,497,60022,77910,353,15210,346,49610,346,496
    OKVIEWCS1/svchost#318,165,76018,454,75618,620,416-12,441,600163,63018,434,81618,416,49418,405,218
    OKVIEWCS1/svchost#46,447,1046,473,7286,500,3521,497,60027,3966,470,4006,466,1216,463,488
    OKVIEWCS1/svchost#54,120,5764,120,5764,120,576004,120,5764,120,5764,120,576
    OKVIEWCS1/svchost#612,857,34412,962,70213,012,9921,497,60047,01312,956,41612,948,33412,943,360
    OKVIEWCS1/svchost#710,371,07210,387,68410,424,320230,40023,61210,383,10410,377,21610,373,593
    OKVIEWCS1/svchost#8942,080942,080942,08000942,080942,080942,080
    OKVIEWCS1/svchost#93,170,3043,191,0123,223,552-1,497,60026,7113,186,9443,181,7143,178,496
    OKVIEWCS1/svchost4,096,0004,154,7094,206,592-2,995,20039,1364,148,2244,140,4714,135,700
    OKVIEWCS1/System114,688114,688114,68800114,688114,688114,688
    OKVIEWCS1/taskeng1,839,1041,920,7961,953,792-1,497,60038,1531,916,6721,911,3691,908,106
    OKVIEWCS1/taskhost2,740,2242,740,2242,740,224002,740,2242,740,2242,740,224
    OKVIEWCS1/ViewTopoSvc144,412,672147,640,320150,740,992-57,024,0002,381,376147,252,736146,754,414146,447,754
    OKVIEWCS1/vmtoolsd#15,312,5125,312,5125,312,512005,312,5125,312,5125,312,512
    OKVIEWCS1/vmtoolsd7,229,4407,276,3167,286,784021,0377,275,0087,273,3267,272,290
    OKVIEWCS1/VMwareTray3,072,0003,126,6133,153,920-2,304,00039,7373,123,2003,118,8113,116,111
    OKVIEWCS1/vmware-usbarbitrator2,330,6242,330,6242,330,624002,330,6242,330,6242,330,624
    OKVIEWCS1/wininit1,495,0401,495,0401,495,040001,495,0401,495,0401,495,040
    OKVIEWCS1/winlogon#11,691,6481,691,6481,691,648001,691,6481,691,6481,691,648
    OKVIEWCS1/winlogon1,449,9841,449,9841,449,984001,449,9841,449,9841,449,984
    OKVIEWCS1/WmiApSrv2,347,0082,395,4772,424,832576,00024,1002,391,8082,387,0902,384,502
    OKVIEWCS1/WmiPrvSE#12,854,9122,954,7523,076,096-6,220,800110,3852,937,4172,914,3042,914,304
    OKVIEWCS1/WmiPrvSE2,494,4642,604,1462,736,128-806,40064,7412,587,6482,579,6022,575,124
    OKVIEWCS1/ws_ConnectionServer2,527,2322,527,2322,527,232002,527,2322,527,2322,527,232
    OKVIEWCS1/ws_MessageBusService373,342,208375,081,870375,918,59260,940,8001,075,388374,977,280374,857,143374,791,562
    OKVIEWCS1/ws_TomcatService428,060,672435,444,622442,257,408175,104,0003,455,052434,882,048434,569,216434,392,143
    OKVIEWCS1/ws_TunnelService253,501,440255,076,580255,688,704-56,448,000884,069255,003,904254,914,853254,861,627
    OKVIEWCS1/wsnm14,024,70414,084,09614,106,6241,267,20025,91514,081,28014,077,65914,075,431



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Process Handle Count

    Description: This analysis checks overall system to determine how many handles the system has open to determine if there is a handle leak. Handle leaks can be attributed to memory leak. If this analysis throws alerts, then you need to manually open the performance monitor log and look at the instances \Process(*)\Handle Count to determine which process is leaking handles. Note: The normal System Overview analysis checks all of the processes.

    \Process(*)\Handle Count

    \Process(*)\Handle Count

    \Process(*)\Handle Count

    \Process(*)\Handle Count

    \Process(*)\Handle Count

    \Process(*)\Handle Count

    \Process(*)\Handle Count

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Process(*)\Handle CountMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/_Total21,55721,73722,058-9,81617021,70421,67621,659
    OKVIEWCS1/avagent173179187-2534178178177
    OKVIEWCS1/avscc13813813800138138138
    OKVIEWCS1/csrss#172727200727272
    OKVIEWCS1/csrss#2299304315-4225303302302
    OKVIEWCS1/csrss1,1451,1641,187-534141,1611,1581,157
    OKVIEWCS1/dllhost#110510510500105105105
    OKVIEWCS1/dllhost19719719700197197197
    OKVIEWCS1/dsamain531533540-283532532532
    OKVIEWCS1/dwm74747400747474
    OKVIEWCS1/explorer549560614-1,74415556554553
    OKVIEWCS1/FlashUtil32_11_4_402_278_ActiveX13013013000130130130
    OKVIEWCS1/Idle00000000
    OKVIEWCS1/iexplore#150550550500505505505
    OKVIEWCS1/iexplore#2558560564282560560560
    OKVIEWCS1/iexplore#352152152100521521521
    OKVIEWCS1/iexplore56957357301572572572
    OKVIEWCS1/LogonUI16416416400164164164
    OKVIEWCS1/lsass9911,0091,032-844131,0061,0041,002
    OKVIEWCS1/lsm238241245-1972240240240
    OKVIEWCS1/Microsoft.ActiveDirectory.WebServices26726827202267267267
    OKVIEWCS1/mmc#132932932900329329329
    OKVIEWCS1/mmc#2622629652-8169626626625
    OKVIEWCS1/mmc19519519500195195195
    OKVIEWCS1/msdtc14714714700147147147
    OKVIEWCS1/rdpclip153156161-1973155155154
    OKVIEWCS1/rundll32257260261-281259259259
    OKVIEWCS1/SecurityGateway86868600868686
    OKVIEWCS1/services26626826801268268268
    OKVIEWCS1/smss33333300333333
    OKVIEWCS1/spoolsv29529529500295295295
    OKVIEWCS1/svchost#1284291303-3386290288288
    OKVIEWCS1/svchost#1010410410400104104104
    OKVIEWCS1/svchost#1169696900696969
    OKVIEWCS1/svchost#2316322330-2815321319319
    OKVIEWCS1/svchost#39889961,011-6478994993993
    OKVIEWCS1/svchost#4531532533561532532532
    OKVIEWCS1/svchost#522922922900229229229
    OKVIEWCS1/svchost#64674734782254473472472
    OKVIEWCS1/svchost#7317319322-282319319319
    OKVIEWCS1/svchost#847474700474747
    OKVIEWCS1/svchost#9282284287-1412284284283
    OKVIEWCS1/svchost359362365-1692362361361
    OKVIEWCS1/System548549552-1121549549549
    OKVIEWCS1/taskeng879193-562909090
    OKVIEWCS1/taskhost12712712700127127127
    OKVIEWCS1/ViewTopoSvc93796898475916966964963
    OKVIEWCS1/vmtoolsd#116416416400164164164
    OKVIEWCS1/vmtoolsd25025225201252252252
    OKVIEWCS1/VMwareTray717273-561727272
    OKVIEWCS1/vmware-usbarbitrator10110110100101101101
    OKVIEWCS1/wininit79797900797979
    OKVIEWCS1/winlogon#110010010000100100100
    OKVIEWCS1/winlogon77777700777777
    OKVIEWCS1/WmiApSrv117120124-1413120119118
    OKVIEWCS1/WmiPrvSE#1139142147-1694142141141
    OKVIEWCS1/WmiPrvSE113117120-1413116116115
    OKVIEWCS1/ws_ConnectionServer14114114100141141141
    OKVIEWCS1/ws_MessageBusService616621625-1693621620620
    OKVIEWCS1/ws_TomcatService1,5521,5611,57228161,5591,5581,558
    OKVIEWCS1/ws_TunnelService2,3902,3912,393-2812,3912,3912,391
    OKVIEWCS1/wsnm5175215282814520520519



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    Time Range
    9/25/2012 11:30:36 AM – 9/25/2012 11:30:51 AMConditionCounterMinAvgMaxHourly Trend
    Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour\\VIEWCS1\Process(_Total)\Handle Count22,05822,05822,05816,200


    Back to the top

    Process Thread Count

    Description: The number of threads currently active in this process. An instruction is the basic unit of execution in a processor, and a thread is the object that executes instructions. Every running process has at least one thread.

    This analysis checks all of the processes to determine if a process has more than 500 threads and if it is on an increasing trend of 50 threads per hour. A process with a large number of threads and/or an aggressive upward trend could indicate a thread leak which typically results in either a memory leak or high context switching. High context switching will result in high privileged mode CPU.

    \Process(*)\Thread Count

    \Process(*)\Thread Count

    \Process(*)\Thread Count

    \Process(*)\Thread Count

    \Process(*)\Thread Count

    \Process(*)\Thread Count

    \Process(*)\Thread Count

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Process(*)\Thread CountMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/_Total1,1381,1601,188-1,012181,1571,1541,151
    OKVIEWCS1/avagent13151601151515
    OKVIEWCS1/avscc77700777
    OKVIEWCS1/csrss#199900999
    OKVIEWCS1/csrss#299900999
    OKVIEWCS1/csrss99900999
    OKVIEWCS1/dllhost#166600666
    OKVIEWCS1/dllhost13131300131313
    OKVIEWCS1/dsamain262727281272626
    OKVIEWCS1/dwm33300333
    OKVIEWCS1/explorer182023-1122191919
    OKVIEWCS1/FlashUtil32_11_4_402_278_ActiveX33300333
    OKVIEWCS1/Idle22200222
    OKVIEWCS1/iexplore#115151500151515
    OKVIEWCS1/iexplore#217171800171717
    OKVIEWCS1/iexplore#315151500151515
    OKVIEWCS1/iexplore13141400141414
    OKVIEWCS1/LogonUI66600666
    OKVIEWCS1/lsass9910-280999
    OKVIEWCS1/lsm91010-280101010
    OKVIEWCS1/Microsoft.ActiveDirectory.WebServices12121300121212
    OKVIEWCS1/mmc#115151500151515
    OKVIEWCS1/mmc#2202228-2252212121
    OKVIEWCS1/mmc44400444
    OKVIEWCS1/msdtc12121200121212
    OKVIEWCS1/rdpclip78901887
    OKVIEWCS1/rundll3291011561101010
    OKVIEWCS1/SecurityGateway77700777
    OKVIEWCS1/services67700777
    OKVIEWCS1/smss33300333
    OKVIEWCS1/spoolsv121213-280121212
    OKVIEWCS1/svchost#17810-561888
    OKVIEWCS1/svchost#1055500555
    OKVIEWCS1/svchost#1155500555
    OKVIEWCS1/svchost#2131314-280131313
    OKVIEWCS1/svchost#3282830-561282828
    OKVIEWCS1/svchost#4101011281101010
    OKVIEWCS1/svchost#577700777
    OKVIEWCS1/svchost#6171920281191919
    OKVIEWCS1/svchost#717171800171717
    OKVIEWCS1/svchost#833300333
    OKVIEWCS1/svchost#9101011-281101010
    OKVIEWCS1/svchost101112-561111111
    OKVIEWCS1/System959698-841969595
    OKVIEWCS1/taskeng567-281666
    OKVIEWCS1/taskhost66600666
    OKVIEWCS1/ViewTopoSvc535759-282565656
    OKVIEWCS1/vmtoolsd#122200222
    OKVIEWCS1/vmtoolsd68801888
    OKVIEWCS1/VMwareTray245-841444
    OKVIEWCS1/vmware-usbarbitrator33300333
    OKVIEWCS1/wininit33300333
    OKVIEWCS1/winlogon#133300333
    OKVIEWCS1/winlogon33300333
    OKVIEWCS1/WmiApSrv567-561666
    OKVIEWCS1/WmiPrvSE#1778-281777
    OKVIEWCS1/WmiPrvSE678-561777
    OKVIEWCS1/ws_ConnectionServer13131300131313
    OKVIEWCS1/ws_MessageBusService535659-1122565655
    OKVIEWCS1/ws_TomcatService1291341401413133132132
    OKVIEWCS1/ws_TunnelService254255257-281255255255
    OKVIEWCS1/wsnm404243561424242



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Process Working Set

    Description: Working Set is the current size, in bytes, of the Working Set of a process. The Working Set is the set of memory pages touched recently by the threads in the process. It is the amount of RAM consumed by each process. If available physical memory (RAM) in the computer is above a threshold, pages are left in the Working Set of a process longer. When available memory falls below a threshold, pages are trimmed from Working Sets more frequently than when not in a low available memory condition. If the trimmed page are still in RAM, but not in the processes working set (due to being trimmed), then some of them may be soft-faulted (RAM to RAM) back into the Working Set.
    This analysis checks for an increasing trend of 100 MB or more per hour in all of the processes combined. This could be an aggressive working set (RAM usage) leak, but keep in mind that this is only tracking the amount of RAM used by all of the processes and does not include committed memory that has trimmed from the working set. This is generally why Private Bytes is a better counter to use for general memory leaks. With that said, Working Set is a helpful counter to have when analyzing low physical memory conditions that might be induced by page locking which can preven the virtual memory manager from trimming. Use this analysis in correlation with Available Memory Analysis.

    Reference:

    \Process(*)\Working Set

    \Process(*)\Working Set

    \Process(*)\Working Set

    \Process(*)\Working Set

    \Process(*)\Working Set

    \Process(*)\Working Set

    \Process(*)\Working Set

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Process(*)\Working SetMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/_Total1,658,892,2881,663,753,5571,671,376,896-228,441,6004,100,3341,662,985,2161,662,258,0301,661,839,518
    OKVIEWCS1/avagent13,336,57613,449,89913,500,4164,032,00058,09613,443,58413,436,92813,433,305
    OKVIEWCS1/avscc13,099,00813,099,00813,099,0080013,099,00813,099,00813,099,008
    OKVIEWCS1/csrss#16,955,0086,955,0086,955,008006,955,0086,955,0086,955,008
    OKVIEWCS1/csrss#26,094,8486,112,5976,254,592-4,492,80051,6586,094,8486,094,8486,094,848
    OKVIEWCS1/csrss4,321,2804,323,5564,333,568-115,2003,2114,322,8164,322,4504,322,225
    OKVIEWCS1/dllhost#15,509,1205,509,1205,509,120005,509,1205,509,1205,509,120
    OKVIEWCS1/dllhost11,456,51211,456,51211,456,5120011,456,51211,456,51211,456,512
    OKVIEWCS1/dsamain37,036,03237,079,72337,130,2401,612,80021,44537,074,94437,072,60337,071,321
    OKVIEWCS1/dwm4,820,9924,820,9924,820,992004,820,9924,820,9924,820,992
    OKVIEWCS1/explorer32,182,27232,349,52533,005,568-22,694,400213,83532,287,74432,264,77732,250,644
    OKVIEWCS1/FlashUtil32_11_4_402_278_ActiveX7,143,4247,143,4247,143,424007,143,4247,143,4247,143,424
    OKVIEWCS1/Idle24,57624,57624,5760024,57624,57624,576
    OKVIEWCS1/iexplore#196,505,85696,505,85696,505,8560096,505,85696,505,85696,505,856
    OKVIEWCS1/iexplore#230,670,84830,690,87330,736,3841,036,80024,45130,685,18430,681,38130,679,355
    OKVIEWCS1/iexplore#372,499,20072,499,20072,499,2000072,499,20072,499,20072,499,200
    OKVIEWCS1/iexplore24,428,54424,541,18424,592,3841,843,20038,06924,534,78424,531,23724,529,054
    OKVIEWCS1/LogonUI15,753,21615,753,21615,753,2160015,753,21615,753,21615,753,216
    OKVIEWCS1/lsass15,802,36815,805,09915,818,752-460,8006,28315,803,39215,802,36815,802,368
    OKVIEWCS1/lsm6,275,0726,298,7386,307,840-921,60015,1026,297,6006,296,1376,295,237
    OKVIEWCS1/Microsoft.ActiveDirectory.WebServices43,171,84043,173,88843,192,32006,00243,171,84043,171,84043,171,840
    OKVIEWCS1/mmc#124,018,94424,096,31324,182,7844,262,40051,52224,086,27224,077,75124,072,507
    OKVIEWCS1/mmc#244,347,39244,472,32044,765,184-8,985,600108,53644,435,96844,433,40844,432,148
    OKVIEWCS1/mmc4,161,5364,161,5364,161,536004,161,5364,161,5364,161,536
    OKVIEWCS1/msdtc8,036,3528,036,3528,036,352008,036,3528,036,3528,036,352
    OKVIEWCS1/rdpclip5,668,8645,702,3155,718,016806,40011,5215,700,3525,698,7065,698,166
    OKVIEWCS1/rundll3213,357,05613,733,43313,811,71212,787,200123,16013,723,64813,711,06713,703,326
    OKVIEWCS1/SecurityGateway7,053,3127,060,1397,094,272-115,20012,5667,055,8727,055,6537,055,518
    OKVIEWCS1/services10,862,59210,883,52710,895,360-460,80010,59710,882,04810,880,14610,878,976
    OKVIEWCS1/smss1,118,2081,118,2081,118,208001,118,2081,118,2081,118,208
    OKVIEWCS1/spoolsv13,152,25613,154,07613,168,640-460,8005,29813,152,25613,152,25613,152,256
    OKVIEWCS1/svchost#17,991,2968,069,5758,122,3681,036,80039,1598,062,9768,054,4918,050,530
    OKVIEWCS1/svchost#105,505,0245,505,0245,505,024005,505,0245,505,0245,505,024
    OKVIEWCS1/svchost#114,435,9684,435,9684,435,968004,435,9684,435,9684,435,968
    OKVIEWCS1/svchost#213,328,38413,333,84513,352,960-691,20010,51313,331,45613,328,38413,328,384
    OKVIEWCS1/svchost#331,555,58431,810,44631,932,416-10,368,000142,47031,795,71231,780,27931,770,782
    OKVIEWCS1/svchost#411,542,52811,550,72011,558,912460,8008,42911,549,69611,548,37911,547,569
    OKVIEWCS1/svchost#511,010,04811,010,04811,010,0480011,010,04811,010,04811,010,048
    OKVIEWCS1/svchost#617,690,62417,773,90917,809,4082,419,20029,86917,769,47217,763,76717,761,831
    OKVIEWCS1/svchost#713,344,76813,354,09813,365,248345,6007,92313,352,70413,350,91213,350,124
    OKVIEWCS1/svchost#82,711,5522,711,5522,711,552002,711,5522,711,5522,711,552
    OKVIEWCS1/svchost#98,863,7448,876,4878,892,416-806,40011,2308,874,4968,872,5218,871,306
    OKVIEWCS1/svchost9,699,3289,726,6359,748,480-921,60015,8959,723,9049,722,7349,722,014
    OKVIEWCS1/System311,296311,296311,29600311,296311,296311,296
    OKVIEWCS1/taskeng4,947,9684,970,9514,984,832691,20012,3394,969,2164,966,9854,965,612
    OKVIEWCS1/taskhost6,053,8886,053,8886,053,888006,053,8886,053,8886,053,888
    OKVIEWCS1/ViewTopoSvc98,082,81698,178,16298,246,656-806,40058,02598,169,60098,158,59298,151,818
    OKVIEWCS1/vmtoolsd#111,186,17611,186,17611,186,1760011,186,17611,186,17611,186,176
    OKVIEWCS1/vmtoolsd14,225,40814,260,45214,270,464115,20015,01514,259,20014,257,88314,257,231
    OKVIEWCS1/VMwareTray5,693,4405,733,4905,754,880-1,728,00029,1865,730,8165,727,3785,725,263
    OKVIEWCS1/vmware-usbarbitrator5,246,9765,246,9765,246,976005,246,9765,246,9765,246,976
    OKVIEWCS1/wininit4,390,9124,390,9124,390,912004,390,9124,390,9124,390,912
    OKVIEWCS1/winlogon#14,980,7364,980,7364,980,736004,980,7364,980,7364,980,736
    OKVIEWCS1/winlogon4,227,0724,227,0724,227,072004,227,0724,227,0724,227,072
    OKVIEWCS1/WmiApSrv7,024,6407,103,6027,122,9442,073,60022,5147,101,1847,098,6617,097,423
    OKVIEWCS1/WmiPrvSE#16,983,6807,155,7127,344,128-9,100,800184,1837,128,7957,094,9557,094,955
    OKVIEWCS1/WmiPrvSE6,164,4806,272,7966,361,0883,225,60071,4476,261,7606,251,0816,245,140
    OKVIEWCS1/ws_ConnectionServer7,036,9287,036,9287,036,928007,036,9287,036,9287,036,928
    OKVIEWCS1/ws_MessageBusService211,431,424212,182,812212,537,34427,648,000384,499212,139,264212,091,758212,066,619
    OKVIEWCS1/ws_TomcatService342,073,344344,798,549350,351,36010,598,4001,596,012344,414,720344,332,288344,289,280
    OKVIEWCS1/ws_TunnelService187,023,360188,258,759188,739,584-43,430,400682,813188,202,752188,135,424188,095,567
    OKVIEWCS1/wsnm22,376,44822,414,22222,437,888-460,80023,10922,411,26422,407,46122,405,435



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    Time Range
    9/25/2012 11:30:36 AM – 9/25/2012 11:30:51 AMConditionCounterMinAvgMaxHourly Trend
    The working set of all processes combined is increasing at a rate greater than 100MBs per hour\\VIEWCS1\Process(_Total)\Working Set1,671,376,8961,671,376,8961,671,376,896556,646,400


    Back to the top

    Process % Processor Time

    Description: This analysis checks all of the processes to determine if any of the processes are consuming a large amount of CPU.

    If a user-mode processor bottleneck is suspected, then consider using a process profiler to analyze the functions causing the high CPU consumption. See How To: Identify Functions causing a High User-mode CPU Bottleneck for Server Applications in a Production Environment article in the references section for more information.

    Role Specific

    - Process(MSExchangeMailboxAssistants*)\%Processor Time should be less than 5% of overll CPU

    - Process(msftefd*)\%Processor Time should be less than 10% of what the store process is consuming. Note: If indexing is running and overall CPU is greater than 80%, then msfte should backoff it’s CPU usage if that threshold is hit.

    References:
    Measuring .NET Application Performance
    http://msdn2.microsoft.com/en-us/library/ms998579.aspx

    How To: Identify Functions causing a High User-mode CPU Bottleneck for Server Applications in a Production Environment http://www.codeplex.com/PerfTesting/Wiki/View.aspx?title=How%20To%3a%20Identify%20a%20Disk%20Performance%20Bottleneck%20Using%20SPA&referringTitle=How%20Tos

    \Process(*)\% Processor Time

    \Process(*)\% Processor Time

    \Process(*)\% Processor Time

    \Process(*)\% Processor Time

    \Process(*)\% Processor Time

    \Process(*)\% Processor Time

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Process(*)\% Processor TimeMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/avagent00000000
    No ThresholdsVIEWCS1/avscc00000000
    No ThresholdsVIEWCS1/csrss#100000000
    No ThresholdsVIEWCS1/csrss#200000000
    No ThresholdsVIEWCS1/csrss00000000
    No ThresholdsVIEWCS1/dllhost#1--------
    No ThresholdsVIEWCS1/dllhost00000000
    No ThresholdsVIEWCS1/dsamain00100000
    No ThresholdsVIEWCS1/dwm00000000
    No ThresholdsVIEWCS1/explorer00000000
    No ThresholdsVIEWCS1/FlashUtil32_11_4_402_278_ActiveX00000000
    No ThresholdsVIEWCS1/iexplore#100000000
    No ThresholdsVIEWCS1/iexplore#200100000
    No ThresholdsVIEWCS1/iexplore#300000000
    No ThresholdsVIEWCS1/iexplore00000000
    No ThresholdsVIEWCS1/LogonUI00000000
    No ThresholdsVIEWCS1/lsass00000000
    No ThresholdsVIEWCS1/lsm00000000
    No ThresholdsVIEWCS1/Microsoft.ActiveDirectory.WebServices00000000
    No ThresholdsVIEWCS1/mmc#100000000
    No ThresholdsVIEWCS1/mmc#2002561000
    No ThresholdsVIEWCS1/mmc00000000
    No ThresholdsVIEWCS1/msdtc00000000
    No ThresholdsVIEWCS1/rdpclip00000000
    No ThresholdsVIEWCS1/rundll3200000000
    No ThresholdsVIEWCS1/SecurityGateway00000000
    No ThresholdsVIEWCS1/services00000000
    No ThresholdsVIEWCS1/smss00000000
    No ThresholdsVIEWCS1/spoolsv00000000
    No ThresholdsVIEWCS1/svchost#100000000
    No ThresholdsVIEWCS1/svchost#1000000000
    No ThresholdsVIEWCS1/svchost#1100000000
    No ThresholdsVIEWCS1/svchost#200000000
    No ThresholdsVIEWCS1/svchost#300000000
    No ThresholdsVIEWCS1/svchost#400000000
    No ThresholdsVIEWCS1/svchost#500000000
    No ThresholdsVIEWCS1/svchost#600000000
    No ThresholdsVIEWCS1/svchost#700000000
    No ThresholdsVIEWCS1/svchost#800000000
    No ThresholdsVIEWCS1/svchost#900000000
    No ThresholdsVIEWCS1/svchost00000000
    No ThresholdsVIEWCS1/System00000000
    No ThresholdsVIEWCS1/taskeng00000000
    No ThresholdsVIEWCS1/taskhost00000000
    No ThresholdsVIEWCS1/ViewTopoSvc00000000
    No ThresholdsVIEWCS1/vmtoolsd#100000000
    No ThresholdsVIEWCS1/vmtoolsd00000000
    No ThresholdsVIEWCS1/VMwareTray00000000
    No ThresholdsVIEWCS1/vmware-usbarbitrator00000000
    No ThresholdsVIEWCS1/wininit00000000
    No ThresholdsVIEWCS1/winlogon#100000000
    No ThresholdsVIEWCS1/winlogon00000000
    No ThresholdsVIEWCS1/WmiApSrv00000000
    No ThresholdsVIEWCS1/WmiPrvSE#100000000
    No ThresholdsVIEWCS1/WmiPrvSE00000000
    No ThresholdsVIEWCS1/ws_ConnectionServer00000000
    No ThresholdsVIEWCS1/ws_MessageBusService001-280000
    No ThresholdsVIEWCS1/ws_TomcatService015281110
    No ThresholdsVIEWCS1/ws_TunnelService00000000
    No ThresholdsVIEWCS1/wsnm00000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Process Virtual Bytes

    Description: This analysis determines if any of the processes are consuming a large of virtual memory. 32-bit processes by default are only allowed to access up to 2 GB of user mode memory. If the process becomes close to this maximum, then it could starve for memory. If a process is becoming close to it’s maximum, then consider moving the process to a 64-bit system. On 32-bit Windows and Windows Server, the /3GB switch could be used to give user mode processes up to 3 GB of addressable memory, but this takes away 1 GB of memory from the kernel which could have worse affects on the entire system such as with Pool Paged Memory and Pool Non-Paged Memory. On x64 (64-bit implementation) Windows and Windows Server, 32-bit processes that are large address aware can address up to 4 GB of virtual address space each and 64-bit processes can address up to 8 TB of virtual address space each. It is important that processes have plenty of virtual address space.

    \Process(*)\Virtual Bytes<br /> Warning Range: 1,610,612,736 to 2,147,483,648

    \Process(*)\Virtual Bytes<br /> Warning Range: 1,610,612,736 to 2,147,483,648

    \Process(*)\Virtual Bytes<br /> Warning Range: 1,610,612,736 to 2,147,483,648

    \Process(*)\Virtual Bytes<br /> Warning Range: 1,610,612,736 to 2,147,483,648

    \Process(*)\Virtual Bytes<br /> Warning Range: 1,610,612,736 to 2,147,483,648

    \Process(*)\Virtual Bytes<br /> Warning Range: 1,610,612,736 to 2,147,483,648

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Process(*)\Virtual BytesMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/avagent64,262,14466,359,29667,407,8720804,22166,228,22466,059,70366,036,657
    OKVIEWCS1/avscc114,884,608114,884,608114,884,60800114,884,608114,884,608114,884,608
    OKVIEWCS1/csrss#150,503,68050,503,68050,503,6800050,503,68050,503,68050,503,680
    OKVIEWCS1/csrss#250,835,45650,929,20951,679,232-23,731,200272,86150,835,45650,835,45650,835,456
    OKVIEWCS1/csrss49,827,84049,860,60849,958,912-1,843,20040,52449,852,41649,846,56549,842,964
    OKVIEWCS1/dllhost#147,697,92047,697,92047,697,9200047,697,92047,697,92047,697,920
    OKVIEWCS1/dllhost59,035,64859,035,64859,035,6480059,035,64859,035,64859,035,648
    OKVIEWCS1/dsamain251,039,744251,360,142251,564,03214,745,600262,999251,334,656251,301,888251,281,723
    OKVIEWCS1/dwm56,180,73656,180,73656,180,7360056,180,73656,180,73656,180,736
    OKVIEWCS1/explorer189,968,384191,282,517199,249,920-246,297,6002,215,720190,689,280190,492,672190,371,682
    OKVIEWCS1/FlashUtil32_11_4_402_278_ActiveX99,340,28899,340,28899,340,2880099,340,28899,340,28899,340,288
    OKVIEWCS1/Idle00000000
    OKVIEWCS1/iexplore#1241,725,440241,725,440241,725,44000241,725,440241,725,440241,725,440
    OKVIEWCS1/iexplore#2172,167,168172,463,900173,494,272460,800562,272172,335,104172,171,849172,170,949
    OKVIEWCS1/iexplore#3210,698,240210,698,240210,698,24000210,698,240210,698,240210,698,240
    OKVIEWCS1/iexplore189,034,496190,272,398190,345,2160308,940190,263,296190,251,593190,244,391
    OKVIEWCS1/LogonUI90,263,55290,263,55290,263,5520090,263,55290,263,55290,263,552
    OKVIEWCS1/lsass53,276,67253,364,05353,800,960-14,745,600201,05553,309,44053,276,67253,276,672
    OKVIEWCS1/lsm30,601,21630,979,86831,125,504-14,745,600241,63830,961,66430,938,25830,923,855
    OKVIEWCS1/Microsoft.ActiveDirectory.WebServices576,192,512576,309,020577,241,0880339,089576,192,512576,192,512576,192,512
    OKVIEWCS1/mmc#1641,236,992641,236,992641,236,99200641,236,992641,236,992641,236,992
    OKVIEWCS1/mmc#2204,902,400205,691,108209,117,184-118,540,8001,268,519205,262,848205,239,442205,225,039
    OKVIEWCS1/mmc153,575,424153,575,424153,575,42400153,575,424153,575,424153,575,424
    OKVIEWCS1/msdtc63,352,83263,352,83263,352,8320063,352,83263,352,83263,352,832
    OKVIEWCS1/rdpclip63,074,30463,511,21164,122,8800449,57363,434,75263,336,44863,275,953
    OKVIEWCS1/rundll3284,914,17685,554,97285,962,75229,491,200494,30385,504,00085,438,46485,398,134
    OKVIEWCS1/SecurityGateway38,797,31238,797,31238,797,3120038,797,31238,797,31238,797,312
    OKVIEWCS1/services48,963,58449,400,49149,487,8720201,05549,389,56849,375,52549,366,882
    OKVIEWCS1/smss5,693,4405,693,4405,693,440005,693,4405,693,4405,693,440
    OKVIEWCS1/spoolsv103,141,376103,170,503103,403,520-7,372,80084,772103,141,376103,141,376103,141,376
    OKVIEWCS1/svchost#139,780,35240,508,53041,353,216-29,491,200626,54240,402,94440,267,19140,183,650
    OKVIEWCS1/svchost#1035,287,04035,287,04035,287,0400035,287,04035,287,04035,287,040
    OKVIEWCS1/svchost#1134,508,80034,508,80034,508,8000034,508,80034,508,80034,508,800
    OKVIEWCS1/svchost#252,346,88052,463,38852,871,168-14,745,600224,28752,412,41652,346,88052,346,880
    OKVIEWCS1/svchost#3126,992,384127,254,528128,040,960-29,491,200370,728127,156,224127,104,731127,073,044
    OKVIEWCS1/svchost#448,283,64848,545,79248,807,93614,745,600269,74448,513,02448,470,89448,444,967
    OKVIEWCS1/svchost#572,105,98472,105,98472,105,9840072,105,98472,105,98472,105,984
    OKVIEWCS1/svchost#6156,819,456157,872,583158,412,80014,745,600481,144157,805,056157,718,235157,666,383
    OKVIEWCS1/svchost#761,943,80862,089,44462,468,0960241,63862,042,11261,981,25761,943,808
    OKVIEWCS1/svchost#813,312,00013,312,00013,312,0000013,312,00013,312,00013,312,000
    OKVIEWCS1/svchost#944,367,87244,571,76244,892,160-14,745,600262,99944,531,71244,480,21944,448,532
    OKVIEWCS1/svchost47,734,78448,288,19948,783,360-29,491,200380,29648,226,30448,146,72548,097,753
    OKVIEWCS1/System3,461,1203,461,1203,461,120003,461,1203,461,1203,461,120
    OKVIEWCS1/taskeng34,287,61635,015,79435,336,192-14,745,600365,84934,975,74434,924,25134,892,564
    OKVIEWCS1/taskhost57,524,22457,524,22457,524,2240057,524,22457,524,22457,524,224
    Greater than 75 percent of estimated process virtual address spaceVIEWCS1/ViewTopoSvc2,937,270,2722,940,998,5422,943,561,728-29,491,2002,103,9942,940,678,1442,940,266,2032,940,012,702
    OKVIEWCS1/vmtoolsd#195,162,36895,162,36895,162,3680095,162,36895,162,36895,162,368
    OKVIEWCS1/vmtoolsd106,856,448108,604,075108,953,6000804,221108,560,384108,504,210108,469,642
    OKVIEWCS1/VMwareTray73,052,16075,149,31276,197,888-88,473,6001,525,90275,018,24074,849,71974,746,014
    OKVIEWCS1/vmware-usbarbitrator54,063,10454,063,10454,063,1040054,063,10454,063,10454,063,104
    OKVIEWCS1/wininit50,532,35250,532,35250,532,3520050,532,35250,532,35250,532,352
    OKVIEWCS1/winlogon#132,849,92032,849,92032,849,9200032,849,92032,849,92032,849,920
    OKVIEWCS1/winlogon26,632,19226,632,19226,632,1920026,632,19226,632,19226,632,192
    OKVIEWCS1/WmiApSrv34,504,70435,116,37335,553,280-29,491,200412,04135,061,76034,991,54334,948,332
    OKVIEWCS1/WmiPrvSE#142,414,08043,031,55243,782,144-38,246,400681,82942,924,32542,781,35542,781,355
    OKVIEWCS1/WmiPrvSE36,782,08037,441,53637,892,096-31,219,200429,37637,385,21637,312,80537,268,244
    OKVIEWCS1/ws_ConnectionServer67,309,56867,309,56867,309,5680067,309,56867,309,56867,309,568
    OKVIEWCS1/ws_MessageBusService1,597,943,8081,601,555,5701,604,235,264-117,964,8002,497,5491,601,220,6081,600,789,9431,600,524,918
    Greater than 75 percent of estimated process virtual address spaceVIEWCS1/ws_TomcatService1,614,323,7121,619,042,3041,625,858,048147,456,0003,078,1821,618,190,3361,617,918,8301,617,792,079
    OKVIEWCS1/ws_TunnelService1,114,841,0881,116,297,4441,117,986,816-29,491,2001,531,7781,116,086,2721,115,814,7661,115,647,685
    OKVIEWCS1/wsnm157,360,128159,690,297160,505,85658,982,4001,051,997159,588,352159,457,280159,376,620



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    Time Range
    9/25/2012 11:29:51 AM – 9/25/2012 11:30:06 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,939,367,4242,939,367,4242,939,367,4240
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,620,615,1681,620,615,1681,620,615,1680
    9/25/2012 11:30:06 AM – 9/25/2012 11:30:21 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,939,367,4242,939,367,4242,939,367,4240
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,618,518,0161,618,518,0161,618,518,016-943,718,400
    9/25/2012 11:30:21 AM – 9/25/2012 11:30:36 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,939,367,4242,939,367,4242,939,367,4240
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,618,518,0161,618,518,0161,618,518,016-471,859,200
    9/25/2012 11:30:36 AM – 9/25/2012 11:30:51 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,943,561,7282,943,561,7282,943,561,728629,145,600
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,619,566,5921,619,566,5921,619,566,592-157,286,400
    9/25/2012 11:30:51 AM – 9/25/2012 11:31:06 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,943,561,7282,943,561,7282,943,561,728471,859,200
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,619,566,5921,619,566,5921,619,566,592-117,964,800
    9/25/2012 11:31:06 AM – 9/25/2012 11:31:21 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,943,561,7282,943,561,7282,943,561,728377,487,360
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,619,566,5921,619,566,5921,619,566,592-94,371,840
    9/25/2012 11:31:21 AM – 9/25/2012 11:31:36 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,943,561,7282,943,561,7282,943,561,728314,572,800
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,619,566,5921,619,566,5921,619,566,592-78,643,200
    9/25/2012 11:31:36 AM – 9/25/2012 11:31:51 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,943,561,7282,943,561,7282,943,561,728269,633,829
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,617,469,4401,617,469,4401,617,469,440-202,225,371
    9/25/2012 11:31:51 AM – 9/25/2012 11:32:06 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,941,464,5762,941,464,5762,941,464,576117,964,800
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,617,469,4401,617,469,4401,617,469,440-176,947,200
    9/25/2012 11:32:06 AM – 9/25/2012 11:32:21 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,942,513,1522,942,513,1522,942,513,152157,286,400
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,619,566,5921,619,566,5921,619,566,592-52,428,800
    9/25/2012 11:32:21 AM – 9/25/2012 11:32:36 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,942,513,1522,942,513,1522,942,513,152141,557,760
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,619,566,5921,619,566,5921,619,566,592-47,185,920
    9/25/2012 11:32:36 AM – 9/25/2012 11:32:51 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,941,464,5762,941,464,5762,941,464,57685,792,582
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,619,566,5921,619,566,5921,619,566,592-42,896,291
    9/25/2012 11:32:51 AM – 9/25/2012 11:33:06 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,939,367,4242,939,367,4242,939,367,4240
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,616,420,8641,616,420,8641,616,420,864-157,286,400
    9/25/2012 11:33:06 AM – 9/25/2012 11:33:21 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,939,367,4242,939,367,4242,939,367,4240
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,614,323,7121,614,323,7121,614,323,712-217,781,169
    9/25/2012 11:33:21 AM – 9/25/2012 11:33:36 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,937,270,2722,937,270,2722,937,270,272-67,408,457
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,614,323,7121,614,323,7121,614,323,712-202,225,371
    9/25/2012 11:33:36 AM – 9/25/2012 11:33:51 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,939,367,4242,939,367,4242,939,367,4240
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,616,420,8641,616,420,8641,616,420,864-125,829,120
    9/25/2012 11:33:51 AM – 9/25/2012 11:33:59 AMConditionCounterMinAvgMaxHourly Trend
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ViewTopoSvc)\Virtual Bytes2,938,318,8482,938,318,8482,938,318,848-29,491,200
    Greater than 75 percent of estimated process virtual address space\\VIEWCS1\Process(ws_TomcatService)\Virtual Bytes1,625,858,0481,625,858,0481,625,858,048147,456,000


    Back to the top

    Process IO Data Operations/sec

    Description: The rate at which the process is issuing read and write I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.

    \Process(*)\IO Data Operations/sec<br /> Warning Range: 1,000 to 1,299.999

    \Process(*)\IO Data Operations/sec<br /> Warning Range: 1,000 to 1,299.999

    \Process(*)\IO Data Operations/sec<br /> Warning Range: 1,000 to 1,299.999

    \Process(*)\IO Data Operations/sec<br /> Warning Range: 1,000 to 1,299.999

    \Process(*)\IO Data Operations/sec<br /> Warning Range: 1,000 to 1,299.999

    \Process(*)\IO Data Operations/sec<br /> Warning Range: 1,000 to 1,299.999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Process(*)\IO Data Operations/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/avagent003-841000
    OKVIEWCS1/avscc00000000
    OKVIEWCS1/csrss#100000000
    OKVIEWCS1/csrss#200100000
    OKVIEWCS1/csrss00000000
    OKVIEWCS1/dllhost#1--------
    OKVIEWCS1/dllhost00000000
    OKVIEWCS1/dsamain01201000
    OKVIEWCS1/dwm00000000
    OKVIEWCS1/explorer01101111
    OKVIEWCS1/FlashUtil32_11_4_402_278_ActiveX00000000
    OKVIEWCS1/Idle00000000
    OKVIEWCS1/iexplore#100000000
    OKVIEWCS1/iexplore#200000000
    OKVIEWCS1/iexplore#300000000
    OKVIEWCS1/iexplore12301222
    OKVIEWCS1/LogonUI00000000
    OKVIEWCS1/lsass00201000
    OKVIEWCS1/lsm00000000
    OKVIEWCS1/Microsoft.ActiveDirectory.WebServices00000000
    OKVIEWCS1/mmc#100000000
    OKVIEWCS1/mmc#200000000
    OKVIEWCS1/mmc00000000
    OKVIEWCS1/msdtc00000000
    OKVIEWCS1/rdpclip00000000
    OKVIEWCS1/rundll3200000000
    OKVIEWCS1/SecurityGateway11200111
    OKVIEWCS1/services00000000
    OKVIEWCS1/smss00000000
    OKVIEWCS1/spoolsv00000000
    OKVIEWCS1/svchost#100000000
    OKVIEWCS1/svchost#1000000000
    OKVIEWCS1/svchost#1100000000
    OKVIEWCS1/svchost#200100000
    OKVIEWCS1/svchost#300100000
    OKVIEWCS1/svchost#400000000
    OKVIEWCS1/svchost#500000000
    OKVIEWCS1/svchost#600100000
    OKVIEWCS1/svchost#700000000
    OKVIEWCS1/svchost#800000000
    OKVIEWCS1/svchost#900000000
    OKVIEWCS1/svchost00000000
    OKVIEWCS1/System002-560000
    OKVIEWCS1/taskeng00000000
    OKVIEWCS1/taskhost00000000
    OKVIEWCS1/ViewTopoSvc002560000
    OKVIEWCS1/vmtoolsd#100000000
    OKVIEWCS1/vmtoolsd00000000
    OKVIEWCS1/VMwareTray00000000
    OKVIEWCS1/vmware-usbarbitrator00000000
    OKVIEWCS1/wininit00000000
    OKVIEWCS1/winlogon#100000000
    OKVIEWCS1/winlogon00000000
    OKVIEWCS1/WmiApSrv00000000
    OKVIEWCS1/WmiPrvSE#100000000
    OKVIEWCS1/WmiPrvSE00000000
    OKVIEWCS1/ws_ConnectionServer00000000
    OKVIEWCS1/ws_MessageBusService445280444
    OKVIEWCS1/ws_TomcatService07183386653
    OKVIEWCS1/ws_TunnelService01100111
    OKVIEWCS1/wsnm00100000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Process IO Other Operations/sec

    Description: The rate at which the process is issuing I/O operations that are neither read nor write operations (for example, a control function). This counter counts all I/O activity generated by the process to include file, network and device I/Os.

    \Process(*)\IO Other Operations/sec<br /> Warning Range: 1,000 to 1,299.999

    \Process(*)\IO Other Operations/sec<br /> Warning Range: 1,000 to 1,299.999

    \Process(*)\IO Other Operations/sec<br /> Warning Range: 1,000 to 1,299.999

    \Process(*)\IO Other Operations/sec<br /> Warning Range: 1,000 to 1,299.999

    \Process(*)\IO Other Operations/sec<br /> Warning Range: 1,000 to 1,299.999

    \Process(*)\IO Other Operations/sec<br /> Warning Range: 1,000 to 1,299.999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Process(*)\IO Other Operations/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/avagent0117-4784000
    OKVIEWCS1/avscc00000000
    OKVIEWCS1/csrss#100000000
    OKVIEWCS1/csrss#200000000
    OKVIEWCS1/csrss003-841000
    OKVIEWCS1/dllhost#1--------
    OKVIEWCS1/dllhost00000000
    OKVIEWCS1/dsamain0211563111
    OKVIEWCS1/dwm00000000
    OKVIEWCS1/explorer011-280111
    OKVIEWCS1/FlashUtil32_11_4_402_278_ActiveX00000000
    OKVIEWCS1/Idle00000000
    OKVIEWCS1/iexplore#100000000
    OKVIEWCS1/iexplore#2071004666
    OKVIEWCS1/iexplore#300000000
    OKVIEWCS1/iexplore03402332
    OKVIEWCS1/LogonUI00000000
    OKVIEWCS1/lsass01402000
    OKVIEWCS1/lsm00000000
    OKVIEWCS1/Microsoft.ActiveDirectory.WebServices00000000
    OKVIEWCS1/mmc#100000000
    OKVIEWCS1/mmc#200000000
    OKVIEWCS1/mmc00000000
    OKVIEWCS1/msdtc00000000
    OKVIEWCS1/rdpclip00000000
    OKVIEWCS1/rundll3222200222
    OKVIEWCS1/SecurityGateway66600666
    OKVIEWCS1/services00000000
    OKVIEWCS1/smss00000000
    OKVIEWCS1/spoolsv00000000
    OKVIEWCS1/svchost#1001280000
    OKVIEWCS1/svchost#1000000000
    OKVIEWCS1/svchost#1100000000
    OKVIEWCS1/svchost#200100000
    OKVIEWCS1/svchost#300601000
    OKVIEWCS1/svchost#400201000
    OKVIEWCS1/svchost#500000000
    OKVIEWCS1/svchost#611200111
    OKVIEWCS1/svchost#700802000
    OKVIEWCS1/svchost#800000000
    OKVIEWCS1/svchost#900000000
    OKVIEWCS1/svchost00501000
    OKVIEWCS1/System001-280000
    OKVIEWCS1/taskeng00000000
    OKVIEWCS1/taskhost00000000
    OKVIEWCS1/ViewTopoSvc005561000
    OKVIEWCS1/vmtoolsd#133300333
    OKVIEWCS1/vmtoolsd31632015141310
    OKVIEWCS1/VMwareTray33300333
    OKVIEWCS1/vmware-usbarbitrator11100111
    OKVIEWCS1/wininit00000000
    OKVIEWCS1/winlogon#100000000
    OKVIEWCS1/winlogon00000000
    OKVIEWCS1/WmiApSrv22200222
    OKVIEWCS1/WmiPrvSE#100000000
    OKVIEWCS1/WmiPrvSE00000000
    OKVIEWCS1/ws_ConnectionServer00000000
    OKVIEWCS1/ws_MessageBusService1518232252171716
    OKVIEWCS1/ws_TomcatService1145971,23829393529
    OKVIEWCS1/ws_TunnelService91012011099
    OKVIEWCS1/wsnm0335569100



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Process ID Process

    Description: ID Process is the unique identifier of this process. ID Process numbers are reused, so they only identify a process for the lifetime of that process.

    \Process(*)\ID Process

    \Process(*)\ID Process

    \Process(*)\ID Process

    \Process(*)\ID Process

    \Process(*)\ID Process

    \Process(*)\ID Process

    \Process(*)\ID Process

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Process(*)\ID ProcessMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/_Total00000000
    No ThresholdsVIEWCS1/avagent1,2601,2601,260001,2601,2601,260
    No ThresholdsVIEWCS1/avscc4,8564,8564,856004,8564,8564,856
    No ThresholdsVIEWCS1/csrss#144844844800448448448
    No ThresholdsVIEWCS1/csrss#24,5844,5844,584004,5844,5844,584
    No ThresholdsVIEWCS1/csrss34434434400344344344
    No ThresholdsVIEWCS1/dllhost#16,1046,1046,104006,1046,1046,104
    No ThresholdsVIEWCS1/dllhost2,2802,2802,280002,2802,2802,280
    No ThresholdsVIEWCS1/dsamain1,0761,0761,076001,0761,0761,076
    No ThresholdsVIEWCS1/dwm4,9204,9204,920004,9204,9204,920
    No ThresholdsVIEWCS1/explorer4,9924,9924,992004,9924,9924,992
    No ThresholdsVIEWCS1/FlashUtil32_11_4_402_278_ActiveX3,3643,3643,364003,3643,3643,364
    No ThresholdsVIEWCS1/Idle00000000
    No ThresholdsVIEWCS1/iexplore#15,4165,4165,416005,4165,4165,416
    No ThresholdsVIEWCS1/iexplore#25,1765,1765,176005,1765,1765,176
    No ThresholdsVIEWCS1/iexplore#35,0605,0605,060005,0605,0605,060
    No ThresholdsVIEWCS1/iexplore5,2845,2845,284005,2845,2845,284
    No ThresholdsVIEWCS1/LogonUI82482482400824824824
    No ThresholdsVIEWCS1/lsass55655655600556556556
    No ThresholdsVIEWCS1/lsm56456456400564564564
    No ThresholdsVIEWCS1/Microsoft.ActiveDirectory.WebServices1,1081,1081,108001,1081,1081,108
    No ThresholdsVIEWCS1/mmc#16,1286,1286,128006,1286,1286,128
    No ThresholdsVIEWCS1/mmc#26,0446,0446,044006,0446,0446,044
    No ThresholdsVIEWCS1/mmc76876876800768768768
    No ThresholdsVIEWCS1/msdtc2,3602,3602,360002,3602,3602,360
    No ThresholdsVIEWCS1/rdpclip4,8604,8604,860004,8604,8604,860
    No ThresholdsVIEWCS1/rundll325,6285,6285,628005,6285,6285,628
    No ThresholdsVIEWCS1/SecurityGateway3,0483,0483,048003,0483,0483,048
    No ThresholdsVIEWCS1/services54054054000540540540
    No ThresholdsVIEWCS1/smss24024024000240240240
    No ThresholdsVIEWCS1/spoolsv1,0361,0361,036001,0361,0361,036
    No ThresholdsVIEWCS1/svchost#174074074000740740740
    No ThresholdsVIEWCS1/svchost#102,0842,0842,084002,0842,0842,084
    No ThresholdsVIEWCS1/svchost#115,8805,8805,880005,8805,8805,880
    No ThresholdsVIEWCS1/svchost#283283283200832832832
    No ThresholdsVIEWCS1/svchost#388088088000880880880
    No ThresholdsVIEWCS1/svchost#493693693600936936936
    No ThresholdsVIEWCS1/svchost#597297297200972972972
    No ThresholdsVIEWCS1/svchost#61,0161,0161,016001,0161,0161,016
    No ThresholdsVIEWCS1/svchost#740040040000400400400
    No ThresholdsVIEWCS1/svchost#81,3161,3161,316001,3161,3161,316
    No ThresholdsVIEWCS1/svchost#91,1481,1481,148001,1481,1481,148
    No ThresholdsVIEWCS1/svchost66066066000660660660
    No ThresholdsVIEWCS1/System44400444
    No ThresholdsVIEWCS1/taskeng5,7125,7125,712005,7125,7125,712
    No ThresholdsVIEWCS1/taskhost4,7764,7764,776004,7764,7764,776
    No ThresholdsVIEWCS1/ViewTopoSvc1,3721,3721,372001,3721,3721,372
    No ThresholdsVIEWCS1/vmtoolsd#14,5884,5884,588004,5884,5884,588
    No ThresholdsVIEWCS1/vmtoolsd1,7201,7201,720001,7201,7201,720
    No ThresholdsVIEWCS1/VMwareTray3,6523,6523,652003,6523,6523,652
    No ThresholdsVIEWCS1/vmware-usbarbitrator1,4921,4921,492001,4921,4921,492
    No ThresholdsVIEWCS1/wininit44044044000440440440
    No ThresholdsVIEWCS1/winlogon#14,6084,6084,608004,6084,6084,608
    No ThresholdsVIEWCS1/winlogon49649649600496496496
    No ThresholdsVIEWCS1/WmiApSrv4,8804,8804,880004,8804,8804,880
    No ThresholdsVIEWCS1/WmiPrvSE#16,0366,0366,036006,0366,0366,036
    No ThresholdsVIEWCS1/WmiPrvSE1,7881,7881,788001,7881,7881,788
    No ThresholdsVIEWCS1/ws_ConnectionServer1,8081,8081,808001,8081,8081,808
    No ThresholdsVIEWCS1/ws_MessageBusService2,8522,8522,852002,8522,8522,852
    No ThresholdsVIEWCS1/ws_TomcatService3,0563,0563,056003,0563,0563,056
    No ThresholdsVIEWCS1/ws_TunnelService3,0403,0403,040003,0403,0403,040
    No ThresholdsVIEWCS1/wsnm1,3321,3321,332001,3321,3321,332



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Process IO Read Operations/sec

    Description: The rate at which the process is issuing read I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.

    \Process(*)\IO Read Operations/sec

    \Process(*)\IO Read Operations/sec

    \Process(*)\IO Read Operations/sec

    \Process(*)\IO Read Operations/sec

    \Process(*)\IO Read Operations/sec

    \Process(*)\IO Read Operations/sec

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Process(*)\IO Read Operations/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/avagent001-280000
    No ThresholdsVIEWCS1/avscc00000000
    No ThresholdsVIEWCS1/csrss#100000000
    No ThresholdsVIEWCS1/csrss#200100000
    No ThresholdsVIEWCS1/csrss00000000
    No ThresholdsVIEWCS1/dllhost#1--------
    No ThresholdsVIEWCS1/dllhost00000000
    No ThresholdsVIEWCS1/dsamain00000000
    No ThresholdsVIEWCS1/dwm00000000
    No ThresholdsVIEWCS1/explorer01101111
    No ThresholdsVIEWCS1/FlashUtil32_11_4_402_278_ActiveX00000000
    No ThresholdsVIEWCS1/Idle00000000
    No ThresholdsVIEWCS1/iexplore#100000000
    No ThresholdsVIEWCS1/iexplore#200000000
    No ThresholdsVIEWCS1/iexplore#300000000
    No ThresholdsVIEWCS1/iexplore01201111
    No ThresholdsVIEWCS1/LogonUI00000000
    No ThresholdsVIEWCS1/lsass00100000
    No ThresholdsVIEWCS1/lsm00000000
    No ThresholdsVIEWCS1/Microsoft.ActiveDirectory.WebServices00000000
    No ThresholdsVIEWCS1/mmc#100000000
    No ThresholdsVIEWCS1/mmc#200000000
    No ThresholdsVIEWCS1/mmc00000000
    No ThresholdsVIEWCS1/msdtc00000000
    No ThresholdsVIEWCS1/rdpclip00000000
    No ThresholdsVIEWCS1/rundll3200000000
    No ThresholdsVIEWCS1/SecurityGateway00000000
    No ThresholdsVIEWCS1/services00000000
    No ThresholdsVIEWCS1/smss00000000
    No ThresholdsVIEWCS1/spoolsv00000000
    No ThresholdsVIEWCS1/svchost#100000000
    No ThresholdsVIEWCS1/svchost#1000000000
    No ThresholdsVIEWCS1/svchost#1100000000
    No ThresholdsVIEWCS1/svchost#200000000
    No ThresholdsVIEWCS1/svchost#300000000
    No ThresholdsVIEWCS1/svchost#400000000
    No ThresholdsVIEWCS1/svchost#500000000
    No ThresholdsVIEWCS1/svchost#600000000
    No ThresholdsVIEWCS1/svchost#700000000
    No ThresholdsVIEWCS1/svchost#800000000
    No ThresholdsVIEWCS1/svchost#900000000
    No ThresholdsVIEWCS1/svchost00000000
    No ThresholdsVIEWCS1/System00000000
    No ThresholdsVIEWCS1/taskeng00000000
    No ThresholdsVIEWCS1/taskhost00000000
    No ThresholdsVIEWCS1/ViewTopoSvc00000000
    No ThresholdsVIEWCS1/vmtoolsd#100000000
    No ThresholdsVIEWCS1/vmtoolsd00000000
    No ThresholdsVIEWCS1/VMwareTray00000000
    No ThresholdsVIEWCS1/vmware-usbarbitrator00000000
    No ThresholdsVIEWCS1/wininit00000000
    No ThresholdsVIEWCS1/winlogon#100000000
    No ThresholdsVIEWCS1/winlogon00000000
    No ThresholdsVIEWCS1/WmiApSrv00000000
    No ThresholdsVIEWCS1/WmiPrvSE#100000000
    No ThresholdsVIEWCS1/WmiPrvSE00000000
    No ThresholdsVIEWCS1/ws_ConnectionServer00000000
    No ThresholdsVIEWCS1/ws_MessageBusService00000000
    No ThresholdsVIEWCS1/ws_TomcatService00100000
    No ThresholdsVIEWCS1/ws_TunnelService00000000
    No ThresholdsVIEWCS1/wsnm00000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Process IO Write Operations/sec

    Description: The rate at which the process is issuing write I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.

    \Process(*)\IO Write Operations/sec

    \Process(*)\IO Write Operations/sec

    \Process(*)\IO Write Operations/sec

    \Process(*)\IO Write Operations/sec

    \Process(*)\IO Write Operations/sec

    \Process(*)\IO Write Operations/sec

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Process(*)\IO Write Operations/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/avagent002-560000
    No ThresholdsVIEWCS1/avscc00000000
    No ThresholdsVIEWCS1/csrss#100000000
    No ThresholdsVIEWCS1/csrss#200000000
    No ThresholdsVIEWCS1/csrss00000000
    No ThresholdsVIEWCS1/dllhost#1--------
    No ThresholdsVIEWCS1/dllhost00000000
    No ThresholdsVIEWCS1/dsamain00201000
    No ThresholdsVIEWCS1/dwm00000000
    No ThresholdsVIEWCS1/explorer00000000
    No ThresholdsVIEWCS1/FlashUtil32_11_4_402_278_ActiveX00000000
    No ThresholdsVIEWCS1/Idle00000000
    No ThresholdsVIEWCS1/iexplore#100000000
    No ThresholdsVIEWCS1/iexplore#200000000
    No ThresholdsVIEWCS1/iexplore#300000000
    No ThresholdsVIEWCS1/iexplore01100111
    No ThresholdsVIEWCS1/LogonUI00000000
    No ThresholdsVIEWCS1/lsass00100000
    No ThresholdsVIEWCS1/lsm00000000
    No ThresholdsVIEWCS1/Microsoft.ActiveDirectory.WebServices00000000
    No ThresholdsVIEWCS1/mmc#100000000
    No ThresholdsVIEWCS1/mmc#200000000
    No ThresholdsVIEWCS1/mmc00000000
    No ThresholdsVIEWCS1/msdtc00000000
    No ThresholdsVIEWCS1/rdpclip00000000
    No ThresholdsVIEWCS1/rundll3200000000
    No ThresholdsVIEWCS1/SecurityGateway11200111
    No ThresholdsVIEWCS1/services00000000
    No ThresholdsVIEWCS1/smss00000000
    No ThresholdsVIEWCS1/spoolsv00000000
    No ThresholdsVIEWCS1/svchost#100000000
    No ThresholdsVIEWCS1/svchost#1000000000
    No ThresholdsVIEWCS1/svchost#1100000000
    No ThresholdsVIEWCS1/svchost#200100000
    No ThresholdsVIEWCS1/svchost#300100000
    No ThresholdsVIEWCS1/svchost#400000000
    No ThresholdsVIEWCS1/svchost#500000000
    No ThresholdsVIEWCS1/svchost#600000000
    No ThresholdsVIEWCS1/svchost#700000000
    No ThresholdsVIEWCS1/svchost#800000000
    No ThresholdsVIEWCS1/svchost#900000000
    No ThresholdsVIEWCS1/svchost00000000
    No ThresholdsVIEWCS1/System002-560000
    No ThresholdsVIEWCS1/taskeng00000000
    No ThresholdsVIEWCS1/taskhost00000000
    No ThresholdsVIEWCS1/ViewTopoSvc002560000
    No ThresholdsVIEWCS1/vmtoolsd#100000000
    No ThresholdsVIEWCS1/vmtoolsd00000000
    No ThresholdsVIEWCS1/VMwareTray00000000
    No ThresholdsVIEWCS1/vmware-usbarbitrator00000000
    No ThresholdsVIEWCS1/wininit00000000
    No ThresholdsVIEWCS1/winlogon#100000000
    No ThresholdsVIEWCS1/winlogon00000000
    No ThresholdsVIEWCS1/WmiApSrv00000000
    No ThresholdsVIEWCS1/WmiPrvSE#100000000
    No ThresholdsVIEWCS1/WmiPrvSE00000000
    No ThresholdsVIEWCS1/ws_ConnectionServer00000000
    No ThresholdsVIEWCS1/ws_MessageBusService445280444
    No ThresholdsVIEWCS1/ws_TomcatService07183386553
    No ThresholdsVIEWCS1/ws_TunnelService01100111
    No ThresholdsVIEWCS1/wsnm00100000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Process % Privileged Time

    Description: % Privileged Time is the percentage of elapsed time that the process threads spent executing code in privileged mode. When a Windows system service is called, the service will often run in privileged mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.

    \Process(*)\% Privileged Time

    \Process(*)\% Privileged Time

    \Process(*)\% Privileged Time

    \Process(*)\% Privileged Time

    \Process(*)\% Privileged Time

    \Process(*)\% Privileged Time

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Process(*)\% Privileged TimeMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/avagent00000000
    No ThresholdsVIEWCS1/avscc00000000
    No ThresholdsVIEWCS1/csrss#100000000
    No ThresholdsVIEWCS1/csrss#200000000
    No ThresholdsVIEWCS1/csrss00000000
    No ThresholdsVIEWCS1/dllhost#1--------
    No ThresholdsVIEWCS1/dllhost00000000
    No ThresholdsVIEWCS1/dsamain00000000
    No ThresholdsVIEWCS1/dwm00000000
    No ThresholdsVIEWCS1/explorer00000000
    No ThresholdsVIEWCS1/FlashUtil32_11_4_402_278_ActiveX00000000
    No ThresholdsVIEWCS1/iexplore#100000000
    No ThresholdsVIEWCS1/iexplore#200000000
    No ThresholdsVIEWCS1/iexplore#300000000
    No ThresholdsVIEWCS1/iexplore00000000
    No ThresholdsVIEWCS1/LogonUI00000000
    No ThresholdsVIEWCS1/lsass00000000
    No ThresholdsVIEWCS1/lsm00000000
    No ThresholdsVIEWCS1/Microsoft.ActiveDirectory.WebServices00000000
    No ThresholdsVIEWCS1/mmc#100000000
    No ThresholdsVIEWCS1/mmc#2002561000
    No ThresholdsVIEWCS1/mmc00000000
    No ThresholdsVIEWCS1/msdtc00000000
    No ThresholdsVIEWCS1/rdpclip00000000
    No ThresholdsVIEWCS1/rundll3200000000
    No ThresholdsVIEWCS1/SecurityGateway00000000
    No ThresholdsVIEWCS1/services00000000
    No ThresholdsVIEWCS1/smss00000000
    No ThresholdsVIEWCS1/spoolsv00000000
    No ThresholdsVIEWCS1/svchost#100000000
    No ThresholdsVIEWCS1/svchost#1000000000
    No ThresholdsVIEWCS1/svchost#1100000000
    No ThresholdsVIEWCS1/svchost#200000000
    No ThresholdsVIEWCS1/svchost#300000000
    No ThresholdsVIEWCS1/svchost#400000000
    No ThresholdsVIEWCS1/svchost#500000000
    No ThresholdsVIEWCS1/svchost#600000000
    No ThresholdsVIEWCS1/svchost#700000000
    No ThresholdsVIEWCS1/svchost#800000000
    No ThresholdsVIEWCS1/svchost#900000000
    No ThresholdsVIEWCS1/svchost00000000
    No ThresholdsVIEWCS1/System00000000
    No ThresholdsVIEWCS1/taskeng00000000
    No ThresholdsVIEWCS1/taskhost00000000
    No ThresholdsVIEWCS1/ViewTopoSvc00000000
    No ThresholdsVIEWCS1/vmtoolsd#100000000
    No ThresholdsVIEWCS1/vmtoolsd00000000
    No ThresholdsVIEWCS1/VMwareTray00000000
    No ThresholdsVIEWCS1/vmware-usbarbitrator00000000
    No ThresholdsVIEWCS1/wininit00000000
    No ThresholdsVIEWCS1/winlogon#100000000
    No ThresholdsVIEWCS1/winlogon00000000
    No ThresholdsVIEWCS1/WmiApSrv00000000
    No ThresholdsVIEWCS1/WmiPrvSE#100000000
    No ThresholdsVIEWCS1/WmiPrvSE00000000
    No ThresholdsVIEWCS1/ws_ConnectionServer00000000
    No ThresholdsVIEWCS1/ws_MessageBusService00000000
    No ThresholdsVIEWCS1/ws_TomcatService00100000
    No ThresholdsVIEWCS1/ws_TunnelService00000000
    No ThresholdsVIEWCS1/wsnm00000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Processor


    Processor % Processor Time

    Description: % Processor Time is the percentage of elapsed time that the processor spends to execute a non-Idle thread. It is calculated by measuring the duration of the idle thread is active in the sample interval, and subtracting that time from interval duration. This counter is the primary indicator of processor activity, and displays the average percentage of busy time observed during the sample interval. % Processor Time is the sum of % User Time and % Privileged Time unless there is hardware involvement in the form of interupts and/or DPCs.

    This analysis creates a Warning alert for utilization greater than 50% on any processor and creates a critical alert for utilization greater than 80%.

    If average processor utilization is high based on the thresholds witin this analysis, then check if it is high user mode CPU or high privileged mode. If high privileged mode CPU is suspected, then see the Privileged Mode CPU Analysis. If a user-mode processor bottleneck is suspected, then consider using a process profiler to analyze the functions causing the high CPU consumption. See How To: Identify Functions causing a High User-mode CPU Bottleneck for Server Applications in a Production Environment article in the references section for more information.

    References:

    \Processor(*)\% Processor Time<br /> Warning Range: 50 to 80<br
/> Critical Range: 80 to 99.999

    \Processor(*)\% Processor Time<br /> Warning Range: 50 to 80<br
/> Critical Range: 80 to 99.999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Processor(*)\% Processor TimeMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/_Total12601111
    OKVIEWCS1/0126-281221
    OKVIEWCS1/1015281100



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Processor % Privileged Time

    Description: This counter indicates the percentage of time a thread runs in privileged mode also known as kernel mode. When your application calls operating system functions (for example to perform file or network I/O or to allocate memory), these operating system functions are executed in privileged mode.

    High privileged mode CPU indicates that computer is spending too much time in system I/O versus real (user mode) work. % Privileged Time is the percentage of elapsed time that the process threads spent executing code in privileged mode. When a Windows system service in called, the service will often run in privileged mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.

    This analysis throws a warning alert if privileged mode CPU is consuming more than 20% of total CPU and a critical alert if consuming More than 30% of total CPU.

    Next steps
    The CPU consumption might be caused by another busy resource such as network, memory, or disk I/O. High privileged mode CPU can also by caused by high amounts of Context Switches/second. See the High Context Switches/second analysis. The KernRate (KrView) tool can be used to profile the kernel to see what component is consuming the most kernel resources. To see more information about how KernRate can be used to analyze high priviledge mode CPU problems, see Mark Russinovich’s blog entry in the references section below.

    References:

    \Processor(*)\% Privileged Time<br /> Warning Range: 20 to 30<br
/> Critical Range: 30 to 99.999

    \Processor(*)\% Privileged Time<br /> Warning Range: 20 to 30<br
/> Critical Range: 30 to 99.999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Processor(*)\% Privileged TimeMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/_Total00100000
    OKVIEWCS1/001201000
    OKVIEWCS1/1001280000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Processor % Interrupt Time

    Description: % Interrupt Time is the time the processor spends receiving and servicing hardware interrupts during sample intervals. This value is an indirect indicator of the activity of devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication lines, network interface cards and other peripheral devices. These devices normally interrupt the processor when they have completed a task or require attention. Normal thread execution is suspended during interrupts. Most system clocks interrupt the processor every 10 milliseconds, creating a background of interrupt activity. A dramatic increase in this counter indicates potential hardware problems.

    This analysis checks for % Interrupt Time greater than 30%. If this occurs, then consider updating devices drivers for hardware that correlates to this alert.

    References:
    Measuring .NET Application Performance
    http://msdn2.microsoft.com/en-us/library/ms998579.aspx

    \Processor(*)\% Interrupt Time<br /> Warning Range: 30 to 50<br
/> Critical Range: 50 to 99.999

    \Processor(*)\% Interrupt Time<br /> Warning Range: 30 to 50<br
/> Critical Range: 50 to 99.999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Processor(*)\% Interrupt TimeMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/_Total00000000
    OKVIEWCS1/000000000
    OKVIEWCS1/100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Processor % DPC Time

    Description: % DPC Time is the percentage of time that the processor spent receiving and servicing deferred procedure calls (DPCs) during the sample interval. DPCs are interrupts that run at a lower priority than standard interrupts. % DPC Time is a component of % Privileged Time because DPCs are executed in privileged mode. They are counted separately and are not a component of the interrupt counters. This counter displays the average busy time as a percentage of the sample time.

    \Processor(*)\% DPC Time<br /> Warning Range: 20 to 99.999

    \Processor(*)\% DPC Time<br /> Warning Range: 20 to 99.999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Processor(*)\% DPC TimeMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS1/_Total00000000
    OKVIEWCS1/000000000
    OKVIEWCS1/100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Processor % User Time

    Description: % User Time is the percentage of elapsed time the processor spends in the user mode. User mode is a restricted processing mode designed for applications, environment subsystems, and integral subsystems. The alternative, privileged mode, is designed for operating system components and allows direct access to hardware and all memory. The operating system switches application threads to privileged mode to access operating system services. This counter displays the average busy time as a percentage of the sample time.

    This analysis provides statistics only. Threads running on a processor will be in either user mode measured using % User Time or in priviledge/kernel mode measured using % Privileged Time. High % User Time indicates a high amount of application code is being executed. This is desirable versus too much time in privileged mode. See the Processor % Privileged Time analysis for more information.

    \Processor(*)\% User Time

    \Processor(*)\% User Time

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Processor(*)\% User TimeMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/_Total01401111
    No ThresholdsVIEWCS1/0124-281111
    No ThresholdsVIEWCS1/101501000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Processor DPC Rate

    Description: DPC Rate is the rate at which deferred procedure calls (DPCs) were added to the processors DPC queues between the timer ticks of the processor clock. DPCs are interrupts that run at alower priority than standard interrupts. Each processor has its own DPC queue. This counter measures the rate that DPCs were added to the queue, not the number of DPCs in the queue. This counter displays the last observed value only; it is not an average.

    \Processor(*)\DPC Rate<br /> Warning Range: 10 to 20<br
/> Critical Range: 20 to 29.999

    \Processor(*)\DPC Rate<br /> Warning Range: 10 to 20<br
/> Critical Range: 20 to 29.999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Processor(*)\DPC RateMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/_Total027-562100
    No ThresholdsVIEWCS1/0016842000
    No ThresholdsVIEWCS1/1015-1411000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Processor Information


    Processor Information Parking Status

    Description: Parking Status represents whether a processor is parked or not.

    \Processor Information(*)\Parking Status

    \Processor Information(*)\Parking Status

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Processor Information(*)\Parking StatusMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/_Total00000000
    No ThresholdsVIEWCS1/0,_Total00000000
    No ThresholdsVIEWCS1/0,000000000
    No ThresholdsVIEWCS1/0,101100111



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Processor Information % of Maximum Frequency

    Description: % of Maximum Frequency is the percentage of the current processor’s maximum frequency.

    \Processor Information(*)\% of Maximum Frequency

    \Processor Information(*)\% of Maximum Frequency

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Processor Information(*)\% of Maximum FrequencyMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/_Total00000000
    No ThresholdsVIEWCS1/0,_Total00000000
    No ThresholdsVIEWCS1/0,010010010000100100100
    No ThresholdsVIEWCS1/0,110010010000100100100



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Server


    Server Pool Nonpaged Failures

    Description: The number of times allocations from nonpaged pool have failed. Indicates that the computer’s physical memory is too small.

    \Server\Pool Nonpaged Failures

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Server\Pool Nonpaged FailuresMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Server Pool Paged Failures

    Description: The number of times allocations from paged pool have failed. Indicates that the computer’s physical memory or paging file are too small.

    \Server\Pool Paged Failures

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\Server\Pool Paged FailuresMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    System


    System Processor Queue Length

    Description: Processor Queue Length (PQL) is the number of threads in the processor queue. Unlike the disk counters, this counter shows ready threads only, not threads that are running. There is a single queue for processor time even on computers with multiple processors. Therefore, if a computer has multiple processors, you need to divide this value by the number of processors servicing the workload. A sustained processor queue of less than 10 threads per processor is normally acceptable, dependent of the workload.

    This analysis determines if the average processor queue length exceeds the number of processors. If so, then this could indicate a processor bottleneck. Use this analysis in correlation with Privileged Mode CPU Analysis and Excessive Processor Use by Process analysis.

    Note: Due to the way in which this counter is collected, ignore this counter and alerts for it when collected from a virtual computer.

    If there are more tasks ready to run than there are processors, threads queue up. The processor queue is the collection of threads that are ready but not able to be executed by the processor because another active thread is currently executing. A sustained or recurring queue of more threads than number of processors is a good indication of a processor bottleneck.

    You can use this counter in conjunction with the \Processor\% Processor Time counter to determine if your application can benefit from more CPUs.

    Reference:

    \System\Processor Queue Length<br /> Warning Range: 7.999 to 39.999<br
/> Critical Range: 39.999 to 79.999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\System\Processor Queue LengthMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    System High Context Switching

    Description:
    Context Switches/sec is the combined rate at which all processors on the computer are switched from one thread to another. Context switches occur when a running thread voluntarily relinquishes the processor, is preempted by a higher priority ready thread, or switches between user-mode and privileged (kernel) mode to use an Executive or subsystem service. It is the sum of Thread\\Context Switches/sec for all threads running on all processors in the computer and is measured in numbers of switches. There are context switch counters on the System and Thread objects. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.

    High context switching is only a problem if overall CPU is high as well. This analysis checks for high CPU, high privileged mode CPU, and high system context switches per sec.

    Threshold: As a general rule, context switching rates of greater than 5,000 per second per processor are considered a warning. If context switching rates exceed 10,000 per second per processor, then there is a constraint.

    Significance: Context switching happens when a higher priority thread preempts a lower priority thread that is currently running or when a high priority thread blocks. High levels of context switching can occur when many threads share the same priority level. This often indicates that there are too many threads competing for the processors on the system. If you do not see much processor utilization and you see very low levels of context switching, it could indicate that threads are blocked.

    Reference:
    Measuring .NET Application Performance
    http://msdn2.microsoft.com/en-us/library/ms998579.aspx

    \System\Context Switches/sec<br /> Warning Range: 9,999.999 to 19,999.998<br
/> Critical Range: 19,999.999 to 39,999.999

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\System\Context Switches/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    OKVIEWCS11,2511,4291,7493,8531331,3911,3781,362



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    System System Calls/sec

    Description: System Calls/sec is the combined rate of calls to operating system service routines by all processes running on the computer. These routines perform all of the basic scheduling and synchronization of activities on the computer, and provide access to non-graphic devices, memory management, and name space management. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.

    \System\System Calls/sec

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\System\System Calls/secMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS13,93410,05483,6752,202,01919,0045,2555,1384,964



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    TCPv4


    TCPv4 Connection Failures

    Description: Connection Failures is the number of times TCP connections have made a direct transition to the CLOSED state from the SYN-SENT state or the SYN-RCVD state, plus the number of times TCP connections have made a direct transition to the LISTEN state from the SYN-RCVD state.

    \TCPv4\Connection Failures

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\TCPv4\Connection FailuresMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    More than 10 TCP connection failures per hourVIEWCS1630632633841632631631



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    Time Range
    9/25/2012 11:30:21 AM – 9/25/2012 11:30:36 AMConditionCounterMinAvgMaxHourly Trend
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures631631631225
    9/25/2012 11:30:36 AM – 9/25/2012 11:30:51 AMConditionCounterMinAvgMaxHourly Trend
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures631631631150
    9/25/2012 11:30:51 AM – 9/25/2012 11:31:06 AMConditionCounterMinAvgMaxHourly Trend
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures631631631112
    9/25/2012 11:31:06 AM – 9/25/2012 11:31:21 AMConditionCounterMinAvgMaxHourly Trend
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures63163163190
    9/25/2012 11:31:21 AM – 9/25/2012 11:31:36 AMConditionCounterMinAvgMaxHourly Trend
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures63163163175
    9/25/2012 11:31:36 AM – 9/25/2012 11:31:51 AMConditionCounterMinAvgMaxHourly Trend
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures63163163164
    9/25/2012 11:31:51 AM – 9/25/2012 11:32:06 AMConditionCounterMinAvgMaxHourly Trend
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures632632632112
    9/25/2012 11:32:06 AM – 9/25/2012 11:32:21 AMConditionCounterMinAvgMaxHourly Trend
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures632632632100
    9/25/2012 11:32:21 AM – 9/25/2012 11:32:36 AMConditionCounterMinAvgMaxHourly Trend
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures63263263290
    9/25/2012 11:32:36 AM – 9/25/2012 11:32:51 AMConditionCounterMinAvgMaxHourly Trend
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures63263263282
    9/25/2012 11:32:51 AM – 9/25/2012 11:33:06 AMConditionCounterMinAvgMaxHourly Trend
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures63263263275
    9/25/2012 11:33:06 AM – 9/25/2012 11:33:21 AMConditionCounterMinAvgMaxHourly Trend
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures633633633104
    9/25/2012 11:33:21 AM – 9/25/2012 11:33:36 AMConditionCounterMinAvgMaxHourly Trend
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures63363363396
    9/25/2012 11:33:36 AM – 9/25/2012 11:33:51 AMConditionCounterMinAvgMaxHourly Trend
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures63363363390
    9/25/2012 11:33:51 AM – 9/25/2012 11:33:59 AMConditionCounterMinAvgMaxHourly Trend
    More than 10 TCP connection failures per hour\\VIEWCS1\TCPv4\Connection Failures63363363384


    Back to the top

    VM Memory


    Memory Active in MB

    Description: Amount of memory that is actively used by the virtual machine, as estimated by VMkernel based on recently touched memory pages.
    A large delta between memory active and vRAM allocated could indicate over-sized VM’s. Consider reducing memory allocation to VM’s and monitor.
    See http://www.vmware.com/files/pdf/perf-vsphere-memory_management.pdf for information on how VMware manages memory!!!

    \VM Memory\Memory Active in MB

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VM Memory\Memory Active in MBMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS16147578600107744728718



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Ballooned in MB

    Description: The amount of memory that has been reclaimed from this virtual machine via the VMware Memory Balloon mechanism.
    When VMware tools are installed on a virtual machine they provide device drivers into the host virtualization layer, from within the guest operating system. Part of this package that is installed is the balloon driver or “vmmemctl” which can be observed inside the guest. The balloon driver communicates to the hypervisor to reclaim memory inside the guest when it is no longer valuable to the operating system. If the Physical ESX server begins to run low on memory it will grow the balloon driver to reclaim memory from the guest. This process reduces the chance that the physical ESX host will begin to swap, which you will cause performance degradation.
    Ballooning indicates that your ESXi hosts have some memory contention. In general, a little bit of ballooning is not bad. Ballooning at a low level allows ESXi to reclaim inactive memory pages from guest VM’s. However, if there are not enough inactive pages to claim, active pages may be reclaimed. This can hurt performance of the guest VM.
    Resolution

    • Verify Distributed Resource Scheduler is enabled on your cluster. DRS can redistribute VM’s from over-subscribed hosts to less busy hosts.
    • Install more memory in physical hosts.
    • Change the power policy of VMware View pools to suspend or power-off to conserve host resources. Note: this is at the expense of increased logon times for users.
    • Add additional hosts to cluster. Note configuration maximums of 8 hosts per cluster in older versions of vSphere and View when using VMFS-based Linked Clones.
    • Reduce the amount of memory given to View desktops. Review the Memory Active in MB counter (above). If memory active is substantially below configured memory, reduce the amount of memory given to desktops. Recommended starting values are 2GB for XP, 2GB for Win7 x86 and 3GB for Win7 x64.

    See http://www.virtualinsanity.com/index.php/2010/02/19/performance-troubleshooting-vmware-vsphere-memory/ for more.

    \VM Memory\Memory Ballooned in MB

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VM Memory\Memory Ballooned in MBMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Limit in MB

    Description: The maximum amount of memory that is allowed to the virtual machine. Assigning a Memory Limit ensures that this virtual machine never consumes more than a certain amount of the allowed memory. By limiting the amount of memory consumed, a portion of this shared resource is allowed to other virtual machines.
    In vSphere, it’s possible to set memory limits that define a maximum quantity of memory a VM is allowed to consume. You might want to set such limits to protect physical memory from being over-consumed by a memory-hungry VM.
    However, if you don’t plan carefully, setting a VM memory limit can have an unexpected impact on VM performance. That impact occurs because the VM is unaware that a limit has been placed upon it. A limited VM with 4GB of assigned vRAM operates under the assumption that it has its full memory assignment. As it attempts to use more memory than its limit, that memory must come from ballooning or swapping. Either of these actions can incur a performance tax on the host, which can impact the performance of other VMs on that host.

    It’s generally not a good idea to set memory limits on VMs. Instead, you should adjust downward the quantity of vRAM assigned to that VM.

    The Memory Limit value shown below should be equal to the amount of vRAM allocated to your View desktop. If the value is less than vRAM assigned, you are limited.

    \VM Memory\Memory Limit in MB

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VM Memory\Memory Limit in MBMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS14,294,967,2954,294,967,2954,294,967,295004,294,967,2954,294,967,2954,294,967,295



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Mapped in MB

    Description: The mapped memory size of this virtual machine. This is the current total amount of guest memory that is backed by physical memory. Note that this number may include pages of memory shared between multiple virtual machines and thus may be an overestimate of the amount of physical host memory *consumed* by this virtual machine.

    \VM Memory\Memory Mapped in MB

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VM Memory\Memory Mapped in MBMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS16,1446,1446,144006,1446,1446,144



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Overhead in MB

    Description: The amount of overhead memory associated with this virtual machine consumed on the host system. Once a virtual machine is powered on the ESX host reserves memory for the the normal operations of VMware infrastructure. This memory can’t be used for swapping or ballooning, and is reserved for the system. Bigger VM’s require more overhead to run.
    See this page for vSphere 5 overhead values: http://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.resmgmt.doc_50%2FGUID-B42C72C1-F8D5-40DC-93D1-FB31849B1114.html
    If you chronically oversize your VM’s, the overhead consumed will increase. This leads to a less efficient datacenter and reduced resources for running VM’s as overhead memory cannot be shared, swapped or ballooned. Right-size your VM’s.

    \VM Memory\Memory Overhead in MB

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VM Memory\Memory Overhead in MBMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS172727200727272



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Reservation in MB

    Description: The minimum amount of memory that is guaranteed to the virtual machine. Assigning a Memory Reservation ensures that even as other virtual machines on the same host consume memory, there is still a certain minimum amount for this virtual machine.
    Reservations may be used in View environments to reduce the footprint of VM’s on disk as reserved memory is included in the .vswap file written to disk for each VM.

    A small reservation on the parent VM can also help ensure that each VM in the pool has at least a little bit of vRAM to work in heavily oversubscribed environments. Take care to not over reserve resources in your environment – do not reserve 100% of memory for each View desktop.

    Starting values for View desktop reservations might be around 10%. For example, If reserving 10% of a 2GB desktop, our vswap is reduced by 205MB per desktop. On a 200 desktop deployment, this can lead to 41GB disk savings (205mb * 200). 205mb reserved memory will probably be enough to keep a Windows desktop running (barely) even if all other memory is ballooned or swapped out if you failed to plan and over-over-subscribed your environment.

    Note: This example 41GB of disk savings will be lost to reserved ESXi host RAM across the cluster. You will not be able to use this host RAM, even if the VM’s with reserved memory are totally idle. This can exacerbate problems caused by oversubscription. To mitigate this impact, consider setting your View pools where you have set a reservation to have a powered-off power policy. A suspend power policy will consume disk space, negating the savings you were trying to achieve by reserving memory.

    \VM Memory\Memory Reservation in MB

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VM Memory\Memory Reservation in MBMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Shared in MB

    Description: The amount of physical memory associated with this virtual machine that is copy-on-write (COW) shared on the host.
    Sharing is good!

    In View environments, most running VM’s will share a common image, especially with Linked Clone pools where all VM’s are running against a common base disk.
    Read more about Transparent Page Sharing (TPS) in View environemnts here: http://myvirtualcloud.net/?p=1797 and here: http://myvirtualcloud.net/?p=2545.

    When multiple virtual machines are running, some of them may have identical sets of memory content. This presents opportunities for sharing memory across virtual machines (as well as sharing within a single virtual machine). For example, several virtual machines may be running the same guest operating system, have the same applications, or contain the same user data. With page sharing,the hypervisor can reclaim the redundant copies and only keep one copy, which is shared by multiple virtual machines in the hostphysical memory. As a result, the total virtual machine host memory consumption is reduced and a higher level of memory overcommitment is possible.

    In ESXi, the redundant page copies are identified by their contents. This means that pages with identical content can be shared regardless of when, where, and how those contents are generated. ESX scans the content of guest physical memory for sharing opportunities. Instead of comparing each byte of a candidate guest physical page to other pages, an action that is prohibitively expensive, ESX uses hashing to identify potentially identical pages.

    \VM Memory\Memory Shared in MB

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VM Memory\Memory Shared in MBMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Shared Saved in MB

    Description: The estimated amount of physical memory on the host saved from copy-on-write (COW) shared guest physical memory.

    This shows the total amount of memory saved on the particular host this VM was running on. More is better. If this value is near zero (0), investigate your host configuration.

    Review http://myvirtualcloud.net/?p=1328 for information on tuning TPS settings to drive higher levels of memory sharing per host.

    \VM Memory\Memory Shared Saved in MB

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VM Memory\Memory Shared Saved in MBMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Shares

    Description: The number of memory shares allocated to the virtual machine.

    This value alone is not significant. Shares must be considered across all VM’s on the host, cluster, and resource pool, if used. If the VM with performance problems has a lower number of shares (or is in a resource pool with a lower number of shares, or oversubscribed shares (http://vmtoday.com/2012/03/vmware-vsphere-resource-pools-resource-allocation-revisited/) than other VM’s it may suffer performance degradation in environments where there is resource contention and/or memory oversubscription.

    Shares play an important role in determining the allocation targets when memory is overcommitted. When the hypervisor needs memory, it reclaims memory from the virtual machine that owns the fewest shares-per-allocated page.

    A significant limitation of the pure proportional-share algorithm is that it does not incorporate any information about the actual memory usage of the virtual machine. As a result, some idle virtual machines with high shares can retain idle memory unproductively, while some active virtual machines with fewer shares suffer from the lack of memory.

    ESX resolves this problem by estimating a virtual machine’s working set size and charging a virtual machine more for the idle memory than for the actively used memory through an idle tax. A virtual machine’s shares-per-allocated page ratio is adjusted to be lower if a fraction of the virtual machine’s memory is idle. Hence, memory will be reclaimed preferentially from the virtual machines that are not fully utilizing their allocated memory. The detailed algorithm can be found in Memory Resource Management in VMware ESX Server.

    \VM Memory\Memory Shares

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VM Memory\Memory SharesMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS161,44061,44061,4400061,44061,44061,440



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Swapped in MB

    Description: The amount of memory associated with this virtual machine that has been swapped by ESX.
    If this is much above zero for an active machine you’ve got problems. TPS and Ballooning have failed to provide sufficient memory for the host to use for other running VM’s because you are oversubscribed, so ESXi is now swapping to disk. Swapping is a slow operation and causes severe degradation of guest performance.

    Resolution

    • Verify Distributed Resource Scheduler is enabled on your cluster. DRS can redistribute VM’s from over-subscribed hosts to less busy hosts.
    • Install more memory in physical hosts.
    • Change the power policy of VMware View pools to suspend or power-off to conserve host resources. Note: this is at the expense of increased logon times for users.
    • Add additional hosts to cluster. Note configuration maximums of 8 hosts per cluster in older versions of vSphere and View when using VMFS-based Linked Clones.
    • Reduce the amount of memory given to View desktops. Review the Memory Active in MB counter (above). If memory active is substantially below configured memory, reduce the amount of memory given to desktops. Recommended starting values are 2GB for XP, 2GB for Win7 x86 and 3GB for Win7 x64.

    \VM Memory\Memory Swapped in MB

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VM Memory\Memory Swapped in MBMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Memory Used in MB

    Description: The estimated amount of physical host memory currently consumed for this virtual machine’s physical memory. This is the same as ‘Memory Mapped in MB’ – ‘Memory Shared Saved in MB’.

    \VM Memory\Memory Used in MB

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VM Memory\Memory Used in MBMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS16,1446,1446,144006,1446,1446,144



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    VM Processor


    Limit in MHz

    Description: The maximum processing power in MHz allowed to the virtual machine. Assigning a CPU Limit ensures that this virtual machine never consumes more than a certain amount of the available processor power. By limiting the amount of processing power consumed, a portion of the processing power becomes available to other virtual machines.

    From VMware KB 1033115: When a CPU Limit is set on a virtual machine resource settings, the virtual machine is deliberately held from being scheduled to a PCPU when it has used up its allocated CPU resource. This happens regardless of the CPU utilization. If the limit is set to 500MHz, the virtual machine is descheduled from the PCPU and has to wait before it is allowed to be scheduled again. As such, the virtual machine might experience performance degradation.

    Note: For an SMP virtual machine, the sum of all vCPUs cannot exceed the specified limit. For example, 4 vCPU virtual machine with a limit of 1200MHz and equal load among vCPUs would result in a max of 300MHz per vCPU.

    Translated, this means that we’re not slowing down the pCPU for this VM – that’s not possible. What we are doing is basically artificially introducing CPU Ready (for more on CPU Ready see here: http://vmtoday.com/2010/08/high-cpu-ready-poor-performance/) for the VM.

    If the value shown here is less than the ‘Host Processor Speed in MHz’ value, you are limited. The default for VM’s is ‘unlimited’, which should appear as some unwieldy number in the range of terahertz or petahertz (not that your servers can do this).

    \VM Processor(*)\Limit in MHz

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VM Processor(*)\Limit in MHzMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/_Total4,294,967,2954,294,967,2954,294,967,295004,294,967,2954,294,967,2954,294,967,295



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Reservation in MHz

    Description: The minimum processing power in MHz available to the virtual machine. Assigning a CPU Reservation ensures that even as other virtual machines on the same host consume shared processing power, there is still a certain minimum amount for this virtual machine.

    See http://www.yellow-bricks.com/2010/07/08/reservations-primer/ and http://frankdenneman.nl/2010/06/reservations-and-cpu-scheduling/for more info on reservations.

    In general, you should not be setting a reservation for Veiw desktops. There may be some unique use cases for reserving CPU for high-profile users’ desktops (CEO, CTO, your own admin console) in View. Do this sparingly, as reservations can limit the ESXi scheduler and make your virtual datacenter inefficient. CPU Reservations can introduce higher CPU ready for VM’s without reservations. Reservations may not solve CPU Ready issues for the VM’s they are set on either (http://joshodgers.com/2012/07/22/common-mistake-using-cpu-reservations-to-solve-cpu-ready/

    \VM Processor(*)\Reservation in MHz

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VM Processor(*)\Reservation in MHzMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/_Total00000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Shares

    Description: The number of CPU shares allocated to the virtual machine.

    Each virtual machine is granted a number of CPU shares. The more shares a virtual machine has, the more often it gets a time slice of a CPU when there is no CPU idle time. Shares represent a relative metric for allocating CPU capacity.

    This value alone is not significant. Shares must be considered across all VM’s on the host, cluster, and resource pool, if used. If the VM with performance problems has a lower number of shares (or is in a resource pool with a lower number of shares, or oversubscribed shares (http://vmtoday.com/2012/03/vmware-vsphere-resource-pools-resource-allocation-revisited/) than other VM’s it may suffer performance degradation in environments where there is resource contention and/or memory oversubscription.

    Read this VMware PDF for a deep-dive into CPU Scheduling: http://www.vmware.com/files/pdf/techpaper/VMW_vSphere41_cpu_schedule_ESX.pdf

    If this value is variable (not a flat line), this may indicate that your VM is in a resource pool configured with a set number of shares. As your View environment dynamically spins up and down VM’s within the pool, the percentage of shares for a particular machine will vary. Understand the impact of shares, reservations and limits on VMs and Resource Pools!!!!

    \VM Processor(*)\Shares

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VM Processor(*)\SharesMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/_Total2,0002,0002,000002,0002,0002,000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    CPU stolen time

    Description: The time (in ms) that the VM was runnable but not scheduled to run.

    This is CPU Ready!!!

    For more on CPU Ready see: http://vmtoday.com/2010/08/high-cpu-ready-poor-performance/

    CPU Ready is often a sign of over subscribing CPU resources or over-sizing your virtual machines. This counter shows CPU Ready time as a percentage per milisecond that the CPU was ready to run but could not be scheduled by the ESXi Scheduler. Multiply by 100 to get percentage of CPU Ready. In general, anything above 10% CPU Ready will result in poor performance.
    For more on Scheduling/Time Keeping in VM’s see: http://www.vmware.com/files/pdf/Timekeeping-In-VirtualMachines.pdf. Also see the vSphere Performance Monitoring Guide here: http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-monitoring-performance-guide.pdf

    If this counter is in a warning or critical state, check CPU Ready for the host that this VM is running on in vCenter. The value in the realtime graph is a summation of miliseconds VM’s were ready but could not be scheduled. Divide the value shown in the vCenter ESXi Performance tab by the number of milisecond timeslices in the graph (realtime graph = 20 second refresh = 20000 slices). Example: If CPU ready is 5200 on the CPU/RealTime graph, divide 5200/20000 = .26 x 100 = 26% CPU RDY. Also check ESXTOP on the ESXi host that this VM is running on. If multiple VM’s show high CPU ready, you are over-provisioning VM’s with too many vCPU’s or have too high of a consolidation ration (too many VM’s per host). Remove vCPU’s or add additional pCPU’s or hosts.

    \VM Processor(*)\CPU stolen time

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VM Processor(*)\CPU stolen timeMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/_Total00000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    % Processor Time

    Description: Current load of the VM’s virtual processor(s).

    This is the amount of time that the CPU is active. If the VM is using vSMP, this is the aggregate average of all CPU’s in the VM.

    If this value is regularly over 70%, you may benefit from adding an additional vCPU. Be aware, however, that an additional CPU multiplied over all VM’s may drive CPU Ready upwards, negatively impacting performance.

    \VM Processor(*)\% Processor Time

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VM Processor(*)\% Processor TimeMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/_Total5715-843666



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Effective VM Speed in MHz

    Description: The approximate average effective speed of the VM’s virtual CPU over the time period between the two samples.

    Remember, A VM’s vCPU cannot go any faster than the speed of a single core/thread of the physical CPU that’s backing it.

    \VM Processor(*)\Effective VM Speed in MHz

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VM Processor(*)\Effective VM Speed in MHzMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/_Total88146634-12,853127111102101



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Host processor speed in MHz

    Description: Host Processor speed.

    This is the clock speed of the physical processor backing the VM. If this value fluxuates, it could be due to a couple issues:
    1.) vMotion of VM between hosts with different physical hardware. Best practice for VMware vSphere clusters suggests maintaining hosts with identical hardare configurations to prevent unpredictable performance as VM’s are vMotioned from host to host. Identical host configuration may also help VMware vSphere Distributed Resource Scheduler recommend best placement for VM’s.
    2.) Power Management settings – if your host is configured with active/dynamic power management in BIOS. Consider setting a static ‘High Performance’ power management profile or disable power management in BIOS. See this VMware KB for more info: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1018206

    \VM Processor(*)\Host processor speed in MHz

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VM Processor(*)\Host processor speed in MHzMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS1/_Total2,3942,3942,394002,3942,3942,394



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Vmware View Connection Server


    All Sessions

    Description: Total numberof all View sessions active over the sampling period.

    A Connection Server can sustain no more than 2000 active PCoIP sessions. This counter includes PCoIP as well as RDP connetions being brokered by this connection server.

    View is typically licensed per concurrent user, with unlimited licenses for Connection and Security servers. If your active session count is high, add additional Connection or Security Servers

    View supports up to 7 Connection Servers (5 actively serving users, 2 standby) per Pod.

    Multiple Connection Servers must be load balanced using a support load balaning mechanism including DNS Round Robin, Network Load Balancing, or a software/hardware load balancing appliance.

    \VMware VDM\All Sessions

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\All SessionsMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS111100111



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    All Sessions High

    Description: Running count of the max number of sessions this View Connection Server has served at any one time. Verify that you have sufficient Connection and Security Servers to handle your peak AND to account for N+1 redundancy.

    \VMware VDM\All Sessions High

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\All Sessions HighMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS111100111



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Full VM Sessions

    Description: Total number of Full VM sessions in use over the sampling period.

    \VMware VDM\Full VM Sessions

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\Full VM SessionsMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Full VM Sessions High

    Description: Maximum number of Full VM sessions at any one time.

    \VMware VDM\Full VM Sessions High

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\Full VM Sessions HighMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Linked Clone Sessions

    Description: Total number of Linked Clone sessions in use over the sampling period.

    \VMware VDM\Linked Clone Sessions

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\Linked Clone SessionsMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS111100111



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Linked Clone Sessions High

    Description: Maximum number of Linked Clone sessions at any one time.

    \VMware VDM\Linked Clone Sessions High

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\Linked Clone Sessions HighMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS111100111



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Other Sessions

    Description: Total number of other sessions in use over the sampling period, including admin, TS, etc..

    \VMware VDM\Other Sessions

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\Other SessionsMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Other Sessions High

    Description: Maximum number of other sessions in use any any one time, including admin, TS, etc..

    \VMware VDM\Other Sessions High

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\Other Sessions HighMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    PCoIP Gateway Sessions

    Description: Total number of PCoIP gateway sessions that are currently open.

    \VMware VDM\PCoIP Gateway Sessions

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\PCoIP Gateway SessionsMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    PCoIP Gateway Sessions High

    Description: An incrementing number that represents the total number of PCoIP gateway sessions that have been open at any one time

    \VMware VDM\PCoIP Gateway Sessions High

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\PCoIP Gateway Sessions HighMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Secure Gateway Sessions

    Description: Total number of Secure Gateway sessions that are currently open.

    \VMware VDM\Secure Gateway Sessions

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\Secure Gateway SessionsMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Secure Gateway Sessions High

    Description: An incrementing number that represents the total number of Secure Gateway sessions that have been open at any one time

    \VMware VDM\Secure Gateway Sessions High

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\Secure Gateway Sessions HighMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    VMware View Connection Server


    All Sessions

    Description: Total numberof all View sessions active over the sampling period.

    A Connection Server can sustain no more than 2000 active PCoIP sessions. This counter includes PCoIP as well as RDP connetions being brokered by this connection server.

    View is typically licensed per concurrent user, with unlimited licenses for Connection and Security servers. If your active session count is high, add additional Connection or Security Servers

    View supports up to 7 Connection Servers (5 actively serving users, 2 standby) per Pod.

    Multiple Connection Servers must be load balanced using a support load balaning mechanism including DNS Round Robin, Network Load Balancing, or a software/hardware load balancing appliance.

    \VMware VDM\All Sessions

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\All SessionsMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS111100111



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    All Sessions High

    Description: Running count of the max number of sessions this View Connection Server has served at any one time. Verify that you have sufficient Connection and Security Servers to handle your peak AND to account for N+1 redundancy.

    \VMware VDM\All Sessions High

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\All Sessions HighMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS111100111



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Full VM Sessions

    Description: Total number of Full VM sessions in use over the sampling period.

    \VMware VDM\Full VM Sessions

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\Full VM SessionsMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Full VM Sessions High

    Description: Maximum number of Full VM sessions at any one time.

    \VMware VDM\Full VM Sessions High

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\Full VM Sessions HighMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Linked Clone Sessions

    Description: Total number of Linked Clone sessions in use over the sampling period.

    \VMware VDM\Linked Clone Sessions

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\Linked Clone SessionsMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS111100111



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Linked Clone Sessions High

    Description: Maximum number of Linked Clone sessions at any one time.

    \VMware VDM\Linked Clone Sessions High

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\Linked Clone Sessions HighMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS111100111



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Other Sessions

    Description: Total number of other sessions in use over the sampling period, including admin, TS, etc..

    \VMware VDM\Other Sessions

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\Other SessionsMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Other Sessions High

    Description: Maximum number of other sessions in use any any one time, including admin, TS, etc..

    \VMware VDM\Other Sessions High

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\Other Sessions HighMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    PCoIP Gateway Sessions

    Description: Total number of PCoIP gateway sessions that are currently open.

    \VMware VDM\PCoIP Gateway Sessions

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\PCoIP Gateway SessionsMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    PCoIP Gateway Sessions High

    Description: An incrementing number that represents the total number of PCoIP gateway sessions that have been open at any one time

    \VMware VDM\PCoIP Gateway Sessions High

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\PCoIP Gateway Sessions HighMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Secure Gateway Sessions

    Description: Total number of Secure Gateway sessions that are currently open.

    \VMware VDM\Secure Gateway Sessions

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\Secure Gateway SessionsMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Secure Gateway Sessions High

    Description: An incrementing number that represents the total number of Secure Gateway sessions that have been open at any one time

    \VMware VDM\Secure Gateway Sessions High

    Overall Counter Instance Statistics

    Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.

    Condition\VMware VDM\Secure Gateway Sessions HighMinAvgMaxHourly TrendStd Deviation10% of Outliers Removed20% of Outliers Removed30% of Outliers Removed
    No ThresholdsVIEWCS100000000



    Alerts

    An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
    No Alerts Found


    Back to the top

    Back to the top

    Disclaimer: This report was generated using the Performance Analysis of Logs (PAL) tool. The information provided in this report is provided “as-is” and is intended for information purposes only. The software is licensed “as-is”. You bear the risk of using it. The contributors give no express warranties, guarantees or conditions. You may have additional consumer rights under your local laws which this license cannot change. To the extent permitted under your local laws, the contributors exclude the implied warranties of merchantability, fitness for a particular purpose and non-infringement.

    { 0 comments… add one now }

    Leave a Comment

    { 1 trackback }