Table of Contents
Advertisement
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Table 5-46
Database Change Notification Client (continued)
Counters
QueueHeadPointer
QueueMax
QueueTailPointer
TablesSubscribed
Database Change Notification Server
The Database Change Notification Server object provides information on different
change-notification-related statistics.
Notification Server counters.
Table 5-47
Database Change Notification Server
Counter
Clients
Queue Delay
QueuedRequestsInDB
QueuedRequestsInMemory
OL-22523-01
Counter Descriptions
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.
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.
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
This counter represents the number of tables in which this client has subscribed.
Table 5-47
Counter Descriptions
This counter represents the number of change notification clients
(services/servlets) that have subscribed for change notification.
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.
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.
This counter represents the number of change notification requests that are
queued in shared memory.
Cisco Unified Communications Manager Managed Services Guide
Performance Monitoring in RTMT
contains information on the Database Change
5-63
Advertisement
Chapters
Table of Contents
Troubleshooting
