This lets you generate a customized trace results page, add comments, and then send it to the people you support. One of the PingPlotter features that Ruby takes advantage of daily is LiveShare. Here, you can see the connection’s performance over a 24-hour period, along with signal quality, and the top three most significant events that occurred. This view shows all of the hops along the traceroute. To get more details, zoom in on the event. Possible culprits, such as local bandwidth saturation.Average latency, packet loss, jitter, and the mean opinion score (MOS).Quality score percentages during the event.These are shown as event cards and highlighted in purple on the timeline graph. Insights also probes the data itself to help support take the right action.Īlong with determining signal quality, Insights will find three most significant events. You can scrub through days’ worth of data in an instant to find incidents and diagnose issues. Insights is PingPlotter’s network troubleshooting assistant that looks at your trace results and identifies where (and in some cases, what) problems are impacting a device’s connection. (Read Ruby’s full case study here.) Examining A Trace With Insights “We had one incident where we could tell that two of our receptionists lived in the same exact house,” chuckles Decker. What’s more, PingPlotter can zone in on the source of the problem - by state, city, even the neighborhood. WAN problems (probably the ISP in this example) begin in the middle. Show clients and ISP’s - along with less technical people - real-time results with LiveShare.Use Insights, the network troubleshooting assistant, to help frontline support handle more complicated tickets.Unravel problems quicker and with more efficiency thanks to automated alerts.Diagnose connection issues for anyone, anywhere from a central dashboard.An IT team member suggested they try PingPlotter. With 750 employees working remotely, Ruby had to find a way to pinpoint connection problems for all of their remote receptionists from one central location. Ruby receives an astounding 40,000 calls every day. ![]() Is it our network? Is it the rep’s ISP? Do we need to send them a new computer? A lot of going back and forth.” “It would take us a week just to figure out what the problem is. “Most of our tickets are reps saying that ‘my calls aren’t coming through clearly,’” says Wendy Decker, the Desktop Support Manager for Ruby Receptionists. You can find issues - like packet loss, high latency, and bad jitter - fast. We thank PingPlotter for being a sponsor.Īn internet connection monitoring tool, PingPlotter constantly tests the connection from the end-user’s perspective, provides visual proof of the problem, and recommends how to solve it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |