Case Study: Splitit Cuts Failed Deployments by 45% with Komodor

A Komodor Case Study

Preview of the Splitit Case Study

Splitit Cuts Failed Deployments by 45% With Komodor

Splitit, a financial services company processing millions of transactions for e-commerce merchants, was using Jenkins for CD and NewRelic for monitoring, but its DevOps team still lacked visibility into buggy deployments that appeared successful on the Jenkins dashboard. The team needed better insight into deployment failures, crashed pods, and fast access to logs so they could troubleshoot issues more effectively and support a shift-left approach.

Komodor added a unified troubleshooting layer across Splitit’s Kubernetes environment, enriching deployment data, alerting the right teams in Slack when failures occurred, and linking directly to relevant pod logs and historical health information. With Komodor, Splitit reduced failed deployment rates by 45%, cut time to identify production failures by about 50%, sped up its delivery pipeline by 24%, and lowered MTTR by more than 50%.


Open case study document...

Splitit

Yuri Yeshurin

Software Architect


Komodor

2 Case Studies