Falcon Social - The most unified customer experience platform.
Production Monitoring Ecosystem
Key challenges and pain points:
WLogs are often filled with “noise”, and there is a lack of context with what variables (and values) were processed when the error occurred.
Sometimes you have no clear view of what happened, and therefore errors go unresolved.
Example problem that OverOps helped resolve:
The first time we used OverOps was for a new backend application that when released immediately had errors and customer impact. By inspecting the contextual values OverOps provides, we were able to see that the frontendclient provided invalid data/params.
What could have taken hours/days to figure out using logs was resolved within an hour.
What is so unique and compelling about OverOps?
We still use logs but OverOps provides much more information about the errors that occur. Seeing the context (source code and state) of errors within our own codebase, is invaluable.
No more log tailing and trying to reproduce the same issue over and over again.
Who uses OverOps at Falcon Social?
Our developers use OverOps as part of their monitoring tools and debugging process, and we plan to spread to more applications. The contextual view of why an error happened helps us solve errors faster, often before users reports them.