The guide below offers a brief introduction to how users interact with monitoring in Mividas Core.
1. Navigate to Mividas Core
Start by navigating to your Mividas Core installation.
2. CMS Cluster notifications
On the Mividas Core dashboard, you’ll find an overview of all call bridges along with their notifications and severity levels. In this example “CMS Cluster” is displaying a single notification marked with a severity level of “Error”. Continue by clicking on the accordion.
3. Expanded cluster
This will expand the accordion to reveal all servers within the cluster, showing that the “CMS 1” server has an error.
4. Click on server “CMS 1”
Continue by clicking on the “CMS 1” server.
5. Expanded server
Clicking the server will expand the accordion, revealing additional server details along with current notifications and their severity levels.
6. “cdrConnectionFailure” error notification
The “CMS 1” server currently shows an error notification: “cdrConnectionFailure.” You can either acknowledge the error—hiding it in the Mividas Core interface until it is triggered again—or address and resolve the issue directly on the server.
7. Click “Monitoring”
8. Monitoring overview
The monitoring section provides an overview of all active notifications generated by your connected servers, along with their severity levels.
9. Filter view on “Errors”
At the top, you’ll find a quick overview of severity levels, indicating the number of affected servers for each severity type. Click on the severity level “Error” to filter the view, displaying only notifications of that severity level.
10. Filtered view
We can see that there is one notification with a severity level of “Error,” which affects one server.
11. Expand row
Continue by expanding the row.
12. Expanded row
Expanding the row will reveal a list of servers affected by this notification. In this case, we see the “CMS 1” server, consistent with what we observed on the Mividas Core dashboard.
13. Click “Acknowledge and hide”
You now have the option to click “Acknowledge and hide”, which will conceal the notification for the server across the interface until it is triggered again. Proceed by clicking the button.
14. The dashboard view
Clicking “Acknowledge and hide” will remove the notification from view. Keep in mind that you can still display acknowledged notifications by using the filter function in the interface.
15. Click “Dashboard”
Navigate back to the Mividas Core dashboard.
16. The dashboard view
After acknowledging the error, the CMS Cluster displays a green checkmark and a note indicating one acknowledged notification. You can easily re-display the error notification if needed.
17. Click “Monitoring”
Navigate back to the “Monitoring” section.
18. Click “Per Server”
Click on “Per Server” tab.
19. The “Per Server” view
The “Per Server” view in monitoring allows quick access to a specific server, clearly displaying its notifications and severity levels. Here, we can see that the “CMS 1” server now has one acknowledged notification.
20. Expand the “CMS 1” server row.
21. Expanded server row
The previously acknowledged “cdrConnectionFailure” now appears as an acknowledged notification, with the option to reactivate and display the error again.
21. Click “Activate and show”
Click the “Activate and Show” button to redisplay the error. Note that the error would also automatically reappear if it is retriggered on the server.
22. Click “Dashboard”
Return to the Mividas Core dashboard.
23. The “Dashboad” view
Click and expand the “CMS 1” server.
24. Expanded “CMS 1” server
The cdrConnectionFailure have now return.
25. Acknowledge and hide the notification
You also have the option to acknowledge and hide the error directly from the dashboard. Click the “Acknowledge and Hide” button to proceed.
26. Acknowledge and hide from expanded server
After acknowledging the error, both the “CMS 1” server and the “CMS Cluster” will display a green checkmark. This concludes our brief demonstration of the monitoring views and workflow in Mividas Core.