103 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 8 out of 100
12 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 7.6 out of 100

Likelihood to Recommend

Microsoft System Center Operations Manager (SCOM)

More appropriate for:
  • Pure Microsoft ecosystem environments (Windows Server and SQL server) and the most common Linux and UNIX platforms.
  • Environments where cost is less of a factor than settling on a single platform for monitoring
  • Environments where the administrators are familiar with the setup and installation of SCOM.
Less appropriate for:
  • Pure UNIX/Linux shops, especially versions not supported out of the box by SCOM.
  • Shops that cannot afford the engagement to setup/configure and maintain on a continuous basis.
  • Shops that cannot dedicate personnel to the care and feeding of SCOM, especially when supporting larger environments.
Anonymous | TrustRadius Reviewer

OpenNMS

I would recommend all system administrators use some form of network monitoring if they are not already doing so, and I'd definitely recommend people consider OpenNMS if they're shopping around. Small businesses will benefit from the low-cost of entry (it's free!), whilst getting all the enterprise features. Larger businesses can benefit from paid support plans.
However, there's no getting around the fact that you will require some advanced networking and sysadmin knowledge to get the most out of OpenNMS, or at least, be prepared for a steep learning curve. If you don't have the resources to devote this time initially, you may struggle.
Anonymous | TrustRadius Reviewer

Feature Rating Comparison

Application Performance Management

Microsoft System Center Operations Manager (SCOM)
8.5
OpenNMS
Application monitoring
Microsoft System Center Operations Manager (SCOM)
8.7
OpenNMS
Database monitoring
Microsoft System Center Operations Manager (SCOM)
9.0
OpenNMS
Threshold alerts
Microsoft System Center Operations Manager (SCOM)
9.6
OpenNMS
Predictive capabilities
Microsoft System Center Operations Manager (SCOM)
7.5
OpenNMS
Application performance management console
Microsoft System Center Operations Manager (SCOM)
7.7
OpenNMS
Collaboration tools
Microsoft System Center Operations Manager (SCOM)
8.2
OpenNMS
Out-of-the box templates to monitor applications
Microsoft System Center Operations Manager (SCOM)
8.6
OpenNMS
Application dependency mapping and thresholding
Microsoft System Center Operations Manager (SCOM)
7.4
OpenNMS
Virtualization monitoring
Microsoft System Center Operations Manager (SCOM)
8.9
OpenNMS
Server availability and performance monitoring
Microsoft System Center Operations Manager (SCOM)
9.5
OpenNMS
Server usage monitoring and capacity forecasting
Microsoft System Center Operations Manager (SCOM)
8.1
OpenNMS
IT Asset Discovery
Microsoft System Center Operations Manager (SCOM)
8.9
OpenNMS

Pros

Microsoft System Center Operations Manager (SCOM)

  • Pick real-time health data from a large number of systems through their agent services installed on those remote systems.
  • Have the ability to directly create an incident in snow with its SCOM-SNOW Integration pack.
  • Have the capability to design activities to perform actions on apps or infrastructure components directly from SCOM Dashboard.
Anonymous | TrustRadius Reviewer

OpenNMS

  • Report on SLA
  • Group network areas
  • Discovery of elements
Anonymous | TrustRadius Reviewer

Cons

Microsoft System Center Operations Manager (SCOM)

  • One of the biggest drawbacks to SCOM is the sheer scope and complexity of the system. This can be a pro and a con. The system is very customizable, what you put into it is what you'll get out of it. That said, the learning curve is fairly steep. An organization needs to be committed to putting time and resources into SCOM to get the most out of it. I've heard stories from colleagues of several different companies that invested in SCOM and then abandoned it due to the excessive time and care required.
  • SCOM is expensive. Not only is the enterprise licensing costly, SCOM requires it's own servers, operational and warehouse databases to be maintained.
  • The OOB SCOM reports are a bit clunky and feel outdated.
Anonymous | TrustRadius Reviewer

OpenNMS

  • We've had a few issues with delayed alerting.
  • I haven't quite figured out how to make topologies work yet, but I haven't spent a ton of time on it either.
  • We've also had a bit of trouble importing some MIBs, but that usually boiled down to working with the vendor to make sure we had the right MIBs and dependencies.
Anonymous | TrustRadius Reviewer

Support Rating

Microsoft System Center Operations Manager (SCOM)

Microsoft System Center Operations Manager (SCOM) 7.7
Based on 18 answers
We are very pleased with the support provided by the Microsoft System Center Operations Manager team. At first, we were quite hesitant to contact support, but the support team showed a very proactive approach and helped with a bunch of issues which would be much harder to overcome on our own, especially when deploying the platform for the first time.
Anonymous | TrustRadius Reviewer

OpenNMS

No score
No answers yet
No answers on this topic

Alternatives Considered

Microsoft System Center Operations Manager (SCOM)

We didn't consider any other alternatives, nor did we try or demo any other product prior to our purchase of SCOM. I know there are several other products out that perform many of the same functions and more such as SolarWinds, however, those products are pricey as well and we decided to stick with the Microsoft product in the end.
Joe Spradlin | TrustRadius Reviewer

OpenNMS

OpenNMS's more attractive GUI and its price break were the main reasons our company chose to explore and use this product. However, it never managed to actually replace Nagios which had a much more established hold within the company. Perhaps we were over-monitoring, but our company claimed a $100k loss per hour of downtime.
Derrick Barnsdale | TrustRadius Reviewer

Return on Investment

Microsoft System Center Operations Manager (SCOM)

  • We wanted to make sure that updates and patches deployed are actually successfully installed on devices and other tools cannot match SCOM for detailed feedback on deployment status.
  • We can now confidently provide management and security teams on successful update of security patches with high accuracy.
  • Deployment complexity took over a year to fully implement all necessary features with help of consultants and in house teams. Wish it was simpler.
Anonymous | TrustRadius Reviewer

OpenNMS

  • Initial adoption required quite a lot of resources and time to get everything right. Totally worth it for us; just be prepared for a gradual process that will get better and better with time.
  • Once setup and running smoothly, it provides us with all the reporting we could hope for, at near zero cost.
  • With OpenNMS, we're able to offer a much more reliable service to our customers, and spend a lot less time dealing with issues.
Anonymous | TrustRadius Reviewer

Pricing Details

Microsoft System Center Operations Manager (SCOM)

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Starting Price

OpenNMS

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?

Starting Price

Rating Summary

Likelihood to Recommend

Microsoft System Center Operations Manager (SCOM)
8.7
OpenNMS
8.5

Support Rating

Microsoft System Center Operations Manager (SCOM)
7.7
OpenNMS

Add comparison