Practical examples

On this page you can find several scenarios that can show you how Ymonitor has been used in practice in the past.

Scenario 1 – Different locations

Below there is an availability graph from the different sentinels of an application. In it you can see that the green line (Atlanta) keeps being around 100% while the other lines (Singapore and Netherlands) show 0% availability around the same time.

Open

Here it is interesting to see that the problems only manifest from two of the three locations. The first step in finding the source of the problem would be to look at what components are the same for the locations showing unavailability and that the location that is fine doesn’t have.

In this example they looked at these components and found that a certain switch was used for the communication of Singapore and the Netherlands while the traffic from Atlanta didn’t go over this switch. So using Ymonitor they had reduced the possible problems down to a single switch.

Scenario 2 – Multiple Services

Below is the availability graph of the citrix implementation of an application. In it you can see that one of the transactions of the application has a problem.

Open

While the line shows that the login transactions has had problems in the past it hasn’t been this much of a problem before. Looking at the application the team couldn’t find any problems. However in Ymonitor there was also a version of the application without Citrix.

In the web version there were no visible problems with the login transactions. Since the problem was only visible from the Citrix measurements it narrowed the problem down to the Citrix servers and connections from them to the application.