Monitoring BVR

The VM can be monitored using the bvr -m command. The command can either be run as a one off snapshot or in a polling mode. The reported information is a realtime view of the current status of BVR.

Table 1. Data that can be monitored
Name Description
System Uptime How long the system has been running in days, hours, minutes and seconds
Cumulative Inbound Call Count Cumulative total number of inbound calls the system has accepted since being restarted
Cumulative Outbound Call Count Cumulative total number of outbound calls the system has accepted since being restarted
Cumulative Call Count Cumulative total number of both inbound and outbound calls the system has accepted since being restarted
Active SIP Calls Current number of active SIP calls - these are calls with active signaling
Active Voice Applications Current number of active voice applications
Active MM CCXM Current number of active multi-mode ccxml applications
Active SM CCXML Sessions Current number of active single-mode ccxml applications
Used Memory Java heap memory used in MB - once the system is running a while this should reach a peak and be less than Max Memory
Max Memory Maximum Java heap memory available in MB
Active Threads Number of active threads by the JVM - once the system is running a while this should reach a peak
Current Channels Total number of channels being used by streaming - this should roughly match the Active SIP Calls
Lock Contention Total number of locks triggered - this is informational and shows kernel lock contention and can be ignored
Last IH Last interrupt handler time - current interrupt handler time, this should be lower than 17ms
Max IH Highest interrupt handler time
Warnings Number of warning messages triggered
Errors Number of error messages triggered