What is our primary use case?
I use
Komodor for troubleshooting the platform, focused on tracking logs and also things like crashes and configuration. We use it in our
Kubernetes in the CI/CD pipeline.
After a new deployment, sometimes the pod crashes and fails, so we use Komodor to open it in the timeline and see the deployment, the config, and understand the config that was changed right before the failure. For example, once we deployed something and the pod crashed, we tried to understand why it crashed, and thanks to Komodor, we found out that the environment variable was missing. In conclusion, we use Komodor to trace a production issue in the deployment, and the timeline showed the configuration change that caused the pod crashes, allowing us to roll back immediately.
Komodor also provides us the ability to see all the services we have, giving us a full picture of everything. It helps us understand why our CI/CD pipeline was not stable. Our cluster changed, we found new images version deployed, and that was a real bug. Thanks to Komodor, we found this flaky situation in our CI/CD and fixed it.
What is most valuable?
The best features Komodor offers include visibility, the ability to see your services, and control your pods.
Visibility and the ability to see services and control pods helped our workflow significantly by allowing me to debug quickly. For example, we use it for debugging. I used to jump between logs and do things manually, and that took time. That is how we worked in my previous position. But in this company, we use Komodor, and I see everything in one timeline. I immediately understand what changed, and it takes me straight to the root cause.
The investigation is reduced thanks to Komodor, which makes it more clear to understand the whole picture. Otherwise, I would need to curl every request to check if it is alive or just run ps to understand if it is alive. But with Komodor, I see everything in one timeline.
The real impact in terms of time savings is in debugging. For example, instead of spending thirty to sixty minutes jumping between logs and different commands, I can usually define the root cause within a minute by using Komodor timeline. We can easily see what has changed between deploys, allowing us to pinpoint the root cause directly and removing the guesswork so I can focus on the actual issue.
What needs improvement?
Perhaps a deeper integration with logs and metrics would help. Today, I still need to jump to an external tool such as a logging or monitoring platform to fully understand the issue. Although Komodor is really good, having richer logs and metrics directly inside Komodor would reduce context switching. I really appreciate the timeline; it is great, but it still requires manual analysis. If Komodor could highlight it or perhaps give some artificial intelligence insights, that would be helpful. Sometimes I need to spend a lot of time to find specific issues, especially when I have different microservices that I need to drill down to find. If there were artificial intelligence insights available where I could write down my problem, it could really improve the experience, especially for junior developers who struggle since they do not know exactly what services are available.
Solving the issue of reducing the switching between tools would be beneficial. I still need to switch tools, not so much, but I do use different logs such as Splunk.
For how long have I used the solution?
In the current company, from the day I arrived, we have used Komodor. In other companies, I used different solutions and various logging tools.
What do I think about the stability of the solution?
Komodor is stable.
What do I think about the scalability of the solution?
We use Komodor with many services, so I believe the scalability is really fine.
Which solution did I use previously and why did I switch?
In this company, we did not evaluate any other solutions besides Komodor; I came in and it was already in use. In my previous company, we used
Coralogix, which is similar but different.
What was our ROI?
It saves us time in investigating, providing a clear root cause on a timeline, which is a significant time-saving aspect.
What other advice do I have?
My advice for others looking into using Komodor is that it helps you quickly find a root cause in
Kubernetes without guesswork. That is my belief regarding its effectiveness.
If you have many services, frequent deployments, and constant changes, Komodor will be a great solution for understanding the root cause when something goes wrong. You can see all the changes in a timeline, figure out the crashes, reduce the time investment in understanding problems, and minimize the need to jump between different log tools. I would rate this product an eight out of ten. Therefore, I recommend choosing Komodor.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other