The reports and displays from CPM Monitoring and CPM Analytics are not expected to be identical. This is because different data is being captured for the different reporting that they are designed to deliver for you:
- Leverages real-time APIs to capture current activities and statistics for each endpoint and infrastructure monitored. Data is captured at the most granular level. For example, individual call legs between conferencing nodes will be captured and displayed in CPM Monitoring.
- Leverages CDR records / Log APIs to capture ALL activities from the infrastructure devices' short-term databases. This will contain all calls including some very short or failed calls.
Here are a couple of common scenarios where the reporting from these two tools might not perfectly align:
You see data in CPM Analytics that does not show up in CPM monitoring - Since it captures all calls from the infrastructure database, CPM Analytics is the true "system of record" in terms of call activities. CPM Monitoring may not catch in real time some calls that failed or ended within a few seconds.
You see data in CPM Monitoring that is not shown in CPM Analytics - Reporting duplicated call legs in CPM Monitoring adds value in troubleshooting a call path. However, it overstates the actual call volume. In CPM Analytics, we implemented advanced cleansing and deduplication logic to display accurate overall call metrics.
CPM Monitoring and CPM Analytics take their data from different sources, and it is therefore possible that data may not match. CPM Monitoring takes real-time data feeds from the endpoints and infrastructure, and reflects this in the CPM Monitoring module. CPM Analytics takes historical data, such as call records and system configuration, and processes these for display in the CPM Analytics module. There is there potential for mismatch when either CPM Monitoring or CPM Analytics does not update.
Article is closed for comments.