- OverOps helped BDEX deduplicate issues in their local environment, allowing them to resolve issues in minutes
- Thanks to OverOps, BDEX dev team doesn’t have to sift through logs to understand what happened in pre-product or production
Chief Technology Officer
BDEX is the first ever real-time Data Exchange Platform (DXP) with offices in New York, Seattle and FT Lauderdale.
Key challenges and pain points:
We used to troubleshoot problems using Log4J, but it failed to enable our team to easily reproduce and understand production issues.
If application state wasn’t logged, the only way to debug would be to change the logging, rebuild the product, redeploy it, and hope the same issue appears again. A very slow process.
Example problem that OverOps helped resolve:
With OverOps, we were alerted in real-time of a new application error within minutes of the deployment and easily saw the source code, application state, and what caused the exception (a null reference).
Within 5 minutes we had a code fix and re-released. It would have taken hours to detect and reproduce the same issue manually. OverOps is truly outstanding and a core part of our monitoring ecosystem.
“Within 5 minutes we had a code fix and re-released. It would have taken hours to detect and reproduce the same issue manually.”
What is so unique and compelling about OverOps?
OverOps has shortened defect investigation time many times over and has enabled us to ship code that is much more stable. It is the best tool for debugging Java in production.
“OverOps is truly outstanding and a core part of our monitoring ecosystem.”
Who uses OverOps at BDEX?
OverOps is a mainstay in our organization for monitoring all of our Java-based code.