Komodor

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.

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.

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.

In the current company, from the day I arrived, we have used Komodor. In other companies, I used different solutions and various logging tools.

Komodor is stable.

We use Komodor with many services, so I believe the scalability is really fine.

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.

It saves us time in investigating, providing a clear root cause on a timeline, which is a significant time-saving aspect.

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.

My main use case for Komodor  is visualizing the workloads that we deploy onto the Kubernetes  infrastructure across all three major clouds using Azure , EKS, AKS, and Google Cloud . We use Komodor  to ensure application teams and other teams can visualize their applications running on the Kubernetes  infrastructure.

A specific example of how my team uses Komodor to visualize those workloads is that there are application teams who do not have access to Kubernetes jump hosts, so they use Komodor for accessing their applications from the Komodor UI. They use Komodor on a day-to-day basis to check if their workloads are running properly or if there are any issues. If the workloads are not running and are experiencing issues, they use Cloud AI integrated in Komodor for debugging the logs.

This is the main task that we use Komodor for, and one additional benefit is that it is also helpful for platform and site reliability engineers to check how many clusters are up and running and how many clusters are accepting the workloads from the users.

One of the best features that Komodor offers is Cloud AI, which debugs all the logs and gives the exact root cause for the issue. From there, we know we do not need an engineer who is an expert in Kubernetes to debug the issue.

Cloud AI has definitely helped my team by saving time, not in a single instance but in multiple cases where we have used Cloud AI for debugging issues in the Kubernetes pods.

Komodor has positively impacted our organization. Since adopting it, all the issues we faced while managing Rancher  are gone, and we are seeing 100% availability for Komodor.

100% availability with Komodor means there have been improvements in uptime and productivity. For instance, when application teams want to deploy their applications, if Rancher  is not up or running, the deployments usually fail at the deployment stage. In the case of Komodor, there have been no such cases reported after adopting it. We saw 100% uptime most of the time, except for some issues with AWS  outages.

There are some features related to the platform that are missing in Komodor, such as Tigera  status or CNI pods. Including these features would be helpful for platform engineers.

I have been using Komodor for managing workloads on Kubernetes and Kubernetes-related infrastructure for the past nine to twelve months.

Komodor is stable in my experience.

Komodor is very highly scalable in terms of infrastructure and in terms of the number of nodes we use.

Customer support from Komodor is very good. I would rate the customer support from Komodor a ten out of ten.

We previously used Rancher, and we faced issues with availability, which is why we switched to Komodor.

We saw around ninety percent ROI using Komodor.

I am not involved in the pricing, setup cost, and licensing for Komodor, so someone from my team will take care of that. Compared with Rancher or any other tools, Komodor is priced cheaply and available at a fair price.

We did not evaluate any other options except Komodor before choosing it.

I would like to add that there are other features in Komodor as well. Whatever application teams need, all the features in Komodor are available for visualizing the Kubernetes environment, so not just one feature but everything is helpful for application teams.

My advice for others looking into using Komodor is that if their main intention is for 100% availability for their application teams, Komodor is completely suitable for their needs.

Overall, Komodor is a very good platform for managing Kubernetes-related infrastructure, and as of now, my experience with Komodor is very positive. I would rate this review a nine out of ten.