What needs improvement with OpsRamp?

If we treat OpsRamp as an infrastructure monitoring tool, there are many positive aspects. However, when viewed as an AIOps tool, there are numerous potential additions. Currently, it performs infrastructure monitoring but has limited capability in application monitoring, which needs improvement. They are introducing observability as a feature where metrics, logs, and traces can be implemented, but this is currently in a primitive state that can grow over time. The platform is very stable, and the UI is excellent. However, regarding AIOps features, enhancements could be made to provide more value, such as dynamic thresholding and other capabilities that competitor tools have, such as LogicMonitor.

I would rate OpsRamp's support around eight out of ten. Based on this rating, I consider there is room for improvement in OpsRamp. Technical support should be improved, and I have noticed other areas in OpsRamp that could be improved or enhanced.

OpsRamp had shortcomings associated with its network capabilities. When my company introduced OpsRamp at a discussion, I saw that its network capabilities, which were not there, were in the process of evolving. When I was reading something yesterday, I saw that everything, like backup, configuration, automation, incident management, discovery, and service mapping, got enabled in OpsRamp. I need to see what other features are there in OpsRamp compared to SolarWinds, especially in network space.

There is room for improvement in the performance of the product. The main problem is with patch management. The actual problem we're facing is with the patch management feature. It's not real-time, which creates inconsistencies. The machine might say there are no updates available, while the OpsRamp agent reports that everything's patched. It's a mismatch. We recently started a new marketplace for clients where we manage patch management. We try to share knowledge with OpsRamp, but they don't have a rapid process for product enhancements. Our main pain point is the lack of engagement from the product team. If someone from OpsRamp could discuss our concerns, work on future enhancements, or even give us an estimated timeline (ETA), it would be a huge improvement.

OpsRamp cannot be scaled for big and large company deployments.

This is an emerging tool and they have tried to consolidate everything not always with success. Automation, for example, needs to be improved to simplify the use of libraries for a gen operator. They're trying to do everything at once, and as a result, some areas are weak. In the next release, I'd like to see an improved dashboard because the current one is very basic. Reporting could also be improved to make it more customizable. It would be helpful for us to see executive reports more frequently, ideally on a weekly basis. Customization is the most important aspect, and it's applicable to both dashboards and reporting.

What's lacking in OpsRamp is process automation, and if there is, I wish there could be more of it, other than just spikes, or it would be better if the alerts can be generated based on different matrices. That option is absent in OpsRamp at the moment, and it would be valuable if that could be provided in the solution, especially if there's any kind of security issue in the VM.

The function to search any particular device within this solution needs to be improved. Currently, the solution develops a lag when a search, or a comparison, is being carried out.

OpsRamp could improve the critical alerts. We have been receiving some false alerts when monitoring. For example, the alert shows the site is down, but when we try to do manual access to the URL, it's accessible.

There is definitely room for improvement. Not every tool, particularly OpsRamp, is 100 percent accurate. There are two features that I personally recommend the OpsRamp team look into. One example is a mature ITSM product. They currently have an internal ITSM. They also have contracts with third-party vendors such as ServiceNow and Service Desk, where you can integrate those applications into OpsRamp and use ITSM. OpsRamp has its own ITSM platform that if it could or would improve the performance of utilizing or the maturity of that particular ITSM for change management or incident management, it should really help an individual to kill two birds with one shot. Purchasing monitoring and alerting licenses allows them to use ITSM without spending the extra money to integrate other tools such as ServiceNow, or Service Desk, for example. The second area for improvement, in my opinion, is that because they are already cloud-centric, whether it is infrastructure, Azure or AWS, or on-premises platforms, they can create their own self-service portal and tie it up to any cloud in the sense that if I am a vendor who is willing to use any cloud in the future, I can just log into the self-service portal from OpsRamp and go ahead and deploy the resources from the cloud, such as building instances, adding storage, deleting storage, adding security, and so on. A single one-stop-shop for OpsRamp, a self-service portal where you could go ahead and deploy resources, enable monitoring, and create an ITSM portal for it. And, near the end, you can also make it so the patching is all done. It has been planned to be a one-stop-shop for everything. I would like to see two things. The first is a self-service portal for the cloud, any cloud deployments, and the second is maturity validation towards ITSM, internalizing OpsRamp TSM. As a result, instead of integrating with more mature tools similar to ServiceNow, people will use OpsRamp.