Cisco Unified Real-Time Monitoring Tool Administration Guide for Cisco Unified Contact Center Express and Cisco Unified IP IVR Release 9.0(1)
System performance objects and counters
Downloads: This chapterpdf (PDF - 541.0KB) The complete bookPDF (PDF - 2.35MB) | Feedback

System performance objects and counters

System performance objects and counters

This appendix contains the following sections:

Cisco Tomcat Connector

The Tomcat Hypertext Transport Protocol (HTTP)/HTTP Secure (HTTPS) Connector object provides information about Tomcat connectors. A Tomcat HTTP connector represents an endpoint that receives requests and sends responses. The connector handles HTTP/HTTPS requests and sends HTTP/HTTPS responses that occur when Unified CCX web pages get accessed. The Secure Socket Layer (SSL) status of web application URLs provides the basis for the instance name for each Tomcat HTTP Connector. For example, https://<IP Address>:8443 for SSL or http://<IP Address>:8080 for non-SSL. The following table contains information on the Tomcat HTTP connector counters.

Table 1 Cisco Tomcat Connector

Counters

Counter Description

Errors

This counter represents the total number of HTTP errors (for example, 401 Unauthorized) that the connector encountered. A Tomcat HTTP connector represents an endpoint that receives requests and sends responses. The connector handles HTTP/HTTPS requests and sends HTTP/HTTPS responses that occur when Unified CCX-related windows are accessed. The Secure Socket Layer (SSL) status of the URLs for the web application provides basis for the instance name for each Tomcat HTTP connector. For example, https://<IP Address>:8443 for SSL or http://<IP Address>:8080 for non-SSL.

MBytesReceived

This counter represents the amount of data that the connector received. A Tomcat HTTP connector represents an endpoint that receives requests and sends responses. The connector handles HTTP/HTTPS requests and sends HTTP/HTTPS responses that occur when Unified CCX-related windows are accessed. The Secure Socket Layer (SSL) status of the URLs for the web application provides basis for the instance name for each Tomcat HTTP connector. For example, https://<IP Address>:8443 for SSL or http://<IP Address>:8080 for non-SSL.

MBytesSent

This counter represents the amount of data that the connector sent. A Tomcat HTTP connector represents an endpoint that receives requests and sends responses. The connector handles HTTP/HTTPS requests and sends HTTP/HTTPS responses that occur when Unified CCX-related windows are accessed. The Secure Socket Layer (SSL) status of the URLs for the web application provides basis for the instance name for each Tomcat HTTP connector. For example, https://<IP Address>:8443 for SSL or http://<IP Address>:8080 for non-SSL.

Requests

This counter represents the total number of request that the connector handled. A Tomcat HTTP connector represents an endpoint that receives requests and sends responses. The connector handles HTTP/HTTPS requests and sends HTTP/HTTPS responses that occur when Unified CCX-related windows are accessed. The Secure Socket Layer (SSL) status of the URLs for the web application provides basis for the instance name for each Tomcat HTTP connector. For example, https://<IP Address>:8443 for SSL or http://<IP Address>:8080 for non-SSL.

ThreadsTotal

This counter represents the current total number of request processing threads, including available and in-use threads, for the connector. A Tomcat HTTP connector represents an endpoint that receives requests and sends responses. The connector handles HTTP/HTTPS requests and sends HTTP/HTTPS responses that occur when Unified CCX-related windows are accessed. The Secure Socket Layer (SSL) status of the URLs for the web application provides basis for the instance name for each Tomcat HTTP connector. For example, https://<IP Address>:8443 for SSL or http://<IP Address>:8080 for non-SSL.

ThreadsMax

This counter represents the maximum number of request processing threads for the connector. Each incoming request on a Unified CCX-related window requires a thread for the duration of that request. If more simultaneous requests are received than the currently available request processing threads can handle, additional threads will be created up to the configured maximum shown in this counter. If still more simultaneous requests are received, they accumulate within the server socket that the connector created, up to an internally specified maximum number. Any further simultaneous requests will receive connection refused messages until resources are available to process them.

A Tomcat HTTP connector represents an endpoint that receives requests and sends responses. The connector handles HTTP/HTTPS requests and sends HTTP/HTTPS responses that occur when Unified CCX-related windows are accessed. The Secure Socket Layer (SSL) status of the URLs for the web application provides basis for the instance name for each Tomcat HTTP connector. For example, https://<IP Address>:8443 for SSL or http://<IP Address>:8080 for non-SSL.

ThreadsBusy

This counter represents the current number of busy/in-use request processing threads for the connector. A Tomcat Connector represents an endpoint that receives requests and sends responses. The connector handles HTTP/HTTPS requests and sends HTTP/HTTPS responses that occur when web pages that are related to Unified CCX are accessed. The Secure Sockets Layer (SSL) status of the URLs for the web application provides the basis for the instance name for each Tomcat connector. For example, https://<IP Address>:8443 for SSL or http://<IP Address>:8080 for non-SSL.

Cisco Tomcat JVM

The Cisco Tomcat Java Virtual Machine (JVM) object provides information about the pool of common resource memory used by Unified CCX applications such as Cisco Unified CCX Administration and Cisco Unified Serviceability. The following table contains information on the Tomcat JVM counters.

Table 2 Tomcat JVM

Counters

Counter Description

KBytesMemoryFree

This counter represents the amount of free dynamic memory block (heap memory) in the Tomcat Java Virtual Machine. The dynamic memory block stores all objects that Tomcat and its web applications such as Cisco Unified CCX Administration and Cisco Unified Serviceability create. When the amount of free dynamic memory is low, more memory gets automatically allocated, and total memory size (represented by the KbytesMemoryTotal counter) increases but only up to the maximum (represented by the KbytesMemoryMax counter). You can determine the amount of memory in use by subtracting KBytesMemoryFree from KbytesMemoryTotal.

KBytesMemoryMax

This counter represents the amount of free dynamic memory block (heap memory) in the Tomcat Java Virtual Machine. The dynamic memory block stores all objects that Tomcat and its web applications such as Cisco Unified CCX Administration and Cisco Unified Serviceability create.

KBytesMemoryTotal

This counter represents the current total dynamic memory block size, including free and in-use memory, of Tomcat Java Virtual Machine. The dynamic memory block stores all objects that Tomcat and its web applications such as Cisco Unified CCX Administration and Cisco Unified Serviceability create.

Cisco Tomcat Web Application

The Cisco Tomcat Web Application object provides information about how to run Unified CCX web applications. The URLs for the web application provide basis for the instance name for each Tomcat Web Application. For example, Cisco Unified CCX Administration (https://<IP Address>:8443/appadmin) gets identified by appadmin, Cisco Unified Serviceability gets identified by ccmservice, Unified CCX Serviceability gets identified by uccxservice, and URLs that do not have an extension, such as https://<IP Address>:8443 or http://<IP Address>:8080), get identified by _root. The following table contains information on the Tomcat Web Application counters.

Table 3 Tomcat Web Application

Counters

Counter Description

Errors

This counter represents the total number of HTTP errors (for example, 401 Unauthorized) that a Unified CCX-related web application encountered. The URLs for the web application provide the basis instance name for each Tomcat Web Application. For example, Unified CCX Administration (https://<IP Address>:8443/appadmin) gets identified by appadmin, Cisco Unified Serviceability gets identified by ccmservice, Unified CCX Serviceability gets identified by uccxservice, and URLs that do not have an extension, such as https://<IP Address>:8443 or http://<IP Address>:8080), get identified by _root.

Requests

This counter represents the total number of requests that the web application handles. Each time that a web application is accessed, its Requests counter increments accordingly. The URLs for the web application provide the basis instance name for each Tomcat Web Application. For example, Unified CCX Administration (https://<IP Address>:8443/appadmin) gets identified by appadmin, Cisco Unified Serviceability gets identified by ccmservice, Unified CCX Serviceability gets identified by uccxservice, and URLs that do not have an extension, such as https://<IP Address>:8443 or http://<IP Address>:8080), get identified by _root.

SessionsActive

This counter represents the number of sessions that the web application currently has active (in use). The URLs for the web application provide the basis instance name for each Tomcat Web Application. For example, Unified CCX Administration (https://<IP Address>:8443/appadmin) gets identified by appadmin, Cisco Unified Serviceability gets identified by ccmservice, Unified CCX Serviceability gets identified by uccxservice, and URLs that do not have an extension, such as https://<IP Address>:8443 or http://<IP Address>:8080), get identified by _root.

Database Change Notification Client

The Database Change Notification Client object provides information on change notification clients. The following table contains information on the Database Change Notification Client counters.

Table 4 Database Change Notification Client

Counters

Counter Descriptions

MessagesProcessed

This counter represents the number of database change notifications that have been processed. This counter refreshes every 15 seconds.

MessagesProcessing

This counter represents the number of change notification messages that are currently being processed or are waiting to be processed in the change notification queue for this client. This counter refreshes every 15 seconds.

QueueHeadPointer

This counter represents the head pointer to the change notification queue. The head pointer acts as the starting point in the change notification queue. To determine the number of notifications in the queue, subtract the head pointer value from the tail pointer value. By default, this counter refreshes every 15 seconds.

QueueMax

This counter represents the largest number of change notification messages that will be processed for this client. This counter remains cumulative since the last restart of the Cisco Database Layer Monitor service.

QueueTailPointer

This counter represents the tail pointer to the change notification queue. The tail pointer represents the ending point in the change notification queue. To determine the number of notifications in the queue, subtract the head pointer value from the tail pointer value. By default, this counter refreshes every 15 seconds

TablesSubscribed

This counter represents the number of tables in which this client has subscribed.

Database Change Notification Server

The Database Change Notification Server object provides information on different change-notification-related statistics. This table contains information on the Database Change Notification Server counters.

Table 5 Database Change Notification Server

Counter

Counter Descriptions

Clients

This counter represents the number of change notification clients (services/servlets) that have subscribed for change notification.

Queue Delay

This counter provides the number of seconds that the change notification process has messages to process but is not processing them. This condition is true if:

  • either Change Notification Requests Queued in Database (QueuedRequestsInDB) and Change Notification Requests Queued in Memory (QueuedRequestsInMemory) are non-zero, or
  • the Latest Change Notification Messages Processed count is not changing.

This condition gets checked every 15 seconds.

QueuedRequestsInDB

This counter represents the number of change notification records that are in the DBCNQueue (Database Change Notification Queue) table via direct TCP/IP connection (not queued in shared memory). This counter refreshes every 15 seconds.

QueuedRequestsInMemory

This counter represents the number of change notification requests that are queued in shared memory.

Database Change Notification Subscription

The Database Change Notification Subscription object displays the names of tables where the client will receive Change Notifications.

The SubscribedTable object displays the table with the service or servlet that will receive change notifications. Because the counter does not increment, this display occurs for informational purposes only.

DB Local_DSN

The Database Local Data Source Name (DSN) object and LocalDSN counter provide the DSN information for the local machine. The following table contains information on the Database local DSN.

Table 6 Database Local Data Source Name

Counters

Counter Descriptions

CcmDbSpace_Used

This counter represents the amount of Ccm DbSpace that is being consumed

CcmtempDbSpace_Used

This counter represents the amount of Ccmtemp DbSpace that is being consumed.

CNDbSpace_Used

This counter represents the percentage of CN dbspace consumed.

LocalDSN

This counter represents the data source name (DSN) that is being referenced from the local machine.

SharedMemory_Free

This counter represents total shared memory that is free.

SharedMemory_Used

This counter total shared memory that is used.

RootDbSpace_Used

This counter represents the amount of RootDbSpace that is being consumed.

DB User Host Information Counters

The DB User Host Information object provides information on DB User Host.

The DB:User:Host Instance object displays the number of connections that are present for each instance of DB:User:Host.

DBPerformance Info

Table 7 DBPerformance Info

Counter

Description

CuicDbSpace_Used

The amount of CUIC dbspace consumed.

CuicSbSpace_Used

The amount of CUIC Blob Space consumed.

CuicTempDbSpace_Used

The amount of CUIC Temp dbspace consumed.

RootDbSpace_Used

The amount of root dbspace consumed.

Enterprise Replication DBSpace Monitors

The enterprise replication DBSpace monitors object displays the usage of various ER DbSpaces. The following table contains information on the enterprise replication DB monitors.

Table 8 Enterprise replication DBSpace monitors

Counters

Counter Descriptions

ERDbSpace_Used

This counter represents the amount of enterprise replication DbSpace that was consumed.

ERSBDbSpace_Used

This counter represents the amount of ERDbSpace that was consumed.

Enterprise Replication Perfmon Counters

The Enterprise Replication Perfmon Counter object provides information on the various replication counters.

The ServerName:ReplicationQueueDepth counter displays the server name followed by the replication queue depth.

Intelligence Center JVM Statistics

Table 9 Intelligence Center JVM Statistics

Counter

Description

EnvMaxThreadsUsed

The real-time maximum threads used object is a real-time snapshot metric indicating the peak amount of threads used simultaneously in the runtime environment since startup. The maximum number of threads used by the runtime environment includes all Cisco Intelligence Center standalone and thread pool threads as well as threads created by the web application server running within the same runtime environment

EnvRtCommitMemUsed

The real-time current memory used object is a real-time snapshot metric indicating the memory committed by the runtime environment. This memory is guranteed to be available to the runtime environment. This can change dynamically over time but is never less than EnvRtCurrMemUsed. The object value is expressed as a count of Mega bytes

EnvRtCurrMemAvail

The real-time current memory available object is a real-time snapshot metric indicating the amount of system memory not being used. The object value is expressed as a count of Mega bytes and indicates the amount of current system memory that is not currently being used.

EnvRtCurrMemUsed

The real-time current memory used object is a real-time snapshot metric indicating the current memory usage by the runtime environment. The object value is expressed as a count of Mega bytes and indicates the current amount of memory used by this runtime environment.

EnvRtCurrThreadsInUse

The real-time current threads in use object is a real-time snapshot metric indicating a count of threads that are in use in the runtime environment. The number of threads in use by the runtime environment include all of the Cisco Intelligence Center standalone and thread pool threads as well as those threads created by the web application server running within the same runtime environment.

EnvRtMaxMemAvail

The real-time maximum memory available object is a real-time snapshot metric indicating the maximum amount of System memory available. The object value is expresses as a count of Mega bytes

EnvRtMaxMemUsed

The real-time maximum memory used object is a real-time snapshot metric indicating the peak memory allocated to the runtime environment. The object value is expressed as a count of Mega bytes and indicates the high water mark of memory that can be used bye the runtime environment

EnvRtUpTime

The real-time up time object is a real-time snapshot metric indicating how long the Cisco Intelligence Center application has been running. The object value is expressed as a count of milliseconds that have elapsed since the application began executing

Intelligence Center System Condition Table

Table 10 Intelligence Center System Condition Table

Counter

Description

CUIC_DATASOURCE_UNAVAILABLE

This counter is no longer valid with the counter value -1. It has been rendered obsolete by the Await Write Time counter.

CUIC_DB_REPLICATION_FAILED

Database replication failed

CUIC_LICENSE_EXPIRED

Unified IC Application license has expired

CUIC_REPORT_ EXECUTION_FAILED

Could not run the report. Could be because associated datasource is offline

CUIC_SERVICE_UNAVAILABLE

Service going down

Infrastructure_DEADLOCK_DETECTED

A deadlock between two or more application threads has been detected. This is an unrecoverable error and the server must be restarted. Detailed information about the deadlock can be found in the logs.

Infrastructure_LICENSE_EXPIRED

There is an expired feature in the license file.

Infrastructure_LICENSE_EXPIRING

There is a feature in the license file that will expire within the next 14 days

Infrastructure_LICENSE_NO_LICENSE

No license file was loaded. Using default evaluation license.

Infrastructure_LICENSE_PROBLEM

There is an error in the license file.

Infrastructure_LOG_PURGER_ERROR

An error occurred while log files were being purged.

Infrastructure_PERSISTENT_STORE_SIZE_ALMOST_FULL

The message store that persists reporting data during a connection loss is approaching capacity. If it fills completely, reporting data will be lost.

Infrastructure_PERSISTENT_STORE_SIZE_FULL

The message store that persists reporting data during a connection loss is at capacity. Reporting data will be lost until the connection with the reporting server is restored.

Infrastructure_PERSISTENT_STORE_SIZE_WARN

: The message store that persists reporting data during a connection loss is more than half full. If it fills completely, reporting data will be lost.

Infrastructure_PORT_SECURITY_MANAGER_ERROR_LOADING

Error manipulating PortSecurityManager firewall rules

Infrastructure_SC_JMX_CONFIGURATION_ERROR

There is a configuration problem with JMX ports

Infrastructure_SERVER_NOT_READY

The Server state is not ready

Infrastructure_SNMP_CONNECTION_ERROR

The connection to SNMP Subagent Failed.

Infrastructure_SOFTWARE_CONFIGURATION_ERROR

There is an error in the files configuring the software on the disk.

Infrastructure_SUBSYSTEM_HEARTBEAT_FAILED

Heartbeats from one or more subsystems have stopped.

Infrastructure_SUBSYSTEM_START_FAILURE

One or more subsystems failed to start.

Infrastructure_SUBSYSTEM_STOP_FAILURE

One or more subsystems failed to stop.

Infrastructure_SYSTEM_SHUT_DOWN

One or more subsystems failed to stop.

RS_CONFIG_UNAVAILABLE

System detected critical error accessing configuration

RS_DATABASE_UNAVAILABLE

System detected critical error with database

RS_MAINTENANCE_IN_PROGRESS

System has detected maintenance in progress on Reporting Server

RS_SYSTEM_THRESHOLD_REACHED

System has detected a critical system threshold reached on Reporting Server

RS_UNRECOVERABLE_ERROR

System has detected an internal error within Reporting Server which may prevent it from functioning correctly. Restart may be required.

Intelligence Center Thread Pool Section

Table 11 Intelligence Center Thread Pool Section

Counter

Description

Active Thread Count

Number of threads currently executing a task.

Core Pool Size

Minimum number of threads the thread pool is configured to have.

Largest Pool Size

The largest number of threads that have ever simultaneously been in the pool.

Maximum Pool Size

Maximum number of threads to which the thread pool can grow.

Pool Size

Number of currently available threads. Calculated from (total pool size) - (number of active threads)

Task Queue Size

The number of tasks currently queued for execution waiting for a thread.

Intelligence Center Tomcat Connector

A Tomcat Connector represents an endpoint that receives requests and sends responses. The Connector handles HTTP/HTTPS requests and sends HTTP/HTTPS responses that occur when CUIC-related web pages are accessed. The instance name for each Tomcat Connector is based on the Secure Sockets Layer (SSL) status of the URLs for the web application. For example, https://IP Address:8443 for SSL or http://IP Address:8081 for non-SSL.

Table 12 Intelligence Center Tomcat Connector

Counter

Description

BytesReceived

This counter represents the amount of data that the Connector has received.

BytesSent

This counter represents the amount of data that the Connector has sent.

Errors

This counter represents the total number of HTTP errors (for example, 401 Unauthorized ) encountered by the Connector.

Requests

This counter represents the total number of requests that have been handled by the Connector.

ThreadsBusy

This counter represents the Connector's current number of busy/in-use request processing threads.

ThreadsMax

This counter represents the Connector's maximum number of request processing threads. Each incoming request on a Cisco CallManager-related web page requires a thread for the duration of that request. If more simultaneous requests are received than can be handled by the currently available request processing threads, additional threads will be created up to the configured maximum shown in this counter. If still more simultaneous requests are received, they accumulate within the server socket created by the Connector, up to an internally-specified maximum. Any further simultaneous requests will receive Connection Refused errors until resources are available to process them.

ThreadsTotal

This counter represents the Connector's current total number of request processing threads, including available and in-use threads.

IP

The IP object provides information on the IPv4-related statistics on your system. The following table contains information on the IP counters.

Table 13 IP

Counters

Counter Descriptions

Frag Creates

This counter represents the number of IP datagrams fragments that have been generated at this entity.

Frag Fails

This counter represents the number of IP datagrams that were discarded at this entity because the datagrams could not be fragmented, such as datagrams where the Do not Fragment flag was set.

Frag OKs

This counter represents the number of IP datagrams that were successfully fragmented at this entity.

In Delivers

This counter represents the number of input datagrams that were delivered to IP user protocols. This includes Internet Control Message Protocol (ICMP).

In Discards

This counter represents the number of input IP datagrams where no problems were encountered, but which were discarded. Lack of buffer space provides one possible reason. This counter does not include any datagrams that were discarded while awaiting reassembly.

In HdrErrors

This counter represents the number of input datagrams that were discarded with header errors. This includes bad checksums, version number mismatch, other format errors, time-to-live exceeded, and other errors that were discovered in processing their IP options.

In Receives

This counter represents the number of input datagrams that were received from all network interfaces. This counter includes datagrams that were received with errors

In UnknownProtos

This counter represents the number of locally addressed datagrams that were received successfully but discarded because of an unknown or unsupported protocol.

InOut Requests

This counter represents the number of incoming IP datagrams that were received and the number of outgoing IP datagrams that were sent.

Out Discards

This counter represents the number of output IP datagrams that were not transmitted and were discarded. Lack of buffer space provides one possible reason.

Out Requests

This counter represents the total number of IP datagrams that local IP user-protocols (including ICMP) supply to IP in requests transmission. This counter does not include any datagrams that were counted in ForwDatagrams.

Reasm Fails

This counter represents the number of IP reassembly failures that the IP reassembly algorithm detected, including time outs, errors, and so on. This counter does not represent the discarded IP fragments because some algorithms, such as the algorithm in RFC 815, can lose track of the number of fragments because it combines them as they are received.

Reasm OKs

This counter represents the number of IP datagrams that were successfully reassembled.

Reasm Reqds

This counter represents the number of IP fragments that were received that required reassembly at this entity.

IP6

The IP6 object, which supports Unified CCX, provides information on the IPv6-related statistics on your system. The following table contains information on the IP counters.

Table 14 IP6

Counters

Counter Descriptions

Frag Creates

This counter represents the number of IP datagrams fragments that have been generated as a result of fragmentation at this entity.

Frag Fails

This counter represents the number of IP datagrams that have been discarded because they needed to be fragmented at this entity but could not, for example because their Do not Fragment flag was set.

Frag OKs

This counter represents the number of IP datagrams that have been successfully fragmented at this entity.

In Delivers

This counter represents the total number of input datagrams successfully delivered to IP user-protocols (including Internet Control Message Protocol [ICMP]).

In Discards

This counter represents the number of input IP datagrams for which no problems were encountered to prevent their continued processing, but which were discarded (for example, for lack of buffer space). This counter does not include any datagrams that were discarded while awaiting reassembly.

In HdrErrors

This counter represents the number of input datagrams discarded due to errors in their IP header, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, and so on.

In Receives

This counter represents the number of input datagrams received from all network interfaces, including those received with errors.

In UnknownProtos

This counter represents the number of locally addressed datagrams that were received successfully but discarded because of an unknown or unsupported protocol.

InOut Requests

This counter represents the total number of IP datagrams received and the number of IP datagrams sent.

Out Discards

This counter represents the number of output IP datagrams that was not transmitted and was discarded. One reason may be a lack of buffer space.

Out Requests

This counter represents the total number of IP datagrams which local IP user-protocols (including Internet Control Message Protocol [ICMP]) supply to IP in requests transmission. This counter does not include any datagrams counted in ForwDatagrams.

Reasm Fails

This counter represents the number of failures detected by the IP reassembly algorithm (for various reasons, for example timed out, errors, and so on). This is not necessarily a count of discarded IP fragments since some algorithms, notably the algorithm in RFC 815, can lose track of the number of fragments by combining them as they are received.

Reasm OKs

This counter represents the number of IP datagrams that have been successfully reassembled.

Reasm Reqds

This counter represents the number of IP fragments received which needed to be reassembled at this entity.

Memory

The memory object provides information about the usage of physical memory and swap memory on the server. The following table contains information on memory counters.

Table 15 Memory

Counters

Counter Descriptions

% Mem Used

This counter displays the system physical memory utilization as a percentage. The value of this counter equals (Total KBytes - Free KBytes - Buffers KBytes - Cached KBytes + Shared KBytes) / Total KBytes, which also corresponds to the Used KBytes/Total KBytes.

% Page Usage

This counter represents the percentage of active pages.

% VM Used

This counter displays the system virtual memory utilization as a percentage. The value of this counter equals (Total KBytes - Free KBytes - Buffers KBytes - Cached KBytes + Shared KBytes + Used Swap KBytes) / (Total KBytes + Total Swap KBytes), which also corresponds to Used VM KBytes/Total VM KBytes.

Buffers KBytes

This counter represents the capacity of buffers in your system in kilobytes.

Cached KBytes

This counter represents the amount of cached memory in kilobytes.

Free KBytes

This counter represents the total amount of memory that is available in your system in kilobytes.

Free Swap KBytes

This counter represents the amount of free swap space that is available in your system in kilobytes.

Faults Per Sec

This counter represents the number of page faults (both major and minor) that the system made per second (post 2.5 kernels only). This does not necessarily represent a count of page faults that generate I/O because some page faults can get resolved without I/O.

Low Total

This counter represents the total low (non-paged) memory for kernel.

Low Free

This counter represents the total free low (non-paged) memory for kernel.

Major Faults Per Sec

This counter represents the number of major faults that the system has made per second that have required loading a memory page from disk (post 2.5 kernels only).

Pages

This counter represents the number of pages that the system paged in from the disk plus the number of pages that the system paged out to the disk.

Pages Input

This counter represents the number of pages that the system paged in from the disk.

Pages Input Per Sec

This counter represents the total number of kilobytes that the system paged in from the disk per second.

Pages Output

This counter represents the number of pages that the system paged out to the disk.

Pages Output Per Sec

This counter represents the total number of kilobytes that the system paged out to the disk per second.

Shared KBytes

This counter represents the amount of shared memory in your system in kilobytes.

Total KBytes

This counter represents the total amount of memory in your system in kilobytes.

Total Swap KBytes

This counter represents the total amount of swap space in your system in kilobytes.

Total VM KBytes

This counter represents the total amount of system physical and memory and swap space (Total Kbytes + Total Swap Kbytes) that is in use in your system in kilobytes.

Used KBytes

This counter represents the amount of system physical memory that is in use on the system in kilobytes. The value of the Used KBytes counter equals Total KBytes - Free KBytes - Buffers KBytes - Cached KBytes + Shared KBytes. The Used KBytes value differs from the Linux term that displays in the top or free command output. The Used value that displays in the top or free command output equals the difference in Total KBytes - Free KBytes and also includes the sum of Buffers KBytes and Cached KBytes.

Used Swap KBytes

This counter represents the amount of swap space that is in use on your system in kilobytes.

Used VM KBytes

This counter represents the system physical memory and the amount of swap space that is in use on your system in kilobytes. The value equals Total KBytes - Free KBytes - Buffers KBytes - Cached KBytes + Shared KBytes + Used Swap KBytes. This corresponds to Used Mem KBytes + Used Swap KBytes.

Network Interface

The network interface object provides information about the network interfaces on the system. The following table contains information on network interface counters.

Table 16 Network interface

Counters

Counter Descriptions

Rx Bytes

This counter represents the number of bytes, including framing characters, that were received on the interface.

Rx Dropped

This counter represents the number of inbound packets that were chosen to be discarded even though no errors had been detected. This prevents the packet from being delivered to a higher layer protocol. Discarding packets to free up buffer space provides one reason.

Rx Errors

This counter represents the number of inbound packets (packet-oriented interfaces) and the number of inbound transmission units (character-oriented or fixed-length interfaces) that contained errors that prevented them from being deliverable to a higher layer protocol.

Rx Multicast

This counter represents the number of multicast packets that were received on this interface.

Rx Packets

This counter represents the number of packets that this sublayer delivered to a higher sublayer. This does not include the packets that were addressed to a multicast or broadcast address at this sublayer.

Total Bytes

This counter represents the total number of received (Rx) bytes and transmitted (Tx) bytes.

Total Packets

This counter represents the total number of Rx packets and Tx packets.

Tx Bytes

This counter represents the total number of octets, including framing characters, that were transmitted out from the interface.

Tx Dropped

This counter represents the number of outbound packets that were chosen to be discarded even though no errors were detected. This action prevents the packet from being delivered to a higher layer protocol. Discarding a packet to free up buffer space represents one reason.

Tx Errors

This counter represents the number of outbound packets (packet-oriented interfaces) and the number of outbound transmission units (character-oriented or fixed-length interfaces) that could not be transmitted because of errors.

Tx Packets

This counter represents the total number of packets that the higher level protocols requested for transmission, including those that were discarded or not sent. This does not include packets that were addressed to a multicast or broadcast address at this sublayer.

Tx QueueLen

This counter represents the length of the output packet queue (in packets).

Number of Replicates Created and State of Replication

The Number of Replicates Created and State of Replication object provides real-time replication information for the system. The following table contains information on replication counters.

Table 17 Number of Replicates Created and State of Replication

Counters

Counter Descriptions

Number of Replicates Created

This counter displays the number of replicates that were created by Informix for the DB tables. This counter displays information during Replication Setup.

Replicate_State

This counter represents the state of replication. The following list provides possible values:

  • 0—Initializing. The counter equals 0 when the server is not defined or when the server is defined but realizes the template has not completed.
  • 1—Replication setup script fired from this node. Cisco recommends that you run utils dbreplication status on the CLI to determine the location and cause of the failure.
  • 2—Good Replication.
  • 3—Bad Replication. A counter value of 3 indicates replication in the cluster is bad. It does not mean that replication failed on a particular server in the cluster. Cisco recommends that you run utils dbreplication status on the CLI to determine the location and cause of the failure.
  • 4—Replication setup did not succeed.

Partition

The partition object provides information about the file system and its usage in the system. The following table contains information on partition counters. These counters are also available for the spare partition, if present.

Table 18 Partition

Counters

Counter Descriptions

% CPU Time

This counter represents the percentage of CPU time that is dedicated to handling I/O requests that were issued to the disk. This counter is no longer valid with the counter value -1.

% Used

This counter represents the percentage of disk space that is in use on this file system.

% Wait in Read

Not Used. The Await Read Time counter replaces this counter. This counter is no longer valid with the counter value -1.

% Wait in Write

Not Used. The Await Write Time counter replaces this counter. This counter is no longer valid with the counter value -1.

Await Read Time

This counter represents the average time, measured in milliseconds, for Read requests that are issued to the device to be served. This counter is no longer valid with the counter value -1.

Await Time

This counter represents the average time, measured in milliseconds, for I/O requests that were issued to the device to be served. This includes the time that the requests spent in queue and the time that was spent servicing them.This counter is no longer valid with the counter value -1.

Await Write Time

This counter represents the average time, measured in milliseconds, for write requests that are issued to the device to be served. This counter is no longer valid with the counter value -1.

Queue Length

This counter represents the average queue length for the requests that were issued to the disk. This counter is no longer valid with the counter value -1.

Read Bytes Per Sec

This counter represents the amount of data in bytes per second that was read from the disk.

Total Mbytes

This counter represents the amount of total disk space in megabytes that is on this file system.

Used Mbytes

This counter represents the amount of disk space in megabytes that is in use on this file system.

Write Bytes Per Sec

This counter represents the amount of data that was written to the disk in bytes per second.

Process

The process object provides information about the processes that are running on the system. The following table contains information on process counters.

Table 19 Process

Counters

Counter Descriptions

% CPU Time

This counter, which is expressed as a percentage of total CPU time, represents the tasks share of the elapsed CPU time since the last update.

% MemoryUsage

This counter represents the percentage of physical memory that a task is currently using.

Data Stack Size

This counter represents the stack size for task memory status.

Nice

This counter represents the nice value of the task. A negative nice value indicates that the process has a higher priority while a positive nice value indicates that the process has a lower priority. If the nice value equals zero, do not adjust the priority when you are determining the dispatchability of a task.

Page Fault Count

This counter represents the number of major page faults that a task encountered that required the data to be loaded into memory.

PID

This counter displays the task-unique process ID. The ID periodically wraps, but the value will never equal zero.

Process Status

This counter displays the process status:

  • 0—Running
  • 1—Sleeping
  • 2—Uninterruptible disk sleep
  • 3—Zombie
  • 4—Stopped
  • 5— Paging
  • 6—Unknown

Shared Memory Size

This counter displays the amount of shared memory (KB) that a task is using. Other processes could potentially share the same memory.

STime

This counter displays the system time (STime), measured in jiffies, that this process has scheduled in kernel mode. A jiffy corresponds to a unit of CPU time and gets used as a base of measurement. One second comprises 100 jiffies.

Thread Count

This counter displays the number of threads that are currently grouped with a task. A negative value (-1) indicates that this counter is currently not available. This happens when thread statistics (which includes all performance counters in the Thread object as well as the Thread Count counter in the Process object) are turned off because the system total processes and threads exceeded the default threshold value.

Total CPU Time Used

This counter displays the total CPU time in jiffies that the task used in user mode and kernel mode since the start of the task. A jiffy corresponds to a unit of CPU time and gets used as a base of measurement. One second comprises 100 jiffies.

UTime

This counter displays the time, measured in jiffies, that a task has scheduled in user mode.

VmData

This counter displays the virtual memory usage of the heap for the task in kilobytes (KB).

VmRSS

This counter displays the virtual memory (Vm) resident set size (RSS) that is currently in physical memory in kilobytes (KB). This includes the code, data, and stack.

VmSize

This counter displays the total virtual memory usage for a task in kilobytes (KB). It includes all code, data, shared libraries, and pages that have been swapped out: Virtual Image = swapped size + resident size.

Wchan

This counter displays the channel (system call) in which the process is waiting.

Processor

The processor object provides information on different processor time usage in percentages. The following table contains information on processor counters.

Table 20 Processor

Counters

Counter Descriptions

% CPU Time

This counter displays the processors share of the elapsed CPU time, excluding idle time, since the last update. This share gets expressed as a percentage of total CPU time.

Idle Percentage

This counter displays the percentage of time that the processor is in the idle state and did not have an outstanding disk I/O request.

IOwait Percentage

This counter represents the percentage of time that the processor is in the idle state while the system had an outstanding disk I/O request.

Irq Percentage

This counter represents the percentage of time that the processor spends executing the interrupt request that is assigned to devices, including the time that the processor spends sending a signal to the computer.

Nice Percentage

This counter displays the percentage of time that the processor spends executing at the user level with nice priority.

Softirq Percentage

This counter represents the percentage of time that the processor spends executing the soft IRQ and deferring task switching to get better CPU performance.

System Percentage

This counter displays the percentage of time that the processor is executing processes in system (kernel) level.

User Percentage

This counter displays the percentage of time that the processor is executing normal processes in user (application) level.

Ramfs

Table 21 Ramfs

Counter

Description

FilesTotal

The total number of files in the ram-based filesystem (ramfs).

SpaceFree

The amount of free data blocks in the ram-based filesystem (ramfs). A block is a uniformly sized unit of data storage for a filesystem. The block size specifies the size that the filesystem will use to read and write data.

SpaceUsed

The amount of used data blocks in the ram-based filesystem (ramfs). A block is a uniformly sized unit of data storage for a filesystem. The block size specifies the size that the filesystem will use to read and write data.

Reporting Engine Info

Table 22 Reporting Engine Info

Counter

Description

Report (H/RT) CellsRetrieved

Total number of cells (rows times columns) that have been retrived from all data sources

Report (H/RT) CellsRetrievedInterval

Change of counter Report (H/RT) CellsRetrieved over the last interval

Report (H/RT) Completed

Total number of reports that have been successfully executed

Report (H/RT) CompletedInterval

Change of counter Report (H/RT) Completed over the last interval

Report (H/RT) Data PreprocessingTimeChart

Total amount of time spent processing report's data to display it in charts.

Report (H/RT) Data PreprocessingTimeChartInterval

Change of counter Report (H/RT) DataPreprocessingTimeChart over the last interval.

Report (H/RT) Data PreprocessingTimeGauge

Total amount of time spent processing report's data to display it in gauges.

Report (H/RT) Data PreprocessingTimeGaugeInterval

Change of counter Report (H/RT) DataPreprocessingTimeGauge over the last interval.

Report (H/RT) Data PreprocessingTimeGrid

Total amount of time spent processing report's data to display it in grids.

Report (H/RT) Data PreprocessingTimeGridInterval

Change of counter Report (H/RT) DataPreprocessingTimeGrid over the last interval.

Report (H/RT) DataSetFetch Accepted

The total number of times that a request to fetch a DataSet has been accepted. Not all requests to fetch a DataSet are accepted. If the data for a report is already being fetched, another worker thread is not created to retrieve the same data.

Report (H/RT) DataSetFetch AcceptedInterval

The interval measure of the above counter.

Report (H/RT) DataSetFetch Requests

The total number of times that a request to fetch data from a Data Source has been received.

This happens every time a report is launched for the first time (in which case, there is also a request to create a new DataSetInfo object), and every time there is a request to refresh a report that has already been launched.

Report (H/RT) DataSetFetch RequestsInterval

The interval measure of the Report (H/RT) DataSetFetchRequests counter.

Report (H/RT) DataSetInfo Created

Out of all the requests for a new DataSetInfo object (Report (H/RT) DataSetInfoRequested), how many times a new object has actually been created.

An object is actually created only when one does not already exist for the same Report Definition and Filter. This is the case if no user has ever run that Report Definition with that Filter or if the Purge mechanism of the CUIC DB has cleared up any record of previous users running that Report Definition with that Filter.

Report (H/RT) DataSetInfo CreatedInterval

The interval measure of the Report (H/RT) DataSetInfoCreated counter.

Report (H/RT) DataSetInfo Requested

The total number of times that a request to create a new DataSetInfo object has been received.

A new DataSetInfo object is created when a report is being launched for the very first time. By report what is meant is the combination of a Report Definition and a Filter. For example, executing Report Definition (template) R1 with Filter F1 produces DataSetInfo D1<R1, F1>. Executing Report Definition R2 with Filter F2 produce DataSetInfo D2<R2, F2>.

If another user runs Report Definition (template) R1 with Filter F1, a request to create a new DataSetInfo object is received, but a new object will not be created. Instead, D1 will be reused. DataSetInfo D1<R1, F1>

Report (H/RT) DataSetInfo RequestedInterval

The interval measure of the Report (H/RT) DataSetInfoRequested counter.

Report (H/RT) DataSetInfo Read

The number of times that a view (grid/gauge/chart) has read the data of a (H/RT) report. This tells how many times the data of reports is being prepared to be displayed to a user (turned into HTML or XML).

Report (H/RT) DataSetInfo ReadInterval

The interval measurement of the Report (H/RT) DataSetReadTotal counter.

Report (H/RT) Failed

The total number of reports that have failed. The total number of times that CUIC has tried to fetch data from a Data Source but it has not been able to.

Report (H/RT) FailedInterval

The interval measurement of the Report (H/RT) Failed counter.

Report (H/RT) RenderedChart

Total number of times that the data of a report has been turned into a Chart and sent to a browser (or any other client).

Report (H/RT) RenderedChart Interval

The interval measurement of the Report (H/RT) RenderedChart counter.

Report (H/RT) RenderedGauge

Total number of times that the data of a report has been turned into a Gauge and sent to a browser (or any other client).

Report (H/RT) RenderedGauge Interval

The interval measurement of the Report (H/RT) RenderedGauge counter.

Report (H/RT) RenderedGrid

Total number of times that the data of a report has been turned into a Grid and sent to a browser (or any other client).

Report (H/RT) RenderedGrid Interval

The interval measurement of the Report (H/RT) RenderedGrid counter.

Report (H/RT) RenderedRows Retrieved

The total number of rows that have been retrieved by CUIC from data sources.

Report (H/RT) RenderedRows RetrievedInterval

The interval measurement of the Report (H/RT) RowsRetrievedTotal counter.

Report (H/RT) Running

The number of (H/RT) reports that are currently running. A report is currently running when the Runnable object has been assigned a thread from the pool. It does not include those that are waiting in a queue for a thread to become available.

Report (H/RT) Running Interval

The interval measurement of the Report (H/RT) Running counter.

Report (H/RT) Runtime

Total amount of seconds spent running reports.

Report (H/RT) RuntimeInterval

Change of counter Report (H/RT) Runtime over the last interval.

Report (H/RT) Runtime DatasourceTime

The number of seconds or milliseconds that CUIC has spent waiting for ICM, or any other database, to return the data of a query. This includes the time from the moment CUIC commits the JDBC query to the moment CUIC gets control back (when the worker thread stops being in an I/O blocked state).

Subset of Report (H/RT) lRuntime. Amount of time that was spent waiting for data sources to return the report's data.

Report (H/RT) Runtime DatasourceTimeInterval

The interval measurement of the Report (H/RT) DataSourceTimeTotal counter.

Report (H/RT) Waiting

Total number of reports that are currently queued for execution.

Report (H/RT) Waiting Interval

Change of counter ReportRealtimeWaiting over the last interval.

ReportsUniqueUsersLoggedinInterval

Total number of unique logged in users over the past interval. Does not count same user who leaves and comes back within the interval.

ReportsUsersFailedLoginAttempts

Total number of failed login attempts.

ReportsUsersFailedLoginAttemptsInterval

Change of counter ReportsUsersFailedLoginAttempts over the last interval.

ReportsUsersLoggedin

Total number of users that are currently logged in

SchedulerInfo

Table 23 SchedulerInfo

Counter

Description

SchedulerIntervalLength

How often the scheduler will execute, in seconds.

SchedulerJobsCompletedCount

The number of jobs that the scheduler service has completed

SchedulerJobsFailedCount

The number of jobs that the scheduler service has failed to complete successfully.

SchedulerJobsRunningCount

The number of jobs that the scheduler service is currently running.

SchedulerState

The current state of the scheduler. The possible values are: 0. - Stopped, 1.- Idle, 2.- Suspended and 3.-Running

System

The System object provides information on file descriptors on your system. The following table contains information on system counters.

Table 24 System

Counters

Counter Descriptions

Allocated FDs

This counter represents the total number of allocated file descriptors.

Being Used FDs

This counter represents the number of file descriptors that are currently in use in the system.

Freed FDs

This counter represents the total number of allocated file descriptors on the system that are freed.

Max FDs

This counter represents the maximum number of file descriptors that are allowed on the system.

Total CPU Time

This counter represents the total time in jiffies that the system has been up and running.

Total Processes

This counter represents the total number of processes on the system.

Total Threads

This counter represents the total number of threads on the system.

TCP

The TCP object provides information on the TCP statistics on your system. The following table contains information on the TCP counters.

Table 25 TCP

Counters

Counter Description

Active Opens

This counter displays the number of times that the TCP connections made a direct transition to the SYN-SENT state from the CLOSED state.

Attempt Fails

This counter displays the number of times that the TCP connections have made a direct transition to the CLOSED state from either the SYN-RCVD state or the SYN-RCVD state, plus the number of times TCP connections have made a direct transition to the LISTEN state from the SYS-RCVD state.

Curr Estab

This counter displays the number of TCP connections where the current state is either ESTABLISHED or CLOSE- WAIT.

Estab Resets

This counter displays the number of times that the TCP connections have made a direct transition to the CLOSED state from either the ESTABLISHED state or the CLOSE-WAIT state.

In Segs

This counter displays the total number of segments that were received, including those received in error. This count only includes segments that are received on currently established connections.

InOut Segs

This counter displays the total number of segments that were sent and the total number of segments that were received.

Out Segs

This counter displays the total number of segments that were sent. This count only includes segments that are sent on currently established connections, but excludes retransmitted octets.

Passive Opens

This counter displays the number of times that TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state.

RetransSegs

This counter displays the total number of segments that were retransmitted because the segment contains one or more previously transmitted octets.

Thread

The Thread object provides a list of running threads on your system. The following table contains information on the Thread counters.

Table 26 Thread

Counters

Counter Description

% CPU Time

This counter displays the threads share of the elapsed CPU time since the last update. This counter expresses the share as a percentage of the total CPU time.

PID

This counter displays the threads leader process ID.

Unified CCX DB Monitors

Table 27 Unified CCX DB Monitors

Counter

Description

DB CRA % Space Used

This represents the amount(%) of space used by Unified CCX Configuration Data.

DB CRA REPOSITORY % Space Used

This represents the amount(%) of space used by Unified CCX Repository.

FcrAsSvr % Space Used

This represents the amount(%) of space used by Unified CCX Frascal.

Unified CCX Engine JVM Heap

Table 28 Unified CCX Engine JVM Heap

Counter

Description

KBytesMemoryCommitted

This represents the amount of memory in Kbytes that is committed for the Engine JVM to use. This amount of memory is guaranteed for the JVM to use.

KBytesMemoryMax

This represents the maximum amount of memory in bytes that can be used by Engine JVM. Based on the availability of System memory, the JVM may fail to allocate memory even if the amount of used memory does not exceed this maximum size.

KBytesMemoryUsed

This represents the amount of memory currently in use by the JVM.

PercentageMemoryUsedAfterGC

This represents the percentage of heap memory that is used by the application after the last full Garbage Collection cycle.