Microsoft's System Center Operations Manager (SCOM) is a monitoring and application performance management option, with the core datacenter and cloud-based systems monitoring.
N/A
Ansible
Score 9.2 out of 10
N/A
The Red Hat Ansible Automation Platform (acquired by Red Hat in 2015) is a foundation for building and operating automation across an organization. The platform includes tools needed to implement enterprise-wide automation, and can automate resource provisioning, and IT environments and configuration of systems and devices. It can be used in a CI/CD process to provision the target environment and to then deploy the application on it.
$5,000
per year
Pricing
Microsoft System Center Operations Manager (SCOM)
Red Hat Ansible Automation Platform
Editions & Modules
No answers on this topic
Basic Tower
5,000
per year
Enterprise Tower
10,000
per year
Premium Tower
14,000
per year
Offerings
Pricing Offerings
Microsoft System Center Operations Manager (SCOM)
Ansible
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Microsoft System Center Operations Manager (SCOM)
Red Hat Ansible Automation Platform
Features
Microsoft System Center Operations Manager (SCOM)
Red Hat Ansible Automation Platform
Application Performance Management
Comparison of Application Performance Management features of Product A and Product B
Microsoft System Center Operations Manager (SCOM)
6.1
Ratings
22% below category average
Red Hat Ansible Automation Platform
-
Ratings
Application monitoring
5.00 Ratings
00 Ratings
Database monitoring
9.00 Ratings
00 Ratings
Threshold alerts
10.00 Ratings
00 Ratings
Predictive capabilities
2.00 Ratings
00 Ratings
Application performance management console
3.00 Ratings
00 Ratings
Collaboration tools
6.00 Ratings
00 Ratings
Out-of-the box templates to monitor applications
4.00 Ratings
00 Ratings
Application dependency mapping and thresholding
4.00 Ratings
00 Ratings
Virtualization monitoring
7.00 Ratings
00 Ratings
Server availability and performance monitoring
10.00 Ratings
00 Ratings
Server usage monitoring and capacity forecasting
8.00 Ratings
00 Ratings
IT Asset Discovery
5.00 Ratings
00 Ratings
Configuration Management
Comparison of Configuration Management features of Product A and Product B
Well suited for IT Departments that can budget the funds and time needed for setup and maintenance of SCOM. The end product is well suited for medium to large environments that have 100's of resources that require monitoring and reporting. Enterprise level statistics are at your fingertips with a few clicks of a mouse after the product has been configured and agents have been deployed. As I said previously, we are a small business and I was fortunate enough to be able to budget this product into our environment. It did take us a while to configure and fully deploy, but as a result, we are well-informed and are able to extract detailed information as it pertains to usage/consumption of our workstation and server resources to include performance metrics and any errors that may arise.
I'm going to say it is best suited for configuration management. Like I said, patching even with security, things of that nature. Probably less suited is hardware management, but Red Hat IBM/IBM has Terraform for that. So it's a trade off.
SCOM can manage Windows OS systems from desktops to servers very well.
SCOM is platform agnostic in that we manage physical and virtual machines with no differentiation.
SCOM can quickly deploy emergency security patches and the best part is it can provide detailed results of success and failure rate of patch deployment.
Debugging is easy, as it tells you exactly within your job where the job failed, even when jumping around several playbooks.
Ansible seems to integrate with everything, and the community is big enough that if you are unsure how to approach converting a process into a playbook, you can usually find something similar to what you are trying to do.
Security in AAP seems to be pretty straightforward. Easy to organize and identify who has what permissions or can only see the content based on the organization they belong to.
It is a monster of a system and really needs a person managing the system full time
Options are a bit clunky especially when you need to set overrides.
Takes a lot of time and effort to setup alerts as you want them, don't rely on the out of the box options you need to invest time into the system to get what you want out of it.
Make sure you size the underlying database server/s correctly (Microsoft provide a tool to calculate based on number of objects you plan to collect data on), it is a datawarehouse underneath after all.
Even is if it's a great tool, we are looking to renew our licence for our production servers only. The product is very expensive to use, so we might look for a cheaper solution for our non-production servers. One of the solution we are looking, is AWX, free, and similar to AAP. This is be perfect for our non-production servers.
Overall it's good but the new architecture can be complex. Improvements can be made in the Config as Code capabilities for managing Red Hat Ansible Automation Platform. Sometimes it can be difficult for those unfamiliar to understand the relationship between Projects/Credentials/Job Templates, etc.
Great in almost every way compared to any other configuration management software. The only thing I wish for is python3 support. Other than that, YAML is much improved compared to the Ruby of Chef. The agentless nature is incredibly convenient for managing systems quickly, and if a member of your term has no terminal experience whatsoever they can still use the UI.
There is a lot of good documentation that Ansible and Red Hat provide which should help get someone started with making Ansible useful. But once you get to more complicated scenarios, you will benefit from learning from others. I have not used Red Hat support for work with Ansible, but many of the online resources are helpful.
SolarWinds stacks well on the ease of use with an easily installable version and highly modular (products can be added to the basic installation and are easily managed from a single endpoint. System Center Operations Manager was selected because the majority of the environment is based on Windows products and it was part of the licensing agreement. It offered an easy way to consolidate the monitoring tools to provide a single point of management.
As I said earlier, Red Hat Ansible remains a top choice because it is a perfect combination of multiple capabilities. Terraform is good in IAC but not in config automation. Puppet is well-suited for developers, but not for system administrators and infrastructure integrators. OpenShift and Kubernetes are generic automators only.
Since we are at the tail end of our POC, we have no immediate ROI to report.
That said, during the POC, we immediately identified several issues within TFS that we immediately addressed and will potentially save us hours of lost time and troubleshooting.
We are still early in our implementation and don't have much yet - but I can say that it has already improved the time it takes to deploy a new virtual server for us, as well as making them more consistent.
In working through what jobs are required, it has really improved the communication between our different teams