It’s only four easy steps. Let’s get started.
Next
Deploy ObserverLIVE service monitors to validate the availability and responsiveness of websites or web applications (SaaS).
How many service monitors will you need between your locations and web applications?
Deploy ObserverLIVE network monitors to validate link connectivity and quality between endpoints.
Here’s an example: An organization with a headquarters and three branch locations needs to assess those connections to confirm compliance with provider service level agreements.
Hub and Spoke:
To confirm connectivity between headquarters and all branch locations the organization will need three network monitors.
Mesh:
To ensure each site has acceptable connectivity with every other site, six network monitors will be required.
How many network monitors will you need between your locations?
Deploy ObserverLIVE VoIP monitors to validate VoIP connectivity and quality between endpoints.
Here’s an example: An organization with four locations needs to ensure VoIP call quality between all sites.
To proactively validate VoIP performance from headquarters to the branches, it will need three VoIP monitors.
To ensure each site has acceptable connectivity with every other site, six VoIP monitors will be needed.
How many VoIP monitors will you need between your locations?
Deploy ObserverLIVE troubleshooting monitors on demand to help resolve application and VoIP issues. Redeploy as needed.
How many monitors would you like to use for remote user troubleshooting?
Submit
Here is a breakout of how many monitors you’ll need for each usage type, along with a total.
0
Request a Quote
Contact Us