What needs improvement with Gremlin Reliability Management Platform?

While I have no complaints about Gremlin Reliability Management Platform, I believe the UI can be improved to enhance the developer experience for security engineers and DevOps engineers. Additionally, AI-driven root cause analysis could provide more visibility for SRE teams. I rate it an eight because we are still using it on a trial and error basis, and the pricing could be optimized for better cost visibility and ROI tracking. Otherwise, I believe it could achieve a ten. The experience with pricing, setup cost, and licensing is moderately good but can improve through options such as having a pay-as-you-go pricing model.

There are certain areas where I think Gremlin Reliability Management Platform can improve. I would certainly add features related to AI and GenAI for recommendations. While dependency identification works well seamlessly, deeper dependency intelligence is lacking. When you have deeper dependencies, reliability management can struggle with identifying those deeper dependency intelligences. Having the intelligence to deeply analyze dependencies will be very helpful. Regarding reliability scores, while those scores are good, having more actionable reliability scores is something I would recommend adding to the existing system. Initially, when I started with Gremlin Reliability Management Platform certification programs, I completed two certifications with Gremlin—one professional and another practitioner. While that certification has helped me, an easier onboarding and learning curve for bringing people into this program can be adjusted. That is one current gap I see. If you really look at the cost-benefit visibility, it is not very evident by using Gremlin Reliability Management Platform. If Gremlin Reliability Management Platform could help realize that and bring in visibility regarding the cost versus the benefit, that is the reason I provide a score less than ten. From a standpoint of simulating complex real-world failures, I believe there is still a gap concerning gap identification. Currently, Gremlin Reliability Management Platform mainly focuses on infrastructure-level failures and does not really simulate business logic failures, data corruption scenarios, or potential failures across regions. One of the key elements needing improvement with Gremlin Reliability Management Platform is the limited team workflow integration I see in my organization. Collaboration and limited team workflow integration are areas I would highlight as needing improvement.

Gremlin Reliability Management Platform is already good, and I do not see any improvements in it. I do not want to add more about the needed improvements for Gremlin Reliability Management Platform, even small things, and I do not wish for anything to be a bit different.

Gremlin Reliability Management Platform can be improved as the pricing is a bit expensive and the learning curve for beginners is a bit difficult. It is not easy to get along with, and we need pretty good time to understand and grasp those concepts before we can use it. The infrastructure also needs to be very mature; it should be set up properly and that takes a lot of compliance and regulation time.

I think that it will be important to have resources to perform self-directed studies on Gremlin Reliability Management Platform as an improvement. There is a small and fast and simple certification, but if they add possibilities to learn and get certified for free, it would be great because it is very powerful and the documentation is very high quality. However, I do not think that only with the documentation you can reach all the complexity of the tool. Some learning paths, free and by webinar, could help. I think it would be useful to have some integration with Splunk or other log collectors, or maybe in the future, the ability to link Dynatrace or any other observability platform.

Gremlin Reliability Management Platform can be improved by introducing open-source features. It currently has a paid version, but introducing open-source features could encourage more people to use and try it. The user interface is great, the integration is smooth, and Gremlin Reliability Management Platform has a fantastic support team that helps us a lot in many cases.

I think Gremlin Reliability Management Platform can be improved by integrating with more AWS services or GCP services. I also think we can somehow integrate it with machine learning or perhaps some sort of AI by utilizing natural language processing so that it will be easier to interact with non-technical persons as well. We need more services and more prebuilt plugins for Gremlin Reliability Management Platform, especially for stress testing. I want to see how it can be integrated with machine learning, particularly on the NLP side. If we can integrate it with natural language, could we talk to Gremlin Reliability Management Platform and have it configure some of the basic settings so that non-technical persons can also work on Gremlin Reliability Management Platform-like tools? Even a QA person should be able to integrate it without needing any DevOps or cloud expertise.

I have no recommendations for how The Enterprise Reliability Platform can be improved.