Teams and Zoom have become ubiquitous in the meeting environment, and now we see many hybrid meetings where some people attend in person and others remotely.
Although complete outages are rare, there are a number of moving parts that can affect the performance of a virtual call between the user's client computer and the Teams/Zoom Service – WiFi, Bluetooth, Network, etc.
OmniContext is a Utilization and Performance Monitor for these components, providing:
Teams Call Quality monitoring (as well as Zoom) – to answer the question - is the problem your end or ours?
VIP focused – explicitly monitor the Teams experience of your key employees
Alert admins to take action on slowdowns in the user experience before they become outages
Capture data to build utilization and optimization strategies for bookable spaces
Teams and Zoom Call Quality Monitoring
Availability of service can be monitored in multiple ways:
Uptime of the service itself is the application running and does it appear healthy on the system where the service is deployed? Such measurement would usually be produced by cloud service providers and published for everybody’s reference. It confirms that the service itself is operational, however does not verify the ability of end users to consume it.
Health of underlying system resources such as networks and hardware. Whereas it does not ensure the service works as such, it can be used to troubleshoot the root causes of failures and to proactively detect resources shortage that leads to the degradation of service.
End-user experience monitoring which confirms that a user can actually work with the application and execute normal actions as expected. This type of monitoring is not available from cloud service providers and can only be performed by customers from their networks.
The principal objectives of service monitoring are:
Know in real time when a service is down, so users can be alerted and the outage can be mitigated immediately
Analyze and understand longer-term performance in order to identify recurring patterns, find root causes of failures, and improve deployments to prevent known problems from happening in the future
Measurements are usually collected from multiple selected locations, which can be at different locations within the customer’s environment, or even directly on users’ workstations. These locations are presented as “sources” in the monitoring status and reports, and the measured services are listed as “targets”.
Alerts and Notifications
OmniContext allows for configuring conditions that trigger alerts such as a total outage, or a level of latency that makes user actions take longer than expected.
Alerts can be configured for a combination of several conditions, or for repeated failures within a certain time period.
Once an alert condition happens, a notification can be sent to an email address, or to the OmniContext mobile app. OmniContext can also post alert notifications into event logs, or automatically create and modify incidents in trouble ticket applications such as ServiceNow.
Out-of-the-Box Monitoring Actions and Parameters
OmniContext Agent is able to run various monitoring tests – from the simplest server pings to sophisticated end user experience simulations in Office365 applications. A number of tests scenarios are available out of the box. When there is a need to monitor a scenario which is not covered by predefined configurations, it is possible to create new scenarios combining atomic transactions into meaningful action sets to simulate end user activities. OmniContext Agent provides user interface to choose a test scenario from predefined ones and to set final configuration for the test.