Maintain SaaS application performance through network visibility.
The upside of the SaaS adoption has already been felt by most of us. We can collaborate with colleagues instantly from anywhere while our data are uploaded to the cloud seamlessly. This is, without a doubt way more convenient and effective than the old way of sending documents to each other via email and trying to maintain control over the document version history stored on disks with shared access.
The lack of visibility and lack of understanding of the communication channels between the applications and end-users may cause communication chaos, paralyse company operations and significantly lower the ROI of adopting SaaS.
Knowing whether the fault is within the network between the affected SaaS user or at the SaaS provider's side a key piece of knowledge that cures a lot of headaches and substantially lowers the impact of SaaS performance issues.
List of devices with the worst Office365 Server Response Times
Since the hot potato of SaaS performance issues usually ends up in the lap of NetOps, having the right data can significantly help them hasten the remediation process. Typically when SaaS performance degrades, there can be 3 different scenarios:
With the right data, the responsible staff can choose the correct course of action in each scenario:
In short, Flowmon outright tells you which of these 3 scenarios is your case.
To distinguish between these 3 scenarios, Flowmon measures the round trip time (the time it takes a packet of a TCP handshake to travel from the local network to the SaaS provider and back), server response time (the time it takes for the SaaS provider’s server to respond), jitter (variance of delays between packets) and volumetric statistics (the volume of data that travels at a given moment).
These metrics typically help to distinguish between the 3 scenarios in the following way:
These combinations of values help to diagnose where the fault lies. Additionally, volumetric statistics can help to diagnose whether the capacity of the local link can carry the SaaS load. Jitter can help to reveal unstable network connections.