Plantronics Manager Pro software-as-a-service allows customers to monitor, manage and distribute updates of their headsets across the organization while keeping track of which users are using which headset. Our application is located in 5 different regions, and handles 2 million end points.
Our main method for finding out that an error occurred, was to wait for customers to report problems. Once an error was discovered, we had to dig through log files to find its root cause and fix it. In some cases, the error would manifest in a different way on our desktop client, but it always leads us right back into the logs.
If we came across errors in our production environment, such as a NullPointerException, reproducing it to pinpoint when and where it happened within the code was a tedious process. If we came across a series of issues that cause a certain exception, we could spend weeks trying to find, debug and solve it.
This reactive process could lead to missing our release schedule, making our developers spend more time on low level tasks instead of developing new features.
A few months ago we rolled out a new version with some new features, and we experienced big performance issues in this new version. OverOps gave us value in those hard-to-find issues, that included detecting slow queries and identifying deadlocks within our code, which lead to speeding up the application’s response time.
OverOps also helped us uncover an issue with our older clients, that were not sending the appropriate required information to our APIs. We were able to track down those clients, identify what causes this issue and fix it quickly.
OverOps helps Plantronics get critical information needed to identify and solve errors, before they hit the users. OverOps also helps the developers be more efficient, in the sense that they can focus more on building new features versus debugging production issues.
We use the OverOps dashboard to monitor our application and servers. By doing so, we’re able to reduce the time it takes us to identify and fix critical production application errors. We’ve cut down the time it takes to resolve errors, and our developers are free to focus on building the product and adding new features, instead of wasting their time on debugging.