Monitor Messages Per Second

The Converged Application Server allows you to monitor the messages per second (MPS) sent or received by your application to align with your licensed capacity. With a default 12-month historic MPS retention, you can audit usage trends and plan adjustments to your MPS license.

The MPS metric is defined by the total number of every SIP request, SIP response, Diameter request, Diameter answer, API Request, API Response, http(s) request and http(s) response both sent to and received by the Converged Application Server (including re-transmissions), over a sampling interval of 30 seconds. The MPS can be calculated as the calls per second multiplied by the incoming and outgoing messages per call.

The following messages are not counted for the MPS metric:

Messages between the Converged Application Server SIP Servlet applications in the same managed node (SIP Engine, JVM), regardless of:
- Messages routed via the local network interface
- Messages passed as java objects
Messages sent to or received from observability and monitoring tools, continuous delivery tooling, configuration tools including REST API for configuration, and other tools used to monitor and operate the Converged Application Server environment
Diameter Connection Control messages
Messages rejected/dropped by the overload protection feature

Understand the following terms to understand how the licensed MPS is calculated.

Peak MPS—The highest number of messages (SIP, Diameter, API, http(s)) amassed in a 1-second interval during a 30-second window.
Average MPS—The number of protocol messages (SIP, Diameter, API, http(s)) per second averaged over a 30 second window.
In the following example, the Peak MPS is 8502, and the Average MPS is 2534.
Sampling Rate—The frequence with which the average number of messages is collected.
For example, if the sampling rate is 5 seconds, then the Converged Application Server calculates the average MPS over a 30 second sliding window. The first sample covers 0 - 30 seconds, the second sample covers 5 - 35 seconds, the third sample covers 10 - 40 seconds, and so on.
Retention Window—A 5 minute period during which the average MPS samples are retained in an internal buffer in memory.
The retention window is used to record the peak of the average MPS values.

Peak Average MPS—The highest number of average MPS values over the retention window.

In the following example data set, the peak of the average MPS is 2542 within this 5 minute retention window.

Time	Sample	Average MPS
1 - 30 seconds	1	2534
5 - 35 seconds	2	2530
10 - 40 seconds	3	2515
15 - 45 seconds	4	2519
. . .	. . .	. . .
4 mins 25 sec - 4 mins 55 sec	59	2540
4 mins 30 sec - 5 mins	60	2542

Licensed Peak Average MPS—Your licensed MPS number.
The Converged Application Server checks the retention window every 5 minutes for peak average MPS values that exceed your licensed peak MPS.

If the peak average MPS value exceeds the threshold limit, the Converged Application Server logs the alarm in the console log and updates the MPSConfig descriptor bean attribute BreachInfo with the message "Threshold limit crossed during period <FROMDATE> and <TODATE>".

The directory <DOMAIN_HOME>/servers/logs/MPS contains files called MPS_<MM-dd-YYYY>.csv that contains the start time, end time, and peak average MPS. This file is rotated daily. Files in this directory that are older than the Historic MPS Persistency value are purged.

Note:

Use the Historic MPS Persistency value to limit how much disk space is devoted to MPS logs.

See the "MPS License Metric Definition" section of the License Document for a detailed definition of what traffic is and is not counted in the MPS metric.