Komodor Reviews

The service overview is definitely the most valuable feature. With it, I can see all the services and see if they're healthy or not without having to go specifically into each workflow individually. It has been immensely helpful for us whenever we've had network issues or other such issues. We've been able to use Komodor and see at a glance where there might be potential issues. It's great to be able to see the historical and real-time data with Komodor because you can see what happened to the workflow when you're trying to understand the current issues with that workflow. For example, you get in to work one day, and there's an issue for which you don't have any context as to what happened in the time leading up to the issue. Being able to see historically what happened, which versions were deployed, and what could have been changed is helpful. Komodor instantaneously correlates events and pinpoints issues. We haven't seen any delays. The overall visibility into our nodes is very good. Since we have quite a few nodes, it has been nice to have the overview of the nodes together with the historical view and suggestions as to what might be wrong. There were things that simply weren't apparent to us before we saw the issue in Komodor. We have been able to save a quarter to a half day of work in figuring out what the problem might be. We have been able to reduce our mean time to repair by about 20% to 50%. We haven't fully rolled out Komodor to our DevOps staff yet, but we're hoping to see a significant reduction in the time spent on production issues because we can push it to the first and second levels.

Komodor's visibility could be improved. I would like to have a better view of the entire cluster at any given moment. For example, I want to be able to see how my cluster is doing, how each service is functioning, and so on. I want to have a better understanding of what is going wrong. I would like to have a clearer view of the big picture. Komodor's visibility into our nodes is limited. The solution was not intended to provide us with a comprehensive overview, but rather to provide quick responses and troubleshooting. Komodor was designed to be more suitable for developers, so they could determine if something had gone wrong with their deployment or the services they are responsible for, rather than for the infrastructure team to conduct a deep dive.

I have used Komodor for two and a half years, and it has come a long way. However, I would say that performance could be improved. Sometimes, it takes longer than it should for developers to pull up logs or interact with the cluster. Komodor is aware of this issue and is working on a fix. Secondly, I like the alerts that Komodor provides, but I think the alert interface could be improved. It is not the most intuitive system in the world, and it can be difficult to set up. I think Komodor could improve the alert interface by making it more user-friendly. Finally, I would like to see Komodor add ServiceMaster visibility. This would give us greater insights into how our services interact with each other. This would be very helpful in troubleshooting problems, as it would allow us to quickly identify which services are affected when one service goes down. Komodor does not currently have this capability, but I hope they will add it in the future.