<< Back to all customers
Mykel Alvis
DevOps Engineer, Cotiviti

Production Monitoring Ecosystem

Key challenges and pain points:

We have an extremely distributed, domain-specific environment, with fast deployments, making it hard to keep track of new errors.

You need to know the minute something weird happens. You can't go searching through the logs after the fact and be effective.

Example problem that OverOps helped resolve:

10 years ago, I would have done absolutely anything to have what OverOps gives us in terms of state at the time that the event occurred, because that cuts down our debug cycles dramatically.

Our developers don't actually look at the production system themselves anymore, they just use OverOps.

What is so unique and compelling about OverOps?

Installation was super simple. Having that immediate feedback, what the code looked like, and what the variable values were, is critical for us. You don't have to recreate that particular problem. It's immediate.

In the absence of OverOps, debugging a distributed solution would have taken us days, weeks, maybe even months. But with OverOps, it's minutes, hours.

What does the future look like with OverOps?

The idea that you can report in real-time on exceptions in a running JVM based application is essential to our development process. My developers would probably get torches and pitchforks if I ever told them we're going to cancel your service.

Get Your First Error Analysis in 5 Minutes

Get Your First Error Analysis in 5 Minutes

Meet more customers: