This short video will focus on our PowerSuite Monitoring Dashboard Solution. The Monitoring Dashboard provides probe list service availability monitoring by mimicking typical end user scenarios 24/7 using custom synthetic transactions to strengthen performance of on-premise Skype for Business and cloud-based Microsoft Teams deployments. When problems occur, incidents are generated that bubble up troubleshooting logs plus insights and expert guidance to shorten resolution times and help deliver a world-class UC and user experience. Here, at the top-level of the Monitoring Dashboard, we see an overview of key Skype for Business information. Current availability, driven by a set of rules to allow for scenario tests from your environment, shows the up-to-date availability of the service. Service availability by range gives us detailed look of availability for a period of time.
High-priority incidents prioritizes incidents that require immediate attention and other recent incidents provide a list of all incidents and their impact to the service during their duration. Now let’s take a look at some examples in the first high-priority incident. We are showing that there is an inbound PSTN issue between two of our synthetic transaction accounts. We can see that this is a sustained incident due to the outage duration. By clicking on this incident, we can drill down and gather more information. Here, PowerSuite monitoring provides us with important information on how to remediate this incident. We see tracking information about the incident, including the scenario that is failing. The analysis widget bubbles up the specific route caused plus insights and expert guidance. Here, PowerSuite is reporting that there is an issue with a media relay authentication service and directs us to investigate the Skype for business edge environment. For a deeper technical understanding of the incident, there is the scenario failures widget. Here, we see the troubleshooting logs that PowerSuite collected for this incident including the steps that were taken the failure and the specific error message returned, the endpoints involved, and the registration path and the sip messages about the incident. Next let’s look at another high-priority incident this incident is showing that there is an issue with one of our dialing access numbers drilling into the analysis widget we see that the PSTN gateway cannot route the call to the PSTN target and the host name of the specific PSTN gateway. This helps us by identifying the piece of equipment that is experiencing an issue. Now we have an action plan for this specific PSTN gateway but also for testing to eliminate the three possible issues that may have led to this incident.