Hello Manny,
thank you for your post.
Please confirm, you've already deployed the remote probe in the branch office and want sensor recommendations for this branch office, correct?
Basically, if the branch office is only using services from the main site via MPLS, you can focus on monitoring the performance of this link.
- If you're using Cisco devices on both ends, considering setting-up Cisco's IP SLA, which will provide several network performance metrics which can be monitored with our Cisco IP SLA Sensor. If you're not using Cisco hardware (or it doesn't support SLA), then you can use our QOS Round Trip sensor, which will provide very similar readings as the IP SLA sensor but by using "dummy" UDP traffic sent from one PRTG probe to the Other (setup requires two probes).
- You should also consider using a SNMP Traffic Sensor on one of the endpoints of the MPLS (or on the uplink switch interface connected to the link) to measure it's traffic statistics, this will allow you to see if for instance issues are being caused by a link bottleneck.
- Lastly, for the "services" which these users use, you can add Ping, HTTP(Exchange's OWA), DNS or Port sensors to confirm whenever your users are able to reach the required services/resources and the response time. The Ping sensor will aditionally provide packet loss statistics when configured for multi-ping.
If the network connectivity to this remote office is in a good stand, users should enjoy a fast experience, if not then concentrate on the performance of your services on your datacenter/main site, there you can deploy specific performance sensors for your services:
Exchange
Exchange Server Sensor
Exchange Transport Queue Sensor
Sharepoint
Sharepoint Process Sensor
Citrix
KB:How can I monitor Citrix environments?
Please check our extensive list of Available Sensor Types for further details.
Best Regards,
Add comment