Group: "active server pages"| asp debugging requests | Number of debugging document requests. |
| asp engine flush notifications | The number of engines invalidated in the cache due to change notification. |
| asp errors during script runtime | Number of requests failed due to runtime errors. |
| asp errors fromasppreprocessor | Number of requests failed due to preprocessor errors. |
| asp errors from script compilers | Number of requests failed due to script compilation errors. |
| asp errors per sec | The number of errors per second. |
| asp in memory template cache hit rate | Percent of requests found in cached in memory. |
| asp in memory templates cached | The number of compiled templates cached in memory. |
| asp request bytes in total | The total size, in bytes, of all requests. |
| asp request bytes out total | The total size, in bytes, of responses sent to clients. This does not include standard HTTP response headers. |
| asp request execution time | The number of milliseconds that it took to execute the most recent request. |
| asp request wait time | The number of milliseconds the most recent request was waiting in the queue. |
| asp requests disconnected | The number of requests that were disconnected due to communication failure. |
| asp requests executing | The number of requests currently executing. |
| asp requests failed total | The total number of requests failed due to errors, authorization failure, and rejections. |
| asp requests not authorized | Number of requests failed due to insufficient access rights. |
| asp requests not found | The number of requests for files that were no found. |
| asp requests queued | The number of requests waiting for service from the queue. |
| asp requests rejected | The total number of requests not executed because there were insufficient resources to process them. |
| asp requests succeeded | The number of requests that executed successfully. |
| asp requests timed out | The number of requests that timed out. |
| asp requests total | The total number of requests since the service was started. |
| asp requests per sec | The number of requests executed per second. |
| asp script engine cache hit rate | Percent of requests found in script engine cache. |
| asp script engines cached | The number of script engines in cache. |
| asp session duration | The number of milliseconds that the most recent session persisted. |
| asp sessions current | The current number of sessions being serviced. |
| asp sessions timed out | The number of sessions timed out. |
| asp sessions total | The total number of sessions since the service was started. |
| asp template cache hit rate | Percent of requests found in template cache. |
| asp template notifications | The number of templates invalidated in the cache due to change notification. |
| asp templates cached | The number of templates currently cached. |
| asp transactions aborted | The number of transactions aborted. |
| asp transactions committed | The number of transactions committed. |
| asp transactions pending | Number of transactions in progress. |
| asp transactions total | The total number of transactions since the service was started. |
| asp transactions per sec | Transactions started per second. |
Group: "apple talk"| at aarp packets per sec (Table) | Number of AARP packets per second received by Appletalk on this port. |
| at atp aloresponse per sec (Table) | Number of ATP At-least-once transaction responses per second on this port. |
| at atp packets per sec (Table) | Number of ATP packets per second received by Appletalk on this port. |
| at atp recvd release per sec (Table) | Number of ATP transaction release packets per second received on this port. |
| at atp response timouts (Table) | Number of ATP release timers that have expired on this port. |
| at atp retries local (Table) | Number of ATP requests retransmitted on this port. |
| at atp retries remote (Table) | Number of ATP requests retransmitted to this port. |
| at atp xoresponse per sec (Table) | Number of ATP Exactly-once transaction responses per second on this port. |
| at average time per aarp packet (Table) | Average time in milliseconds to process an AARP packet on this port. |
| at average time per atp packet (Table) | Average time in milliseconds to process an ATP packet on this port. |
| at average time per ddp packet (Table) | Average time in milliseconds to process a DDP packet on this port. |
| at average time per nbp packet (Table) | Average time in milliseconds to process an NBP packet on this port. |
| at average time per rtmp packet (Table) | Average time in milliseconds to process an RTMP packet on this port. |
| at average time per zip packet (Table) | Average time in milliseconds to process a ZIP packet on this port. |
| at bytes in per sec (Table) | Number of bytes received per second by Appletalk on this port. |
| at bytes out per sec (Table) | Number of bytes sent per second by Appletalk on this port. |
| at current non paged pool (Table) | The current amount of nonpaged memory resources used by AppleTalk. |
| at ddp packets per sec (Table) | Number of DDP packets per second received by Appletalk on this port. |
| at nbp packets per sec (Table) | Number of NBP packets per second received by Appletalk on this port. |
| at packets in per sec (Table) | Number of packets received per second by Appletalk on this port. |
| at packets out per sec (Table) | Number of packets sent per second by Appletalk on this port. |
| at packets routed in per sec (Table) | Number of packets routed in on this port. |
| at packets routed out per sec (Table) | Number of packets routed out on this port. |
| at packets dropped (Table) | Number of packets dropped due to resource limitations on this port. |
| at rtmp packets per sec (Table) | Number of RTMP packets per second received by Appletalk on this port. |
| at zip packets per sec (Table) | Number of ZIP packets per second received by Appletalk on this port. |
Group: "asp dotnetapplications"| adn appl anonymous requests (Table) | Number of requests utilizing anonymous authentication. |
| adn appl anonymous requests per sec (Table) | Number of Authentication Anonymous Requests/Sec |
| adn appl cacheapientries (Table) | Total number of entries within the cache added by the user. |
| adn appl cacheapihit ratio (Table) | Ratio of hits called from user code. |
| adn appl cacheapihits (Table) | Number of cache hits from user code. |
| adn appl cacheapimisses (Table) | Number of cache misses called from user code. |
| adn appl cache api turnover rate (Table) | Number of additions and removals to the API cache per second. |
| adn appl cache total entries (Table) | Total number of entries within the cache (both internal and user added) |
| adn appl cache total hit ratio (Table) | Ratio of hits from all cache calls. |
| adn appl cache total hits (Table) | Total number of hits from the cache. |
| adn appl cache total misses (Table) | Total number of cache misses. |
| adn appl cache total turnover rate (Table) | Number of additions and removals to the total cache per second. |
| adn appl compilations total (Table) | Number of .asax, .ascx, .ashx, .asmx, or .aspx source files dynamically compiled. |
| adn appl debugging requests (Table) | Number of debugging requests processed. |
| adn appl errors compilation (Table) | Number of errors that have occurred during compilation. |
| adn appl errors execution (Table) | Number of errors that have occurred during the processing of a request. |
| adn appl errors preprocessing (Table) | Number of errors that have occurred during parsing and configuration. |
| adn appl errors total (Table) | Total number of errors occurred. |
| adn appl errors total per sec (Table) | Rate of errors occurred. |
| adn appl errors unhandled exec (Table) | Number of errors not handled by user code, but by the default error handler. |
| adn appl errors unhandled exec per sec (Table) | Rate of unhandled errors. |
| adn appl output cache entries (Table) | Current number of entries in the output cache. |
| adn appl output cache hit ratio (Table) | Ratio of hits to requests for output cacheable requests. |
| adn appl output cache hits (Table) | Total number of ouput cacheable requests served from the output cache. |
| adn appl output cache misses (Table) | Total number of ouput cacheable requests not served from the output cache. |
| adn appl output cache turnover rate (Table) | Number of additions and removals to the output cache per second. |
| adn appl pipeline instance count (Table) | Number of active pipeline instances. |
| adn appl request bytes in total (Table) | The total size, in bytes, of all requests. |
| adn appl request bytes out total (Table) | The total size, in bytes, of responses sent to a client. This does not include standard HTTP response headers. |
| adn appl requests executing (Table) | The number of requests currently executing. |
| adn appl requests failed (Table) | Total number of failed requests. |
| adn appl requests in appl queue (Table) | The number of requests in the application request queue. |
| adn appl requests not authorized (Table) | Number of requests failed due to unauthorized access. |
| adn appl requests not found (Table) | The number of requests for resources that were not found. |
| adn appl requests succeeded (Table) | The number of requests that executed successfully. |
| adn appl requests timed out (Table) | The number of requests that timed out. |
| adn appl requests total (Table) | The total number of requests since the application was started. |
| adn appl requests per sec (Table) | The number of requests executed per second. |
| adn appl session sql srvr conn total (Table) | The total number of connections to the SQL Server used by session state. |
| adn appl session state srvr conn total (Table) | The total number of connections to the State Server used by session state. |
| adn appl sessions abandoned (Table) | The number of sessions that have been explicitly abandoned. |
| adn appl sessions active (Table) | The current number of sessions currently active. |
| adn appl sessions timed out (Table) | The number of sessions timed out. |
| adn appl sessions total (Table) | Total number of sessions since the application was started. |
| adn appl transactions aborted (Table) | The number of transactions aborted. |
| adn appl transactions committed (Table) | The number of transactions committed. |
| adn appl transactions pending (Table) | Number of transactions in progress. |
| adn appl transactions total (Table) | The total number of transactions since the application was started. |
| adn appl transactions per sec (Table) | Transactions started per second. |
Group: "browser"| browser announcements domain per sec | Announcements Domain/sec is the rate at which a Domain has announced itself to the network. |
| browser announcements server per sec | Announcements Server/sec is the rate at which the servers in this domain have announced themselves to this server. |
| browser announcements total per sec | Announcements Total/sec is the sum of Announcements Server/sec and Announcements Domain/sec. |
| browser duplicate master announce | Duplicate Master Announcements indicates the number of times that the master browser has detected another master browser on the same domain. |
| browser election packets per sec | Election Packets/sec is the rate of Browser election packets that have been received by this workstation. |
| browser enumerations domain per sec | Enumerations Domain/sec is the rate of Domain browse requests that have been processed by this workstation. |
| browser enumerations other per sec | Enumerations Other/sec is the rate of browse requests processed by this workstation that were not domain or server browse requests. |
| browser enumerations server per sec | Enumerations Server/sec is the rate of Server browse requests that have been processed by this workstation. |
| browser enumerations total per sec | Enumerations Total/sec is the rate of browse requests that have been processed by this workstation. This is the sum of Enumerations Server, Enumerations Domain, and Enumerations Other. |
| browser illegal datagrams per sec | Illegal Datagrams/sec is the rate of incorrectly formatted datagrams that have been received by the workstation. |
| browser mailslot allocations failed | Mailslot Allocations Failed is the number of times the datagram receiver has failed to allocate a buffer to hold a user mailslot write. |
| browser mailslot opens failed per sec | Mailslot Opens Failed/sec indicates the rate of mailslot messages received by this workstation that were to be delivered to mailslots that are not present on this workstation. |
| browser mailslot receives failed | Mailslot Receives Failed indicates the number of mailslot messages that couldn't be received due to transport failures. |
| browser mailslot writes failed | Mailslot Writes Failed is the total number of mailslot messages that have been successfully received, but that were unable to be written to the mailslot. |
| browser mailslot writes per sec | Mailslot Writes/sec is the rate of mailslot messages that have been successfully received. |
| browser missed mailslot datagrams | Missed Mailslot Datagrams is the number of Mailslot Datagrams that have been discarded due to configuration or allocation limits. |
| browser missed server announcements | Missed Server Announcements is the number of server announcements that have been missed due to configuration or allocation limits. |
| browser missed server list requests | Missed Server List Requests is the number of requests to retrieve a list of browser servers that were received by this workstation, but could not be processed. |
| browser server alloc failed per sec | Server Announce Allocations Failed/sec is the rate of server (or domain) announcements that have failed due to lack of memory. |
| browser server list requests per sec | Server List Requests/sec is the rate of requests to retrieve a list of browser servers that have been processed by this workstation. |
Group: "cache"| cache async copy reads per sec | Async Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer. The application will regain control immediately even if the disk must be accessed to retrieve the page. |
| cache async data maps per sec | Async Data Maps/sec is the frequency that an application using a file system, such as NTFS, to map a page of a file into the file system cache to read the page, and does not wait for the page to be retrieved if it is not in main memory. |
| cache async fast reads per sec | Async Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the data directly from the cache. Normally, file I/O requests will invoke the appropriate file system to retrieve data from a file, but this path permits data to be retrieved from the cache directly (without file system involvement) if the data is in the cache. Even if the data is not in the cache, one invocation of the file system is avoided. If the data is not in the cache, the request (application program call) will not wait until the data has been retrieved from disk, but will get control immediately. |
| cache async mdl reads per sec | Async MDL Reads/sec is the frequency of reads from the file system cache that use a Memory Descriptor List (MDL) to access the pages. The MDL contains the physical address of each page in the transfer, thus permitting Direct Memory Access (DMA) of the pages. If the accessed page(s) are not in main memory, the calling application program will not wait for the pages to fault in from disk. |
| cache async pin reads per sec | Async Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk. Pages read in this fashion are pinned in memory at the completion of the read. The file system will regain control immediately even if the disk must be accessed to retrieve the page. While pinned, a page's physical address will not be altered. |
| cache copy read hits percent | Copy Read Hits is the percentage of cache copy read requests that hit the cache, that is, they did not require a disk read in order to provide access to the page in the cache. A copy read is a file read operation that is satisfied by a memory copy from a page in the cache to the application's buffer. The LAN Redirector uses this method for retrieving information from the cache, as does the LAN Server for small transfers. This is a method used by the disk file systems as well. |
| cache copy reads per sec | Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer. The LAN Redirector uses this method for retrieving information from the file system cache, as does the LAN Server for small transfers. This is a method used by the disk file systems as well. |
| cache data flush pages per sec | Data Flush Pages/sec is the number of pages the file system cache has flushed to disk as a result of a request to flush or to satisfy a write-through file write request. More than one page can be transferred on each flush operation. |
| cache data flushes per sec | Data Flushes/sec is the rate at which the file system cache has flushed its contents to disk as the result of a request to flush or to satisfy a write-through file write request. More than one page can be transferred on each flush operation. |
| cache data map hits percent | Data Map Hits is the percentage of data maps in the file system cache that could be resolved without having to retrieve a page from the disk, because the page was already in physical memory. |
| cache data map pins per sec | Data Map Pins/sec is the frequency of data maps in the file system cache that resulted in pinning a page in main memory, an action usually preparatory to writing to the file on disk. While pinned, a page's physical address in main memory and virtual address in the file system cache will not be altered. |
| cache data maps per sec | Data Maps/sec is the frequency that a file system such as NTFS, maps a page of a file into the file system cache to read the page. |
| cache fast read not possibles per sec | Fast Read Not Possibles/sec is the frequency of attempts by an Application Program Interface (API) function call to bypass the file system to get to data in the file system cache that could not be honored without invoking the file system. |
| cache fast read resource miss per sec | Fast Read Resource Misses/sec is the frequency of cache misses necessitated by the lack of available resources to satisfy the request. |
| cache fast reads per sec | Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the data directly from the cache. Normally, file I/O requests invoke the appropriate file system to retrieve data from a file, but this path permits direct retrieval of data from the cache without file system involvement if the data is in the cache. Even if the data is not in the cache, one invocation of the file system is avoided. |
| cache lazy write flushes per sec | 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. |
| cache lazy write pages per sec | Lazy Write Pages/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 on a single disk write operation. |
| cache mdl read hits percent | MDL Read Hits is the percentage of Memory Descriptor List (MDL) Read requests to the file system cache that hit the cache, i.e., did not require disk accesses in order to provide memory access to the page(s) in the cache. |
| cache mdl reads per sec | MDL Reads/sec is the frequency of reads from the file system cache that use a Memory Descriptor List (MDL) to access the data. The MDL contains the physical address of each page involved in the transfer, and thus can employ a hardware Direct Memory Access (DMA) device to effect the copy. The LAN Server uses this method for large transfers out of the server. |
| cache pin read hits percent | Pin Read Hits is the percentage of pin read requests that hit the file system cache, i.e., did not require a disk read in order to provide access to the page in the file system cache. While pinned, a page's physical address in the file system cache will not be altered. The LAN Redirector uses this method for retrieving data from the cache, as does the LAN Server for small transfers. This is usually the method used by the disk file systems as well. |
| cache pin reads per sec | Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk. Pages read in this fashion are pinned in memory at the completion of the read. While pinned, a page's physical address in the file system cache will not be altered. |
| cache read aheads per sec | Read Aheads/sec is the frequency of reads from the file system cache in which the Cache detects sequential access to a file. The read aheads permit the data to be transferred in larger blocks than those being requested by the application, reducing the overhead per access. |
| cache sync copy reads per sec | Sync Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer. The file system will not regain control until the copy operation is complete, even if the disk must be accessed to retrieve the page. |
| cache sync data maps per sec | Sync Data Maps/sec counts the frequency that a file system, such as NTFS, maps a page of a file into the file system cache to read the page, and wishes to wait for the page to be retrieved if it is not in main memory. |
| cache sync fast reads per sec | Sync Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the data directly from the cache. Normally, file I/O requests invoke the appropriate file system to retrieve data from a file, but this path permits direct retrieval of data from the cache without file system involvement if the data is in the cache. Even if the data is not in the cache, one invocation of the file system is avoided. If the data is not in the cache, the request (application program call) will wait until the data has been retrieved from disk. |
| cache sync mdl reads per sec | Sync MDL Reads/sec is the frequency of reads from the file system cache that use a Memory Descriptor List (MDL) to access the pages. The MDL contains the physical address of each page in the transfer, thus permitting Direct Memory Access (DMA) of the pages. If the accessed page(s) are not in main memory, the caller will wait for the pages to fault in from the disk. |
| cache sync pin reads per sec | Sync Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk. Pages read in this fashion are pinned in memory at the completion of the read. The file system will not regain control until the page is pinned in the file system cache, in particular if the disk must be accessed to retrieve the page. While pinned, a page's physical address in the file system cache will not be altered. |
Group: "dns"| dns axfr request received | AXFR Request Received is the total number of full zone transfer requests received by the master DNS server. |
| dns axfr request sent | AXFR Request Sent is the total number of full zone transfer requests sent by the secondary DNS server. |
| dns axfr response received | AXFR Response Received is the total number of full zone transfer responses received by the secondary DNS server. |
| dns axfr success received | AXFR Success Received is the total number of successful full zone transfers received by the secondary DNS server. |
| dns axfr success sent | AXFR Success Sent is the total number of successful full zone transfers of the master DNS server. |
| dns caching memory | Caching Memory is the total caching memory used by DNS server. |
| dns database node memory | Database Node Memory is the total database node memory used by DNS server. |
| dns dynamic update no operation | Dynamic Update NoOperation is the total number of No-operation/Empty dynamic update requests received by the DNS server. |
| dns dynamic update no op per sec | Dynamic Update NoOperation/sec is the average number of No-operation/Empty dynamic update requests received by the DNS server in each second. |
| dns dynamic update queued | Dynamic Update Queued is the total number of dynamic updates queued by the DNS server. |
| dns dynamic update received | Dynamic Update Received is the total number of dynamic update requests received by the DNS server. |
| dns dynamic update received per sec | Dynamic Update Received/sec is the average number of dynamic update requests received by the DNS server in each second. |
| dns dynamic update rejected | Dynamic Update Rejected is the total number of dynamic updates rejected by the DNS server. |
| dns dynamic update time outs | Dynamic Update TimeOuts is the total number of dynamic update timeouts of the DNS server. |
| dns dynamic update write todb | Dynamic Update Written to Database is the total number of dynamic updates written to the database by the DNS server. |
| dns dynamic update write todbper sec | Dynamic Update Written to Database/sec is the average number of dynamic updates written to the database by the DNS server in each second. |
| dns ixfr request received | IXFR Request Received is the total number of incremental zone transfer requests received by the master DNS server. |
| dns ixfr request sent | IXFR Request Sent is the total number of incremental zone transfer requests sent by the secondary DNS server. |
| dns ixfr response received | IXFR Response Received is the total number of incrementalzone transfer responses received by the secondary DNS server. |
| dns ixfr success received | IXFR Success Received is the total number of successful incremental zone transfers received by the secondary DNS server. |
| dns ixfr success sent | IXFR Success Sent is the total number of successful incremental zone transfers of the master DNS server. |
| dns ixfr tcp success received | IXFR TCP Success Received is the total number of successful TCP incremental zone transfers received by the secondary DNS server. |
| dns ixfr udp success received | IXFR UDP Success Received is the total number of successful UDP incremental zone transfers received by the secondary DNS server. |
| dns nbstat memory | Nbstat Memory is the total Nbstat memory used by DNS server. |
| dns notify received | Notify Received is the total number of notifies received by the secondary DNS server. |
| dns notify sent | Notify Sent is the total number of notifies sent by the master DNS server. |
| dns record flow memory | Record Flow Memory is the total record flow memory used by DNS server. |
| dns recursive queries | Recursive Queries is the total number of recursive queries received by DNS server. |
| dns recursive queries per sec | Recursive Queries/sec is the average number of recursive queries received by DNS server in each sencond. |
| dns recursive query failure | Recursive Query Failure is the total number of recursive query failures. |
| dns recursive query failure per sec | Recursive Query Failure/sec is the average number of recursive query failures in each second. |
| dns recursive send time outs | Recursive TimeOuts is the total number of recursive query sending timeouts. |
| dns recursive time out per sec | Recursive TimeOut/sec is the average number of recursive query sending timeouts in each second. |
| dns secure update failure | Secure Update Failure is the total number of secure updates failed of the DNS server. |
| dns secure update received | Secure Update Received is the total number of secure update requests received by the DNS server. |
| dns secure update received per sec | Secure Update Received/sec is the average number of secure update requests received by the DNS server in each second. |
| dns tcp message memory | TCP Message Memory is the total TCP message memory used by DNS server. |
| dns tcp query received | TCP Query Received is the total number of TCP queries received by DNS server. |
| dns tcp query received per sec | TCP Query Received/sec is the average number of TCP queries received by DNS server in each second. |
| dns tcp response sent | TCP Response Sent is the total number of TCP reponses sent by DNS server. |
| dns tcp response sent per sec | TCP Response Sent/sec is the average number of TCP reponses sent by DNS server in each second. |
| dns total query received | Total Query Received is the total number of queries received by DNS server. |
| dns total query received per sec | Total Query Received/sec is the average number of queries received by DNS server in each second. |
| dns total response sent | Total Response Sent is the total number of reponses sent by DNS server. |
| dns total response sent per sec | Total Response Sent/sec is the average number of reponses sent by DNS server in each second. |
| dns udp message memory | UDP Message Memory is the total UDP message memory used by DNS server. |
| dns udp query received | UDP Query Received is the total number of UDP queries received by DNS server. |
| dns udp query received per sec | UDP Query Received/sec is the average number of UDP queries received by DNS server in each second. |
| dns udp response sent | UDP Response Sent is the total number of UDP reponses sent by DNS server. |
| dns udp response sent per sec | UDP Response Sent/sec is the average number of UDP reponses sent by DNS server in each second. |
| dns wins lookup received | WINS Lookup Received is the total number of WINS lookup requests received by the server. |
| dns wins lookup received per sec | WINS Lookup Received/sec is the average number of WINS lookup requests received by the server in each second. |
| dns wins response sent | WINS Response Sent is the total number of WINS lookup responses sent by the server. |
| dns wins response sent per sec | WINS Response Sent/sec is the average number of WINS lookup responses sent by the server in each second. |
| dns wins reverse lookup received | WINS Reverse Lookup Received is the total number of WINS reverse lookup requests received by the server. |
| dns wins reverse lookup rcv per sec | WINS Reverse Lookup Received/sec is the average number of WINS reverse lookup requests received by the server in each second. |
| dns wins reverse response sent | WINS Reverse Response Sent is the total number of WINS Reverse lookup responses sent by the server. |
| dns wins reverse response sent per sec | WINS Reverse Response Sent/sec is the average number of WINS Reverse lookup responses sent by the server in each second. |
| dns zone transfer failure | Zone Transfer Failure is the total number of failed zone transfers of the master DNS server. |
| dns zone transfer request received | Zone Transfer Request Received is the total number of zone transfer requests received by the master DNS server. |
| dns zone transfer soa request sent | Zone Transfer SOA Request Sent is the total number of zone transfer SOA requests sent by the secondary DNS server. |
| dns zone transfer success | Zone Transfer Success is the total number of successful zone transfers of the master DNS server. |
Group: "dotnetclrmemory"| ncm num bytes in all heaps (Table) | This counter is the sum of four other counters; Gen 0 Heap Size; Gen 1 Heap Size; Gen 2 Heap Size and the Large Object Heap Size. This counter indicates the current memory allocated in bytes on the GC Heaps. |
| ncm num gc handles (Table) | This counter displays the current number of GC Handles in use. GCHandles are handles to resources external to the CLR and the managed environment. Handles occupy small amounts of memory in the GCHeap but potentially expensive unmanaged resources. |
| ncm num gen0collections (Table) | This counter displays the number of times the generation 0 objects (youngest; most recently allocated) are garbage collected (Gen 0 GC) since the start of the application. Gen 0 GC occurs when the available memory in generation 0 is not sufficient to satisfy an allocation request. This counter is incremented at the end of a Gen 0 GC. Higher generation GCs include all lower generation GCs. This counter is explicitly incremented when a higher generation (Gen 1 or Gen 2) GC occurs. _Global_ counter value is not accurate and should be ignored. This counter displays the last observed value. |
| ncm num gen1collections (Table) | This counter displays the number of times the generation 1 objects are garbage collected since the start of the application. The counter is incremented at the end of a Gen 1 GC. Higher generation GCs include all lower generation GCs. This counter is explicitly incremented when a higher generation (Gen 2) GC occurs. _Global_ counter value is not accurate and should be ignored. This counter displays the last observed value. |
| ncm num gen2collections (Table) | This counter displays the number of times the generation 2 objects (older) are garbage collected since the start of the application. The counter is incremented at the end of a Gen 2 GC (also called full GC). _Global_ counter value is not accurate and should be ignored. This counter displays the last observed value. |
| ncm num induced gc (Table) | This counter displays the peak number of times a garbage collection was performed because of an explicit call to GC.Collect. Its a good practice to let the GC tune the frequency of its collections. |
| ncm num total committed bytes (Table) | This counter displays the amount of virtual memory (in bytes) currently committed by the Garbage Collector. (Committed memory is the physical memory for which space has been reserved on the disk paging file). |
| ncm num total reserved bytes (Table) | This counter displays the amount of virtual memory (in bytes) currently reserved by the Garbage Collector. (Reserved memory is the virtual memory space reserved for the application but no disk or main memory pages have been used.) |
| ncm num of pinned objects (Table) | This counter displays the number of pinned objects encountered in the last GC. This counter tracks the pinned objects only in the heaps that were garbage collected e.g. a Gen 0 GC would cause enumeration of pinned objects in the generation 0 heap only. A pinned object is one that the Garbage Collector cannot move in memory. |
| ncm num of sink blocks in use (Table) | This counter displays the current number of sync blocks in use. Sync blocks are per-object data structures allocated for storing synchronization information. Sync blocks hold weak references to managed objects and need to be scanned by the Garbage Collector. Sync blocks are not limited to storing synchronization information and can also store COM interop metadata. This counter was designed to indicate performance problems with heavy use of synchronization primitives. |
| ncm percent time in gc (Table) | % Time in GC is the percentage of elapsed time that was spent in performing a garbage collection (GC) since the last GC cycle. This counter is usually an indicator of the work done by the Garbage Collector on behalf of the application to collect and compact memory. This counter is updated only at the end of every GC and the counter value reflects the last observed value; its not an average. |
| ncm allocated bytes per sec (Table) | This counter displays the rate of bytes per second allocated on the GC Heap. This counter is updated at the end of every GC; not at each allocation. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval. |
| ncm finalization survivors (Table) | This counter displays the number of garbage collected objects that survive a collection because they are waiting to be finalized. If these objects hold references to other objects then those objects also survive but are not counted by this counter; the 'Promoted Finalization-Memory from Gen 0' and 'Promoted Finalization-Memory from Gen 1' counters represent all the memory that survived due to finalization. This counter is not a cumulative counter; its updated at the end of every GC with count of the survivors during that particular GC only. This counter was designed to indicate the extra overhead that the application might incur because of finalization. |
| ncm gen0promoted bytes per sec (Table) | This counter displays the bytes per second that are promoted from generation 0 (youngest) to generation 1; objects that are promoted just because they are waiting to be finalized are not included in this counter. Memory is promoted when it survives a garbage collection. This counter was designed as an indicator of relatively long-lived objects being created per sec. This counter displays the difference between the values observed in the last two samples divided by the duration of the sample interval. |
| ncm gen0heap size (Table) | This counter displays the maximum bytes that can be allocated in generation 0 (Gen 0); its does not indicate the current number of bytes allocated in Gen 0. A Gen 0 GC is triggered when the allocations since the last GC exceed this size. The Gen 0 size is tuned by the Garbage Collector and can change during the execution of the application. At the end of a Gen 0 collection the size of the Gen 0 heap is infact 0 bytes; this counter displays the size (in bytes) of allocations that would trigger the next Gen 0 GC. This counter is updated at the end of a GC; its not updated on every allocation. |
| ncm gen1promoted bytes per sec (Table) | This counter displays the bytes per second that are promoted from generation 1 to generation 2 (oldest); objects that are promoted just because they are waiting to be finalized are not included in this counter. Memory is promoted when it survives a garbage collection. Nothing is promoted from generation 2 since it is the oldest. This counter was designed as an indicator of very long-lived objects being created per sec. This counter displays the difference between the values observed in the last two samples divided by the duration of the sample interval. |
| ncm gen1heap size (Table) | This counter displays the current number of bytes in generation 1 (Gen 1); this counter does not display the maximum size of Gen 1. Objects are not directly allocated in this generation; they are promoted from previous Gen 0 GCs. This counter is updated at the end of a GC; its not updated on every allocation. |
| ncm gen2heap size (Table) | This counter displays the current number of bytes in generation 2 (Gen 2). Objects are not directly allocated in this generation; they are promoted from Gen 1 during previous Gen 1 GCs. This counter is updated at the end of a GC; its not updated on every allocation. |
| ncm large object heap size (Table) | This counter displays the current size of the Large Object Heap in bytes. Objects greater than 20 KBytes are treated as large objects by the Garbage Collector and are directly allocated in a special heap; they are not promoted through the generations. This counter is updated at the end of a GC; its not updated on every allocation. |
| ncm promot finalization memory gen0 (Table) | This counter displays the bytes of memory that are promoted from generation 0 to generation 1 just because they are waiting to be finalized. This counter displays the value observed at the end of the last GC; its not a cumulative counter. |
| ncm promot finalization memory gen1 (Table) | This counter displays the bytes of memory that are promoted from generation 1 to generation 2 just because they are waiting to be finalized. This counter displays the value observed at the end of the last GC; its not a cumulative counter. This counter is reset to 0 if the last GC was a Gen 0 GC only. |
| ncm promoted memory from gen0 (Table) | This counter displays the bytes of memory that survive garbage collection (GC) and are promoted from generation 0 to generation 1; objects that are promoted just because they are waiting to be finalized are not included in this counter. This counter displays the value observed at the end of the last GC; its not a cumulative counter. |
| ncm promoted memory from gen1 (Table) | This counter displays the bytes of memory that survive garbage collection (GC) and are promoted from generation 1 to generation 2; objects that are promoted just because they are waiting to be finalized are not included in this counter. This counter displays the value observed at the end of the last GC; its not a cumulative counter. This counter is reset to 0 if the last GC was a Gen 0 GC only. |
Group: "file replica conn"| frc authentications (Table) | The number of successful authentication checks made on packets received from the partner associated with this connection. |
| frc authentications in error (Table) | The cumulative number of authentication check failures detected on packets received from the partner associated with this connection. |
| frc bindings (Table) | The number of successful RPC bind requests to the FRS server on the partner associated with this connection. |
| frc bindings in error (Table) | The cumulative number of unsuccessful RPC bind requests to the FRS server on the partner associated with this connection. |
| frc communication timeouts (Table) | The cumulative number of times a communication request has taken too long to the partner associated with this connection. |
| frc fetch blocks received (Table) | The number of blocks of staging file data received from the partner associated with this connection. The underlying transport may break a block into a smaller number of packets on the wire. |
| frc fetch blocks received in bytes (Table) | The number of bytes of staging file data received from the partner associated with this connection. |
| frc fetch blocks sent (Table) | The number of blocks of staging file data sent to the partner associated with this connection. The underlying transport may break a block into a smaller number of packets on the wire. |
| frc fetch blocks sent in bytes (Table) | The number of bytes of staging file data sent to the partner associated with this connection. |
| frc fetch requests received (Table) | The number of staging files received from the partner associated with this connection. |
| frc fetch requests sent (Table) | The number of staging files requested from the partner associated with this connection. |
| frc inbound change orders dampened (Table) | The number of change orders received from the partner associated with this connection that have been filtered out by the inbound dampening check. |
| frc join notifications received (Table) | The number of partner join notifications received from the partner associated with this connection. |
| frc join notifications sent (Table) | The number of partner join requests (if this is an inbound connection) or ready-to-join notifications (if this is an outbound connection) sent to the partner associated with this connection. |
| frc joins (Table) | The number of successful joins with the partner associated with this connection. |
| frc local change orders sent (Table) | The number of locally originated replication change orders that have been sent to the partner associated with this connection. |
| frc local change orders sent at join (Table) | The number of locally originated replication change orders produced by a partner induced version vector scan that have been sent to the partner associated with this connection. |
| frc outbound change orders dampened (Table) | The number of change orders sent to the partner associated with this connection that have been filtered out by the outbound dampening check and thus were never sent. |
| frc packets sent (Table) | The total number of FRS data and control packets sent to the partner associated with this connection. |
| frc packets sent in bytes (Table) | The total number of FRS data and control bytes sent to the partner associated with this connection. |
| frc packets sent in error (Table) | The cumulative number of FRS data or control packets not sent because of some error condition associated with this connection. |
| frc remote change orders received (Table) | The number of change orders received from the partner associated with this connection that have passed the inbound dampening check. |
| frc remote change orders sent (Table) | The number of replication change orders originating upstream from this member (i.e. remote) that have been sent to the partner associated with this connection. |
| frc unjoins (Table) | The number of unjoins with the partner associated with this connection. |
Group: "file replica set"| frs authentications (Table) | The number of successful authentication checks made on packets received from any partner associated with this replica set member. |
| frs authentications in error (Table) | The cumulative number of authentication check failures detected on packets received from any partner associated with this replica set member. |
| frs bindings (Table) | The number of successful RPC bind requests to the FRS server on any partner associated with this replica set member. |
| frs bindings in error (Table) | The cumulative number of unsuccessful RPC bind requests to the FRS server on any partner associated with this replica set member. |
| frs bytes of files installed (Table) | The total number of bytes of staging file data that have been installed on this replica set member. |
| frs bytes of staging fetched (Table) | The total number of bytes of staging file data received by this replica set member from its inbound partners. |
| frs bytes of staging generated (Table) | The total number of bytes of staging file data generated by this replica set member not including the number of bytes produced as part of regeneration. |
| frs bytes of staging regenerated (Table) | The total number of bytes of staging file data regenerated by this replica set member for a specific outbound partner request. |
| frs chg orders aborted (Table) | The number of local plus remote file updates that were aborted on this replica set member. |
| frs chg orders evaporated (Table) | The number of local file updates that were never processed because the underlying file was deleted first. |
| frs chg orders issued (Table) | The number of local plus remote file updates initiated on this replica set member. |
| frs chg orders morphed (Table) | The number of local plus remote file updates that encountered a name space collision on this replica set member. |
| frs chg orders propagated (Table) | The number of local plus remote file updates that were propagated to the outbound log of this replica set member. The update remains pending in the outbound log until it has been delivered to all outbound partners. |
| frs chg orders received (Table) | The number of local plus remote file updates that have been received by this replica set member. Note that depending on the replication topology it is possible for the same remote file update to be sent from multiple inbound partners. However, only one will send the actual file data. |
| frs chg orders retired (Table) | The number of local plus remote file updates retired on this replica set member. |
| frs chg orders retried (Table) | The number of local plus remote file updates that were retried for any reason on this replica set member. |
| frs chg orders retried fetch (Table) | The number of local plus remote file updates that were retried due to a stage file fetch problem on this replica set member. |
| frs chg orders retried generate (Table) | The number of local plus remote file updates that were retried due to a stage file generation problem on this replica set member. |
| frs chg orders retried install (Table) | The number of local plus remote file updates that were retried due to a stage file install problem on this replica set member. Most likely caused by a sharing conflict trying to access the target file or directory. |
| frs chg orders retried rename (Table) | The number of local plus remote file updates that were retried due to a problem during the final target file rename or delete operation on this replica set member. Most likely caused by a sharing conflict trying to access the target file or directory. |
| frs chg orders sent (Table) | The number of local plus remote file updates that have been sent to the outbound partners of this replica set member. |
| frs communication timeouts (Table) | The cumulative number of FRS data or control packets not sent to an outbound partner because the send request timed out. |
| frsdsbindings (Table) | The number of times FRS has attempted to acquire a binding handle to the active directory. |
| frsdsbindings in error (Table) | The cumulative number of attempts to acquire a binding handle to the active directory that failed with some error status. |
| frsdsobjects (Table) | The number of FRS configuration Objects retreived from the directory service. |
| frsdsobjects in error (Table) | The cumulative count of FRS configuration objects retreived from the directory service that were missing either the distinguished name, object GUID or the relative distinguished name attributes. |
| frsdspolls (Table) | The number of times FRS has polled the active directory for FRS configuration information on this computer. |
| frsdspolls with chgs (Table) | The number of times FRS has polled the active directory for FRS configuration information and configuration changes were found. |
| frsdspolls without chgs (Table) | The number of times FRS has polled the active directory for FRS configuration information and no configuration changes were found. |
| frsdssearches (Table) | The number of times FRS has made a search request to the active directory. |
| frsdssearches in error (Table) | The cumulative number of times FRS has made a search request to the active directory and the request returned with an error condition. |
| frs fetch blocks received (Table) | The number of blocks of staging file data received from all inbound partners associated with this replica set member. The underlying transport may break a block into a smaller number of packets on the wire. |
| frs fetch blocks received in bytes (Table) | The total number of bytes of staging file data received by this replica set member from all inbound partners. |
| frs fetch blocks sent (Table) | The number of blocks of staging file data sent to any outbound partner associated with this replica set member. The underlying transport may break a block into a smaller number of packets on the wire. |
| frs fetch blocks sent in bytes (Table) | The total number of bytes of staging file data sent to the outbound partners of this replica set member. |
| frs fetch requests received (Table) | The number of staging files received from all inbound partners associated with this replica set member. |
| frs fetch requests sent (Table) | The number of staging files requested from any inbound partner associated with this replica set member. |
| frs files installed (Table) | The number of file updates and deletes performed on this replica set member. |
| frs files installed with error (Table) | The cumulative number of file updates that were aborted because of some non-recoverable error. |
| frs inbound chg orders dampened (Table) | The number of remotely originated file updates that were dampened because the update was already delivered by another member. |
| frs join notifications received (Table) | The number of partner join notifications received from all inbound partners associated with this replica set member. |
| frs join notifications sent (Table) | The number of inbound partner join requests or outbound partner ready-to-join notifications sent to all partners associated with this replica set member. |
| frs joins (Table) | The number of successful joins with any partner associated with this replica set member. |
| frskbof staging space free (Table) | The amount of staging space (in Kilobyte units) currently available within the staging space limit. Note that there may not actually be this amount of free space left on the staging volume. |
| frskbof staging space in use (Table) | The amount of staging space (in Kilobyte units) currently in use. |
| frs local chg orders aborted (Table) | The number of locally originated file updates that were aborted. Most likely because a file was deleted before a change to it could be propagated so no stage file could be generated. |
| frs local chg orders issued (Table) | The number of locally originated file updates initiated on this replica set member. |
| frs local chg orders morphed (Table) | The number of locally originated file updates that encountered a name space collision on this replica set member. Most likely caused by the reanimation of a parent dir. |
| frs local chg orders propagated (Table) | The number of locally originated file updates that were propagated to the outbound log of this replica set member. The update remains pending in the outbound log until it has been delivered to all outbound partners. |
| frs local chg orders retired (Table) | The number of locally originated file updates retired on this replica set member. |
| frs local chg orders retried (Table) | The number of locally originated file updates that were retried for any reason on this replica set member. |
| frs local chg orders retried fetch (Table) | The number of locally originated file updates that were retried due to a stage file fetch problem on this replica set member. |
| frs local chg orders retried generate (Table) | The number of locally originated file updates that were retried due to a stage file generation problem on this replica set member. Most likely caused by a sharing conflict trying to access the target file. |
| frs local chg orders retried install (Table) | The number of locally originated file updates that were retried due to a stage file install problem on this replica set member. Most likely caused by a sharing conflict trying to access the target file or directory. |
| frs local chg orders retried rename (Table) | The number of locally originated file updates that were retried due to a problem during the final target file rename or delete operation on this replica set member. Most likely caused by a sharing conflict trying to access the target file or directory. |
| frs local chg orders sent (Table) | The number of locally originated file updates that have been sent to the outbound partners of this replica set member. |
| frs local chg orders sent join (Table) | The number of locally originated file updates which were created by a partner induced version vector scan that have been sent to the outbound partners of this replica set member. |
| frs outbound chg orders dampened (Table) | The number of pending outbound file updates that were dampened because the outbound partner has already received it from another source. |
| frs packets received (Table) | The number of FRS data or control packets (RPC calls) received by FRS. |
| frs packets received in bytes (Table) | The total number of FRS data and control bytes received by all replica sets on this computer. |
| frs packets received in error (Table) | The cumulative number of FRS data or control packets received that were out of rev or otherwise malformed. |
| frs packets sent (Table) | The number of FRS data and control packets sent to all outbound partners associated with this replica set member. |
| frs packets sent in bytes (Table) | The total number of FRS data and control bytes sent by this replica set member to other members. |
| frs packets sent in error (Table) | The cumulative number of FRS data or control packets not sent to an outbound partner because of some error condition. |
| frs remote chg orders aborted (Table) | The number of remotely originated file updates that were aborted. Most likely because of an attempt to fetch a staging file from an inbound partner and the partner no longer has the file because it has been deleted. |
| frs remote chg orders issued (Table) | The number of remotely originated file updates initiated on this replica set member. |
| frs remote chg orders morphed (Table) | The number of remotely originated file updates that encountered a name space collision on this replica set member. Most likely caused by simultaneous create of a file or directory with the same name on more than one replica set member. |
| frs remote chg orders propagated (Table) | The number of remotely originated file updates that were propagated to the outbound log of this replica set member. The update remains pending in the outbound log until it has been delivered to all outbound partners. |
| frs remote chg orders received (Table) | The number of remotely originated file updates that have been received by this replica set member. Note that depending on the replication topology it is possible for the same file update to be sent from multiple inbound partners. However, only one will send the actual file data. |
| frs remote chg orders retired (Table) | The number of remotely originated file updates retired on this replica set member. |
| frs remote chg orders retried (Table) | The number of remotely originated file updates that were retried for any reason on this replica set member. |
| frs remote chg orders retried fetch (Table) | The number of remotely originated file updates that were retried due to a stage file fetch problem on this replica set member. |
| frs remote chg orders retried generat (Table) | The number of remotely originated file updates that were retried due to a stage file generation problem on this replica set member. |
| frs remote chg orders retried install (Table) | The number of remotely originated file updates that were retried due to a stage file install problem on this replica set member. Most likely caused by a sharing conflict trying to access the target file or directory. |
| frs remote chg orders retried rename (Table) | The number of remotely originated file updates that were retried due to a problem during the final target file rename or delete operation on this replica set member. Most likely caused by a sharing conflict trying to access the target file or directory. |
| frs remote chg orders sent (Table) | The number of remotely originated file updates that have been sent to the outbound partners of this replica set member. |
| frs replica sets created (Table) | The cumulative number of replica sets to which this computer has been added as a member. |
| frs replica sets deleted (Table) | The cumulative number of replica sets from which this computer's membership has been provisionally deleted, but could still be reanimated. |
| frs replica sets removed (Table) | The cumulative number of replica sets from which this computer's membership has been permanently deleted. |
| frs replica sets started (Table) | The number of replica sets for which processing has been started. |
| frs staging files fetched (Table) | The number of staging files requested by this replica set member. |
| frs staging files generated (Table) | The number of staging files generated by this replica set member. |
| frs staging files generated with err (Table) | The cumulative number of staging files generated by this replica set member where an error was detected during generation. |
| frs staging files regenerated (Table) | The number of staging files regenerated by this replica set member for a specific outbound partner request. |
| frs threads exited (Table) | The number of execution threads that have terminated. |
| frs threads started (Table) | The number of new execution threads started. |
| frs unjoins (Table) | The number of unjoins with any partner associated with this replica set member. |
| frs usn reads (Table) | The number of times FRS has initiated a read on the NTFRS change log. Each volume has its own change log. |
| frs usn records accepted (Table) | The number of NTFS change log records accepted by FRS for further processing. |
| frs usn records examined (Table) | The number of NTFS change log records examined by FRS. |
| frs usn records rejected (Table) | The number of NTFS change log records skipped by FRS. Most likely because the change log record was for a file not part of any active replica set. |
Group: "gateway service for net ware"| nw bytes received per sec | Bytes Received/sec is the rate of bytes coming in to the Redirector from the network. It includes all application data as well as network protocol information (such as packet headers). |
| nw bytes total per sec | Bytes Total/sec is the rate the Redirector is processing data bytes. This includes all application and file data in addition to protocol information such as packet headers. |
| nw bytes transmitted per sec | Bytes Transmitted/sec is the rate at which bytes are leaving the Redirector to the network. It includes all application data as well as network protocol information (such as packet headers and the like). |
| nw connect net ware 2x | Connect NetWare 2.x counts connections to NetWare 2.x servers. |
| nw connect net ware 3x | Connect NetWare 3.x counts connections to NetWare 3.x servers. |
| nw connect net ware 4x | Connect NetWare 4.x counts connections to NetWare 4.x servers. |
| nw file data operations per sec | File Data Operations/sec is the rate the Redirector is processing data operations. One operation includes (hopefully) many bytes. We say hopefully here because each operation has overhead. You can determine the efficiency of this path by dividing the Bytes/sec by this counter to determine the average number of bytes transferred/operation. |
| nw file read operations per sec | File Read Operations/sec is the rate at which applications are asking the Redirector for data. Each call to a file system or similar Application Program Interface (API) call counts as one operation. |
| nw file write operations per sec | File Write Operations/sec is the rate at which applications are sending data to the Redirector. Each call to a file system or similar Application Program Interface (API) call counts as one operation. |
| nw packet burst io per sec | Packet Burst IO/sec is the sum of Packet Burst Read NCPs/sec and Packet Burst Write NCPs/sec. |
| nw packet burst read ncp count per sec | Packet Burst Read NCP Count/sec is the rate of NetWare Core Protocol requests for Packet Burst Read. Packet Burst is a windowing protocol that improves performance. |
| nw packet burst read timeouts per sec | Packet Burst Read Timeouts/sec is the rate the NetWare Service needs to retransmit a Burst Read Request because the NetWare server took too long to respond. |
| nw packet burst write ncp count per sec | Packet Burst Write NCP Count/sec is the rate of NetWare Core Protocol requests for Packet Burst Write. Packet Burst is a windowing protocol that improves performance. |
| nw packet burst write timeouts per sec | Packet Burst Write Timeouts/sec is the rate the NetWare Service needs to retransmit a Burst Write Request because the NetWare server took too long to respond. |
| nw packets received per sec | Packets Received/sec is the rate at which the Redirector is receiving packets (also called SMBs or Server Message Blocks). Network transmissions are divided into packets. The average number of bytes received in a packet can be obtained by dividing Bytes Received/sec by this counter. Some packets received might not contain incoming data, for example an acknowledgment to a write made by the Redirector would count as an incoming packet. |
| nw packets transmitted per sec | Packets Transmitted/sec is the rate at which the Redirector is sending packets (also called SMBs or Server Message Blocks). Network transmissions are divided into packets. The average number of bytes transmitted in a packet can be obtained by dividing Bytes Transmitted/sec by this counter. |
| nw packets per sec | Packets/sec is the rate the Redirector is processing data packets. One packet includes (hopefully) many bytes. We say hopefully here because each packet has protocol overhead. You can determine the efficiency of this path by dividing the Bytes/sec by this counter to determine the average number of bytes transferred/packet. You can also divide this counter by Operations/sec to determine the average number of packets per operation, another measure of efficiency. |
| nw read operations random per sec | Read Operations Random/sec counts the rate at which, on a file-by-file basis, reads are made that are not sequential. If a read is made using a particular file handle, and then is followed by another read that is not immediately the contiguous next byte, this counter is incremented by one. |
| nw read packets per sec | Read Packets/sec is the rate at which read packets are being placed on the network. Each time a single packet is sent with a request to read data remotely, this counter is incremented by one. |
| nw server disconnects | Server Disconnects counts the number of times a Server has disconnected your Redirector. See also Server Reconnects. |
| nw server reconnects | Server Reconnects counts the number of times your Redirector has had to reconnect to a server in order to complete a new active request. You can be disconnected by the Server if you remain inactive for too long. Locally even if all your remote files are closed, the Redirector will keep your connections intact for (nominally) ten minutes. Such inactive connections are called Dormant Connections. Reconnecting is expensive in time. |
| nw server sessions | Server Sessions counts the total number of security objects the Redirector has managed. For example, a logon to a server followed by a network access to the same server will establish one connection, but two sessions. |
| nw write operations random per sec | Write Operations Random/sec is the rate at which, on a file-by-file basis, writes are made that are not sequential. If a write is made using a particular file handle, and then is followed by another write that is not immediately the next contiguous byte, this counter is incremented by one. |
| nw write packets per sec | Write Packets/sec is the rate at which writes are being sent to the network. Each time a single packet is sent with a request to write remote data, this counter is incremented by one. |
Group: "ias accounting clients"| icc accounting requests (Table) | Shows the number of packets received from this client on the accounting port. |
| icc accounting requests per sec (Table) | Shows the rate, in seconds, at which packets were received from this client on the accounting port. |
| icc accounting responses (Table) | Shows the number of RADIUS Accounting-Response packets sent to this client. |
| icc accounting responses per sec (Table) | Shows the rate in seconds at which duplicate RADIUS Accounting-Request packets were received from this client. |
| icc bad authenticators (Table) | Shows the number of packets that contained invalid Signature attributes. |
| icc bad authenticators per sec (Table) | Shows the rate, in seconds, at which packets that contained invalid Signature attributes were received. |
| icc dropped packets (Table) | Shows the number of incoming packets silently discarded for a reason other than being malformed, bad authenticators, or unknown types. |
| icc dropped packets per sec (Table) | Shows the rate in seconds at which incoming packets were silently discarded for a reason other than being malformed, bad authenticators, or unknown types. |
| icc duplicate accounting requests (Table) | Shows the number of duplicate RADIUS Accounting-Request packets received from this client. |
| icc duplicate accounting rqst per sec (Table) | Shows the rate, in seconds, at which duplicate RADIUS Accounting-Request packets were received from this client. |
| icc malformed packets (Table) | Shows the number of malformed packets received. Bad authenticators or unknown types are not included. |
| icc malformed packets per sec (Table) | Shows the rate, in seconds, at which malformed packets were received. |
| icc no record (Table) | Shows the number of RADIUS Accounting-Request packets that were received and responded to but not recorded. |
| icc no record per sec (Table) | Shows the rate, in seconds, at which RADIUS Accounting-Request packets were received and responded to but not recorded. |
| icc packets received (Table) | Shows the number of packets received. |
| icc packets received per sec (Table) | Shows the rate, in seconds, at which packets were received. |
| icc packets sent (Table) | Shows the number of packets sent. |
| icc packets sent per sec (Table) | Shows the rate, in seconds, at which packets were sent. |
| icc unknown type (Table) | Shows the number of packets of unknown type that were received. An unknown type is a RADIUS packet that contains an unrecognized entry in the Code field, used to identify the packet type. Consequently IAS does not support packets of unknown type. |
| icc unknown type per sec (Table) | Shows the rate, in seconds, at which packets of unknown type were received. |
