Universal Messaging 10.3 | Concepts | Deployment | Server | Periodic Logging of Server Status
 
Periodic Logging of Server Status
The Universal Messaging server writes status information to the log file at regular intervals. The default interval can be configured using the StatusBroadcast realm configuration property, and the default value is 5 seconds).
For information on realm configuration properties, see the section Realm Configuration in the Enterprise Manager part of the Administration Guide.
Here is a sample status log message:

ServerStatusLog> Memory=3577, Direct=3925, EventMemory=0,
Disk=277070, CPU=0.2, Scheduled=29, Queued=0, Connections=5,
BytesIn=12315, BytesOut=19876, Published=413, Consumed=1254,
QueueSize=0, ClientsSize=0, CommQueueSize=0
The following table describes the status log metrics:
Metric
Description
Unit
Memory
Free JVM memory
Megabyte
Direct
Free direct memory
Megabyte
EventMemory
JVM memory consumed by events
Megabyte
Disk
Free disk space in UM data directory
Megabyte
CPU
Recent CPU usage for the JVM process
A floating point number in the [0.0,1.0] interval. A value of 0.0 means that none of the CPUs were running threads from the JVM process during the recent period of time observed, while a value of 1.0 means that all CPUs were actively running threads from the JVM 100% of the time during the recent period being observed. All values between 0.0 and 1.0 are possible depending of the activities going on in the JVM process and the whole system.
Scheduled
Number of tasks in the internal scheduler
Queued
Number of total tasks currently queued in all thread pools
Connections
Active Universal Messaging connections
BytesIn
Total bytes received for currently active Universal Messaging connections
byte
BytesOut
Total bytes sent for currently active Universal Messaging connections
byte
Published
Total number of consumed events
Consumed
Total number of published events
QueueSize
Cluster queue size (present only if the realm is part of a cluster)
ClientsSize
Cluster client request queue size (present only if the realm is part of a cluster)
CommQueueSize
Cluster communication queue size (present only if the realm is part of a cluster)
During server startup and each time the log file is rolled, a status log legend is printed in the log file:
ServerStatusLog> Activating Realm status log with format:
Memory - free memory (MB)
Direct - free direct memory (MB)
EventMemory - used event memory (MB)
Disk - free disk space (MB) in server data directory
CPU - cpu load average
Scheduled - scheduled tasks
Queued - total queued tasks in all thread pools
Connections - active connections count
BytesIn - total bytes received (for all active connections)
BytesOut - total bytes send (for all active connections)
Published - total count of published events
Consumed - total count of consumed events
QueueSize - cluster queue size
ClientsSize - cluster client request queue size
CommQueueSize - cluster communication queue size
Periodic logging of the server status can be disabled using the EnableStatusLog realm configuration property.
For information on realm configuration properties, see the section Realm Configuration in the Enterprise Manager part of the Administration Guide.
For information on log rolling, see the section Universal Messaging Enterprise Manager : Logs Panel in the Enterprise Manager part of the Administration Guide.