Vivint Smart Home helps customers create a smarter home with intelligently designed products that simplify their lives.
Production Monitoring Ecosystem
Key challenges and pain points:
Before OverOps, when we needed to trace a sequence of events, we had to turn on all the high-level debug logs and follow the messages to make sure things were working. Sometimes we’d come across a generic exception, or see an exception too late and it would get lost in the logs, or the stack trace would not contain enough context to actually figure out what had happened.
Example problem that OverOps helped resolve:
Before using OverOps, there were a large amount of errors that were simply being ignored, which made our build process slower. It took a lot of time to make it stable and ready for launch.
When we installed OverOps, we immediately started seeing some critical errors that we didn't know existed, which led us to refine the product. That's ultimately what made our product stable enough to launch.
How has OverOps helped you solve these issues?
Our application includes data intelligence and machine learning, so there are a lot of pieces that are harder to detect and QA. We needed a way to ensure that we're providing a great customer experience because that's what we're all about.
OverOps gives us a complete solution, allowing us to detect where and when something happens and solve it quickly, without impacting our customers.
How are you integrating OverOps with your daily workflow?
With OverOps, we’ve cut the time it takes us to find and solve exceptions in our application. We have a firefighting channel where we publish these exceptions, as well as the ability to tie each message to a call bot. This allows us to monitor the application without searching and sifting through log files.