OpsRamp Reviews

Currently, my use case for OpsRamp is using it as an infrastructure monitoring tool for customers, where we can provide infrastructure monitoring as a platform. We can have AI appended to those monitoring capabilities where we can have correlations, alert prediction, some automations, deduplication, noise reduction, and these features predominantly.

What I appreciate most about OpsRamp is that while many tools in the market provide standard monitoring, OpsRamp stands out as a differentiator by providing AIOps features, including correlation, deduplication, and automation where we can run RBA scripts on top of created alerts. Additionally, it has multiple out-of-the-box integrations available where we can connect to various external tools and integrate them for orchestration between systems.

As a monitoring tool, compared to standard monitoring tools, the benefits include increased productivity and significant noise reduction through its correlation capabilities. The comprehensive monitoring capabilities cover infrastructure monitoring, synthetics, network monitoring, and integrations. It can act as a monitor of monitors, which we currently utilize when customers have multiple monitoring tools in their landscape. OpsRamp can integrate with these monitoring tools and create leverage by providing monitoring as a comprehensive solution.

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 have been using OpsRamp for the past four years.

We have discussions with both the customer success team and the support team. When we encounter platform challenges or issues, we raise a ticket. Previously, when it was smaller and not acquired by HP, support was more primitive. Now that it is HP's OpsRamp, things are improving, but there is definitely scope for better support.

The availability could be improved. With other tools, there is dedicated support for specific customers or implementation partners and MSPs. Having a dedicated firefighter team for each MSP would be beneficial, as we are handling around 30 to 35 customers where we are implementing OpsRamp. With the current generic support system, issue resolution takes considerable time. I would rate their support at seven out of ten.

Positive

I have worked with ignio initially, a tool made by TCS that functions as an AIOps tool performing automation, RPA, and monitoring. I have also used Zabbix, SolarWinds, and OpsRamp. Currently, I am being trained with LogicMonitor.

The initial setup is very straightforward. Compared to other monitoring tools, the initial configurations in OpsRamp are simpler. However, regarding AI capabilities, one definitely needs substantial hands-on knowledge of the tool to provide value to the customer.

We have a partnership where we act as an MSP and implementation partner to HP's OpsRamp.

We are implementing OpsRamp successfully as it is an excellent tool for infrastructure monitoring for a standard customer base. However, overselling features can complicate implementation. It is important to stick with available features and provide customers with clear, precise details about what can and cannot be done to avoid anomalies.

I use the capability for predictive analytics. The feature is effective in its current form. OpsRamp provides prediction features on the alerts themselves by analyzing data from created alerts and predicting future alert creation. However, it does not predict utilization or forecast utilization from the metric details collected for each monitored parameter.

The flexibility of being deployable both in cloud and on-premises is beneficial as it is a SaaS platform that doesn't require extensive infrastructure. You only need gateways in your customer landscape to operate. Compared to other tools with on-premises setups that require managing numerous servers, this makes it more cost-effective for implementation teams.

I rate OpsRamp 8 out of 10.

I use the cloud version of OpsRamp, and that is my main use case; we do not use it on-premises for other purposes.

I find the features of OpsRamp valuable, and in particular, I use OpsRamp's multi-tenant architecture for managing large-scale operations.

The multi-tenant architecture capability of OpsRamp has helped me streamline and improve the processes within my organization.

I have utilized OpsRamp's capability for predictive analytics, and it has been important in fostering collaboration between my IT and development teams under DevOps methodologies, where applicable.

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.

I am a customer of OpsRamp, and we have been using it for almost seven years.

The initial setup was straightforward for me, although it took a lot of time. As for deployment, OpsRamp is indeed a hybrid model, as we use both cloud and on-premises solutions.

I would rate the stability of this solution seven out of ten.

I use the cloud provider and would evaluate the scalability of OpsRamp in my experience as adequate.

I have utilized other solutions before OpsRamp for these use cases. It does not necessarily have to be cost-wise, but there are tangible benefits and positive impacts of OpsRamp that I have experienced.

Before choosing OpsRamp, I evaluated DataDog, and I participated in the initial setup of OpsRamp.

I find the licensing model convenient and clear enough, and I have seen a return on investment with OpsRamp.

I share the impression that OpsRamp pricing is fair; it does not strike me as expensive, and the licensing model is clear enough.

I am a senior system engineer at Micron Technology. Overall, I would rate OpsRamp eight out of ten as a product.

We are working with one of the customers on a tools consolidation project. There are multiple monitoring tools, and I am comparing OpsRamp and SolarWinds to see which one is better to consolidate. There are multiple different products, like seven or eight tools for different monitoring purposes, that just want to have a single platform.

We are working on the OpsRamp for many customers. I am using the tool in manufacturing as a line of business, but it is purely for IT purposes.

Some of the features in OpsRamp are a little more visible in terms of a dashboard, but I don't see them with SolarWinds. OpsRamp has its event correlation, but I don't think SolarWinds has it. When it comes to NPM, NCM, or NTA, I won't discount SolarWinds' capabilities, but OpsRamp is still evolving in that space. I have been comparing the high observability of SolarWinds versus that of OpsRamp. For a fair comparison, I started comparing the high observability of SolarWinds and OpsRamp. Some of the features in SolarWinds, especially on the network side, are good, but in OpsRamp, a single pane of view, containerization, monitoring, and a single pane of glass view are good.

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.

I have been using OpsRamp for eighteen to twenty-four months. My company has a partnership with OpsRamp.

It is a pretty stable solution. I didn't see stability in SolarWinds.

It is a scalable solution. The integrations were not there for the product I saw when it was acquired by HP or before when it was not HP OpsRamp and just OpsRamp. Mostly, all industry technologies can be integrated.

For customer service, I won't be able to rate SolarWinds at all since it was pathetic, but OpsRamp was better. I rate the technical support an eight out of ten.

Positive

The product's initial setup phase was straightforward since it is a SaaS product. Even the hardware, what I need are just VMs, so not even heavy resource hardware. I take a gamut of 3,500 elements, and I can run it on four or five VMs. If I go with SolarWinds, it requires a little bit of heavy resources. It also requires an SQL database meant for enterprise. If I go with two cores, it will cost me 15,000. As per the high observability resource requirements, it requires heavy resources, especially on SolarWinds.

I have seen within my organization, the implementation could be done in two to two and a half months. From day one, the automation started, and the entire process, based on the state, the minimum is one and a half months. The maximum they did, the professional services did the implementation and the migration in less than three months.

We saw a lot of ROI on OpsRamp when we did the consolidation, including SolarWind. SolarWinds was replaced in many places. We have seen a visible ROI and efficiency.

OpsRamp's automation capabilities have improved efficiency since the tool offers runbooks of Ansible, Python, PowerShell, and Perl. With automation, I haven't reached the stage where I can start comparing the automation capabilities yet. I am reading through the tool document, and I am looking at its observability, monitoring, and what parameters are being monitored. In SolarWinds, the dashboards are missing and don't offer a single pane of glass view.

AI observability is the key in OpsRamp product and it works well. Some of the native scripts get deployed on day one, and we can deploy some of it. From an automation perspective, if there is some use case that got deployed, it works flawlessly. Some issues are common in any of the tools even if you deploy it a 100 percent, but barring that, the rest of the thing offers 90 to 95 percent efficiency.

I would recommend OpsRamp to others.

I rate the tool a nine out of ten.

We use OpsRamp to set up a digitalized solution within my organization. 

We use it for set validations, monitoring automation, noise reduction, operational efficiency, and other similar purposes.

Event Management and Hybrid IT Infrastructure Monitoring, Alert Reduction, Higher efficiency and reduced complexity by consolidating
multiple tools, Increased Productivity, IT Process Automation

Personally, I like their monitoring and alerting tools. I have also used the OpsRamp ITSM tool.  It greatly assists small and medium-sized businesses in using the ITSM, alerting, and monitoring features. You can also use patch management.  These three features are beneficial. It is also user-friendly.

When I say we're trying to use monitoring and alerting, we use it for hybrid infrastructures and application transaction monitoring within OpsRamp, which could be our organization's internal environment, infrastructure environment, or external infrastructure environment. It's a mix of internal and external factors. Furthermore, we use it for hybrid infrastructure monitoring and application monitoring in general.

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.

I have been using OpsRamp for approximately three and a half years.

We are using version 12.0.

Both Azure and Amazon Web Services users can get assistance from us. We have both cloud versions of it available. These are the SaaS versions that are available and specifically used with Azure and AWS. Currently, it is on a multi-cloud platform.

When it came to the stability of the tool and technology used for OpsRamp, we had no complaints as an organization. But, aside from those two recommendations, everything is working as expected.

OpsRamp is a scalable product. 

I currently have 49 customers in my organization, it can be easily scaled. Everyone seems to be pleased with it.

I am not saying 49 customers are using it from my end. I'm claiming that we've adopted 49 customers internally. We have 49 internal customers who use our OpsRamp platform. To come in and place those queries or support questions there.

I would rate their technical support a four and a half out of five.

Positive

I have previously used IBM ticketing and monitoring tools. I was a former IBMer. I also use ServiceNow and Jira to some extent to go into detail about it. In addition, I was involved in the development of my own CMDB in the sense that change management databases for the organization.

I can be of assistance in those areas, not just monitoring and ticketing, nor just those tools. I have used tools such as Zerto, Veeam Backup & Restore, PlateSpin, Racemi, and other migration tools that help migrate environments from on-premises to the cloud.

OpsRamp's initial setup is very straightforward. Because everything is prepared, a recent college graduate can complete this installation. All you need to do is define your workflows. If you understand the workflow, you can define it and get through it quickly.

It took us about a week to fully comprehend the OpsRamp deployment.

Deployment is quite simple. However, defining the workflows and the complexity of the security rules, as well as everything else, most likely took a week or a week and a half. Aside from that, it was quite simple. 

We also had help from OpsRamp to educate us on how quickly we could deploy.

It was completed by me, internally, by myself, and by my team. However, we eventually had support from them to assist us. We called when we are stuck with something, and they did a screen share with us to show us how to correct the problem, and that is what we did.

Definitely. Yes. You are getting your money's worth. It's a good return on your investment. This is what we have achieved, 90% alert reduction, 70% of manual, routine IT processes now automated 50% increase in team efficiency and productivity

It all depends on the organization. However, my company has paid for a yearly subscription. It's not a subscription; it's more of a license. It's known as a perpetual license. 

You pay it for a year and you'll have full access to the entire platform, not only for monitoring and alerting, you will have access to the entire platform, and whatever technology they develop will be made available to you.

In terms of pricing, I would say it is more of an economical range.

There are technically six vendors with whom we conducted a proof of concept. It could be OpsRamp, Zendesk, ServiceNow, Service Desk, Zoho, or another product. There are six of them, and we believe that only a few are too mature, such as ServiceNow, Jira, and OpsRamp.

Aside from technology and maturity levels, we also considered the cost. 

When it comes to the maturity of the product similar to ServiceNow and Jira, it is 90% to 95% mature. It is, however, more efficient. 

We thought OpsRamp was more efficient. It not only provides a ticketing tool, for monitoring and alerting. For example, an individual who purchases the licenses can gain access to OpsRamp monitoring and alerting. It will also have access to OpsRamp ITSM, and gains access to OpsRamp patch management.

It can also be used for authentication, authorization, and patching in the same way that BladeLogic deployment can.

We felt there were more advantages to focusing on a single dedicated tool, such as ServiceNow. ServiceNow is extremely expensive. In terms of monitoring, alerting, ticketing, and other similar tasks, I believe OpsRamp outperforms ServiceNow. OpsRamp is capable of working on a multi-tenancy architecture which is actually beneficial to us.

I would recommend performing a proof of concept with your problem statement to gain a better understanding to how to monitor one or two applications. It is also important to understand whether it is intended for large corporations or mid-sized businesses.

If you have an ITSM from a different vendor and are only coming here for monitoring, you should consider it. However, if you don't have anything in mind and have a requirement for ITSM, OpsRamp, security patching, or operating system patching, you'll need to conduct a POC, validate the results, compare and contrast, and then use it automatically. 

OpsRamp would undoubtedly be chosen solution, by a person performing the POC.

I would rate OpsRamp a nine out of ten,because I was able to reduce alerts by 90% in my environment, and roughly 70% of manual routine IT processes are now automated as well as a 50% increase in team efficiency and productivity. 

These are my benefits, where I can integrate my incident management, change management, and ticketing system into my monitoring environment and get better application usage. Whoever has those requirements should seriously consider incorporating OpsRamp into their environment.

We use this technology internally to some extent. We have not gone to a high level of external use. However, we are currently using 90% of our resources internally and 10% of our resources in the external environment. I would see a consumer if I were using it internally. If I ask a customer to use my product, I would consider 10% as a reseller and 90% as internal usage.

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.

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.

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

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

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

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.

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

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

This solution provides predictive analysis and interconnection between tools. For example, when there's a database connected to a specific application that's hosted on a particular web server with a particular UI. We can create our own topology map which shows the interconnection between nodes. I'm an implementer and consultant.

Predictive analysis is the most valuable feature. It's very clear in informing us what issues to expect in the future and when they will occur. This tool provides us with deep machine learning, which is really great. Correlation is another great feature of this solution where we already have service maps on topology maps. There is an interconnection between the tools. If there's a problem on one particular node, we can fix the issue quickly. In traditional monitoring, we were getting around 10 to 15 events at a time and it was hard to know what to fix first. OpsRamp gives us a ready-made root cause analysis directing the operator where to go. We see such beautiful things nowadays in AIOps. This tool is a market leader. 

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.

I've been using this solution for 18 months. 

We haven't had any stability issues. 

The solution is scalable. 

Customer support is responsive. They proactively schedule regular meetings with us, providing a few check points, and then notifying us what to expect in the next release. 

Positive

We used BMC products as well as Moogsoft a few years back. It's all about the complexity. BMC is way more complex than OpsRamp because it's on-prem with interconnectivity and support issues. Moogsoft is a good tool but its algorithms are complex. As a layman, operator or implementer, using the solution becomes very time-consuming. With OpsRamp, the algorithms and the way they present the inputs are very relatable and easy to understand.

The initial setup is reasonably straightforward. The solution is SaaS so it doesn't require any attention to what's going on in the background, and which components are up or down. The product has good features in the cloud and we've had almost no downtime since implementation. That's very important because it makes our lives as implementers, way easier. I can focus on where we can improve instead of wasting time fixing backend issues. If the prerequisites are in place, core implementation can take just one or two days because there are only a few things that need to be in place. 

I'm not involved with the licensing but I believe that this is an affordable solution. 

I rate this solution eight out of 10.

We have multiple customers, and we manage their infrastructure on Microsoft Azure, so for monitoring, we use OpsRamp, and we have multiple thresholds applied to multiple customers' resources. We also use OpsRamp for inventory management.

We have multiple data centers for multiple customers, and they have their data centers on Microsoft Azure. For example, multiple WebEx and virtual machines running multiple web servers, plus different automation accounts and virtual network gateways are there. Our customers have multiple complex environments, so what we've done is integrate those environments with OpsRamp then we put thresholds on different resources. OpsRamp monitors those resources, and if there are spikes because of 95% CPU utilization or usage, the solution generates the alerts, and those alerts are sent to our data tool. Once we receive the alerts, we escalate those notifications to our customers.

The feature we found most valuable in OpsRamp is alert generation because whenever there is any kind of spike on any virtual machine, the solution generates alerts based on the thresholds we implemented. We have integrated our ideas and tools with OpsRamp, so alerts are generated, then we notify the customers. That's the main feature we like about OpsRamp because we don't have to monitor each resource. Instead, OpsRamp does the monitoring for us, and it generates the alerts based on the thresholds.

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.

I've been using OpsRamp for one and a half years, and I'm still using it.

OpsRamp is a stable solution.

OpsRamp is a scalable solution.

We found the technical support for OpsRamp very helpful. Last week, we created a support ticket because we were facing an issue with one of our customers. The user was with our onshore team, and he was unable to access his account because it was a newly created account that required MFA and SSO. We created a ticket, and the support team worked with us and resolved the issue. The team was able to identify the main issue, so we found OpsRamp support very helpful.

As an MSP, we have multiple requirements and tools because of Azure Expert MSP, and that requires passing the Microsoft audit. We contacted the Microsoft customer support team, including the OpsRamp support team and the teams for the other tools. Whenever we raised a concern, the OpsRamp support team resolves the concern and improves on the functionalities. Recently, we required the automation of alerts in OpsRamp, particularly self-healing alerts for a certain period, so OpsRamp support gave guidance and enhanced that functionality, so we could achieve that target.

I didn't use another solution before using OpsRamp.

For a technical guy, setting up OpsRamp is straightforward because you just have to first integrate it with your ideas and tools and with the infrastructure of Microsoft Azure or any other public cloud. Once that's done, you can simply integrate your environment and onboard your customers on OpsRamp, so it's a pretty straightforward process. The initial setup for OpsRamp isn't that complex.

I don't have any idea about the licensing cost for OpsRamp, but I just know that its pricing is based on the resource count for each tenant.

My advice to anyone looking into using OpsRamp is that if you only go with Microsoft Azure, then you can either calculate the total count of the resources, and you can also see the matrix by going into each of the resources, for example, the virtual machine. If you want automation in terms of the spikes in any virtual machine, however, it's best to use OpsRamp. Spiking could be triggered by a cyber attack on the virtual machine or web server, so OpsRamp can automatically notify you of that incident. I would also recommend OpsRamp to other users and companies for the complete monitoring and complete visibility of resource details, even for the past three months. You can customize the dates to see your required information. You can also have multiple reports generated from OpsRamp for a specific time or a custom period. Use OpsRamp if you want complete visibility over your resources in Azure.

As there's always a possibility for improvement, I would rate OpsRamp as eight out of ten.

We mainly use this solution for its incident and inventory management functions.

We find the product's seamless integration with Zendesk to be extremely valuable to our business.

We would like this solution to be developed into a full CMP tool, so that we are able to use a single product for all of our cloud management needs.

We have been using this solution for over two years now.

We have found it to be a very stable solution.

This solution is easily scalable as required.

We have found the technical support team to be very good at what they do.  They respond quickly when we raise issues, and will escalate problems when we feel it is necessary.

In addition to this, the support team have arranged training for our in-house team on their new upgrade release.

Positive

We were previously using multiple solutions, but decided to switch to this product after trialling and reviewing it, due to how robust it is.

We found that the initial setup for this solution was straightforward, but that it would require some time and training before using the tool itself.  When setting up the product, we needed to set up multiple service and user accounts in the cloud and then integrate them with the software; this wasn't difficult to do, but it was time consuming.

The licensing for this solution is offered in bundles, payable on a yearly basis.  The cost of the bundle is dependant on how many resources an organization is using.

I would recommend this solution to any business that is looking for this type of product.  The software is web-based, which means that the implementation only requires logging into a URL in order for it to be carried out.

I would rate this solution an eight out of ten.

I main used this solution for on-boarding network and storage devices, then monitoring the clients environment, according to their requirements for these devices.

The most valuable feature of this solution in my experience, is that the available reporting is quite accurate. 

The user interface of this product requires some changes as it is not inclusively user-friendly. For example, the performance indicators are color-based , which means that they are confusing for anyone who is color blind.

The report building feature of this solution could definitely be enhanced to be more straightforward to use, and to allow for different parameters for reporting to be input, such as showing the version in use in a clients environment.

The product also tends to release updates first and find out there is an issue later. This leads to clients reporting bugs in the running performance.

I have been working with this solution for five years.

This is a mostly stable but solution, but scaling up the number of users has a negative impact on its performance.

This solution is scalable, but extra users tends to result in connection losses.

The support team for this solution are very good and have excellent technical skills. However, there were occasional issues with language barriers that meant it took longer to resolve problems than it should have.

There are also support articles available on the product website, but despite the manufacturers claims that they are user-friendly, they are actually complicated to follow.

Neutral

I found the initial setup of this solution to be quite easy, and the deployment across 100 devices took around 15 minutes to complete.

The initial setup, I think the OpsRamp team does it. And like I said, there are resources that you can follow, but they're not actually quite accurate.

I would recommend this solution to start-up organizations on a budget, but it may not be suitable for larger businesses with more in-depth requirements.

I would rate this solution a five out of ten.

We are using OpsRamp for infrastructure monitoring and site URL availability.

The most valuable feature of OpsRamp is the creation of the dashboards of the infrastructure for the CPU memory and SQL servers. Additionally, URL monitoring through Selenium scripting and the availability dashboard is useful.

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.

I have been using OpsRamp for approximately two years.

OpsRamp is stable. However, we have some issues with the OpsRamp agent sometimes.

OpsRamp is scalable. We can add and control the users.

We have more than 100 people using the solution. 10 to 15 of the 100 users are administrators who create dashboard alerts.

There are times when we raise a support request to the OpsRamp team and the response is not quick enough. The SLA is not quick enough.

The initial setup of OpsRamp is in the middle range of difficulty. The time it takes for the deployments depends on many factors, such as infrastructure resources.

We have an administration team in Active Directory managing the user's access to OpsRamp at the employee level, they will grant certain permission to everything.

There is an annual licensing fee to use OpsRamp.

Our company selected OpsRamp over other solutions because it is more user-friendly and cost-effective.

You will have to know what monitoring you need to set up and what kind of alerts. 

I would recommend this tool to others.

I rate OpsRamp an eight out of ten.