Komodor Reviews

Name: Komodor
Brand: Komodor
Rating: 4.4 (5 reviews)

4.4 out of 5

5 reviews
100% willing to recommend

104 followers

What is Komodor?

Komodor is the missing piece in your DevOps toolchain - offering one unified platform from which you can gain a deep understanding of all of your system events and changes. We integrate with all of your tools, monitor changes and alerts and organize information on a clear digestible dashboard and provide you with the right context at the right time.

Get the Komodor Buyer's Guide and find out what your peers are saying about Komodor, Amazon EKS, Rancher Labs and more!

Komodor is the #12 ranked solution in Container Management software. PeerSpot users give Komodor an average rating of 8.8 out of 10. Based on the analysis of the 5 most recent Komodor reviews, the overall sentiment is positive, with a sentiment score of 9.0. (The highest in the category). Komodor is most commonly compared to Amazon EKS: Komodor vs Amazon EKS. Komodor is popular among the large enterprise segment, accounting for 65% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a wellness & fitness company, accounting for 27% of all views.

Helped 816,406 peers since 2012

Featured reviews

Jacek Kisynski

Senior Staff Software Developer at Visier

There's nothing in particular that is wrong with Komodor. It's hard to say that there's something we would really like to see improved. I hope that the cost analytics and resource usage allocation areas will see further development. For example, where we can now see if the pods are over- or under-provisioned, I wouldn't mind higher-level development. I would like to see if we're utilizing nodes in the cluster, if pod allocation is optimal, how much idling we have, and whether we scale up and down efficiently. I would like to see them help us optimize costs further. Because, as our company grows and our clusters get busier and busier, any inefficiency is a lot of money wasted. That's definitely high on our wish list: anything that helps us track wasted resources.

Read full review

Mark Davydov

Director of Development Operations at Workiz Inc.

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.

Read full review

Carsten Skov

DevOps Engineer at a retailer with 1,001-5,000 employees

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.

Read full review

Komodor mindshare

As of November 2024, the mindshare of Komodor in the Container Management category stands at 1.2%, up from 0.4% compared to the previous year, according to calculations based on PeerSpot user engagement data.

Container Management

Key learnings from peers

Last updated Nov 21, 2024

Valuable Features

Komodor provides valuable features like service overview, historical and real-time data access, and instant event correlation for troubleshooting. Users benefit from multi-cluster centralized event timelines, deployment notifications, and comprehensive logging. The ability to overlay node and deployment events aids in quick issue identification. It helps pinpoint resource allocation issues with real-time metrics, simplifies Kubernetes troubleshooting, and speeds up onboarding. The ease of access to timelines and logs is particularly appreciated.

"The most valuable aspect is the speed with which I can narrow down what's going on. Usually, I look at the overview of events and then the timeline of an event and the status of the logs to quickly check what's happening or what has happened."
"The event timeline has been super helpful, enabling us to overlay node events in the same timeline as deployment events... That helps an engineer very quickly troubleshoot without having to do too much digging."
"Komodor's multi-cluster centralized event timeline is the most valuable feature."

Room for Improvement

Users suggest improving Komodor's installation process and enhancing visibility into clusters and nodes. They desire more configurability and a user-friendly alert interface. Performance issues, particularly in log retrieval and service visibility, need attention. Users express concern over excessive access permissions and desire integrated metrics for better usage insights. Improvements in cost analytics and resource usage allocation are also important, as efficiency in node and pod management could reduce waste.

"I hope that the cost analytics and resource usage allocation areas will see further development. For example, where we can now see if the pods are over- or under-provisioned, I wouldn't mind higher-level development."
"One thing we don't have visibility into, which I would love to have, is metrics, such as user logins and usage. It's really hard to know what people are doing when I don't have any metrics on that directly."
"I like the alerts that Komodor provides, but I think the alert interface could be improved."

Pricing

"Other options pop up, but Komodor's pricing works well for our use case. It's fair, and we appreciate it. A lot of other vendors price their solutions in a way that would cost us disproportionately more money than they should. Komodor's pricing is reasonable in the way they calculate usage and value."
"The licensing model is fine. It is per node, which is good, but the pricing is high. Currently, I am fine with it, but I am a little concerned about the pricing as we scale. So, it is on the higher end. On a scale of one to ten, where ten is the most expensive, Komodor is a seven."
"We pay according to the number of resources we have; if we are a small start-up, we have fewer resources and thus pay less."

Popular Use Cases

Komodor is primarily used for troubleshooting and visualizing workloads in multi-cluster environments. It aids operations staff and developers by simplifying Kubernetes monitoring and troubleshooting tasks. Users appreciate its ability to visually represent deployments, replace the verbose Kubernetes Dashboard, and offer insights without direct cluster access. It’s a key tool for ensuring cluster reliability, optimizing setups for cost-efficiency, and enabling developer interaction with Kubernetes through alerts and accessible monitoring workflows.

Service and Support

Komodor’s support team is responsive and effective, resolving issues promptly, often within 24 hours. They maintain a shared Slack channel and offer an app Help feature. Although generally fast in their response, there are occasional delays for West Coast operations due to time zone differences as their team is based in Israel. Customers appreciate their approachable and friendly service, and value the engagement with their feedback. Overall, clients find satisfaction in their interactions with Komodor.

Deployment

Komodor's initial setup is praised for its simplicity and speed. Multiple users mention that deployment is straightforward and can be completed in minutes. It often requires minimal personnel, with many setups handled by one or two individuals. Kubernetes and Helm chart usage contribute to the ease. Maintenance involves occasional updates, typically due to frequent releases. Users appreciate the immediate value upon going live, impressing teams with its effectiveness and ease of implementation.

Scalability

Komodor shows scalability in various environments, being used in multiple clusters and accommodating a wide range of users. Deployment across different organization sizes—from small to large—suggests effective scaling. While some observe potential lag issues with numerous nodes, many acknowledge its ability to expand without problems, rating it highly. Most users assert confidence in its ability to handle scaling demands, indicating a positive scalability perception without major concerns.

Stability

Users find Komodor mostly stable, with minimal issues over the year, aside from a small outage. Some experience intermittent lag and slow queries, possibly due to design adjustments to handle data. While some intermittent lag is noted, others report no issues, even suggesting stability improvements were unnecessary. Stability is often rated eight out of ten. Multiple users have commented on varying speeds, with the platform sometimes performing slowly and other times quickly.

These insights are based on the in-depth reviews provided by peers to help you make a better buying decision.

Download our Komodor Buyer's Guide for additional reliable information.