Cisco Explorer 1540 Specifications Page 181

  • Download
  • Add to my manuals
  • Print
  • Page
    / 924
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 180
5-57
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
Chapter 5 Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Database Change Notification Server
The Database Change Notification Server object provides information on different
change-notification-related statistics.
Table 5-47 contains information on the Database Change
Notification Server counters.
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.
Table 5-46 Database Change Notification Client (continued)
Counters Counter Descriptions
Ta b l e 5-47 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.
Page view 180
1 ... 180 181 182 ... 924

Comments to this Manuals

No comments