Share your experience using OpsRamp

The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.

Use our online form to submit your review. It's quick and you can post anonymously.

Your review helps others learn about this solution
The PeerSpot community is built upon trust and sharing with peers.
It's good for your career
In today's digital world, your review shows you have valuable expertise.
You can influence the market
Vendors read their reviews and make improvements based on your feedback.
Examples of the 83,000+ reviews on PeerSpot:

Muhammad Umair Gulfam - PeerSpot reviewer
Implementation Engineer at a computer software company with 201-500 employees
Real User
Top 20
Automates Azure resource monitoring and inventory management but slow with real-time patch status
Pros and Cons
  • "Most features work fine."
  • "We have 55 AVDs, and patches might roll out to 32-35 initially, with the rest taking a month or so. OpsRamp can't detect them all directly. Since clients want patches applied as soon as possible, we manually patch those remaining devices."

What is our primary use case?

The primary use cases were inventory management for Azure, integrated with different templates to monitor resource status, CPU, memory, etc. 

We also used it for Azure Virtual Desktop (AVD) patch management, but Windows Update doesn't support query filtering for AVDs, unlike regular servers. So, to update and track AVDs, we needed software or a tool to automate the process.

Initially, things were fine. However for the past two months, there were data discrepancies between OpsRamp and other reports. Support confirmed it was related to Microsoft patch rollouts, with some devices scheduled for later than others.  We have 55 AVDs, and patches might roll out to 32-35 initially, with the rest taking a month or so. OpsRamp can't detect them all directly.

Since clients want patches applied as soon as possible, we manually patch those remaining devices.

What needs improvement?

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.

For how long have I used the solution?

I have been using this solution for two years. I use Version 16.0.

What do I think about the stability of the solution?

Overall, I would rate the stability an eight out of ten. 

What do I think about the scalability of the solution?

We haven't really tested its scalability yet. We primarily use it for monitoring and basic device status checks.

Which solution did I use previously and why did I switch?

We used an upgrade management product. It's similar to OpsRamp in function, but it's native to the cloud providers like Azure and AWS. 

OpsRamp, on the other hand, is a third-party tool. We use it primarily as a monitoring tool. We apply templates to resources, gather data, and generate reports for clients. It's an agentless solution that collects data from hosts and sends it back to the portal for reporting and presentation.

How was the initial setup?

It integrated well with our ITSM tools, and everything seemed fine.

What other advice do I have?

Most features work fine, but I'd rate it a six out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Reseller
Flag as inappropriate
Global Director at a computer software company with 51-200 employees
MSP
Top 20
A cost-effective and easy-deploy single-platform solution, but it cannot be scaled for big and large company deployments
Pros and Cons
  • "The most valuable features of OpsRamp include a single pane of glass, event correlation, personalized dashboards, and a single platform solution."
  • "OpsRamp cannot be scaled for big and large company deployments."

What is most valuable?

The most valuable features of OpsRamp include a single pane of glass, event correlation, personalized dashboards, and a single platform solution.

What needs improvement?

OpsRamp cannot be scaled for big and large company deployments.

For how long have I used the solution?

I have been using OpsRamp for four to five years.

What do I think about the stability of the solution?

I rate OpsRamp an eight out of ten for stability.

What do I think about the scalability of the solution?

I rate OpsRamp a seven out of ten for scalability.

Which solution did I use previously and why did I switch?

I previously used Micro Focus. We switched to OpsRamp because it’s a cost-effective, single-platform solution that is easy to deploy.

How was the initial setup?

The solution's initial setup is easy.

What about the implementation team?

The solution's deployment took three months.

What was our ROI?

We have seen a return on investment with OpsRamp.

What's my experience with pricing, setup cost, and licensing?

OpsRamp is a cost-effective solution.

What other advice do I have?

OpsRamp is deployed on-cloud in our organization.

Overall, I rate OpsRamp a seven out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate