AWS OpsWorks vs. IBM Netcool Network Management

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
AWS OpsWorks
Score 4.6 out of 10
N/A
AWS OpsWorks is a configuration management service that provides managed instances of Chef and Puppet.N/A
IBM Netcool Network Management
Score 8.7 out of 10
N/A
Netcool Network Management integrates the IBM Tivoli Network Manager IP Edition, Tivoli Netcool/OMNIbus and Netcool Configuration Manager products into a unified solution that consolidates the management of networks.N/A
Pricing
AWS OpsWorksIBM Netcool Network Management
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
AWS OpsWorksIBM Netcool Network Management
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
AWS OpsWorksIBM Netcool Network Management
Top Pros
Top Cons

No answers on this topic

Best Alternatives
AWS OpsWorksIBM Netcool Network Management
Small Businesses
HashiCorp Terraform
HashiCorp Terraform
Score 8.6 out of 10
NinjaOne
NinjaOne
Score 9.2 out of 10
Medium-sized Companies
Ansible
Ansible
Score 9.0 out of 10
Intermapper
Intermapper
Score 8.5 out of 10
Enterprises
Ansible
Ansible
Score 9.0 out of 10
Cisco Prime LAN Management (discontinued)
Cisco Prime LAN Management (discontinued)
Score 7.5 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
AWS OpsWorksIBM Netcool Network Management
Likelihood to Recommend
6.0
(3 ratings)
9.0
(1 ratings)
Support Rating
6.0
(1 ratings)
-
(0 ratings)
User Testimonials
AWS OpsWorksIBM Netcool Network Management
Likelihood to Recommend
Amazon AWS
Where you already have some Chef recipes to build your application boxes and are happy to run directly on VMs, OpsWorks really shines. It won't do anything too complex for you, so it only really works well for simple stacks (load balancers, application layers, database layers). If you want to do more complex infrastructure, Cloudformation or Terraform are probably worth looking at.
Read full review
IBM
This tool was integrated with Control-M, so whenever we receive any job failure, long-running job, job not started yet, etc, we receive an alert against it. This tool is also integrated with Maximo where we receive the incidents as well for it. Alert's color was as per the criticality of the job and that makes it very easy for an associate to act on it to resolve. We have the SLAs for the jobs as per the urgency of the jobs.
Read full review
Pros
Amazon AWS
  • connect between serveral AWS services (EC2, RDS, ELB)
  • easy configuration management deployment via Chef
Read full review
IBM
  • This is one of the best monitoring tools.
  • Very simple to user.
  • Color code makes it very simple as per severity.
  • We receive the heartbeat alert every hour that shows the system is running up and fine.
  • We have black, red, yellow, and orange color alerts that show the critical, urgent, major, and minor incidents.
Read full review
Cons
Amazon AWS
  • Getting up and running with OpsWorks is a very technical and potentially time-consuming process. You need to know the ins and outs of Chef/Puppet if you really want to get into it and there isn't a convenient way to test out the environment locally so debugging can be time-consuming.
  • To take advantage of some of the newer AWS instance types you need to be running on a VPC, which again is a pain if you don't have a DevOps team.
  • The error logs and monitoring metrics in OpsWorks are pretty basic and haven't changed much over the years.
Read full review
IBM
  • Sometimes color differences of the incidents as per the criticality .
  • We don't receive the heartbeat alerts sometimes.
  • If the tool is down and we don't receive the alerts on the console we wait for the heartbeat alert and it makes some extra delay in resolving things.
Read full review
Support Rating
Amazon AWS
Unless you pay for a pricey support package getting support on OpsWorks will be pretty slow. Documentation is also relatively limited and sometimes hard to follow when compared to competitors. Generally, we've been able to get the answers we need from OpsWorks support when we run into problems but don't expect rapid responses.
Read full review
IBM
No answers on this topic
Alternatives Considered
Amazon AWS
OpsWorks isn't really a direct competitor to Terraform/Cloudformation, but it does allow you to do some of the more simple things on offer quite quickly and effectively. Opsworks was used for this reason, along with existing internal knowledge of Chef. Along with some of the other services on offer from AWS, it is good to use as a stepping stone along the way when building your systems - or perhaps it would be entirely suitable for a fairly simple project.
Read full review
IBM
This is one of the essential tools for monitoring. This tool was integrated with Maximo and Control-M in my organization. So whenever any job failed in Control-M, we receive an alert against it in the IBM Netcool/OMNIbus. We receive the alerts in different colors as per the criticality. Black for critical ones(Sev1), red for urgent (Sev2), yellow for major(Sev3), and orange for minor(Sev4). So it makes an easy to operate and act on the alerts as per the severity. This tool is very user-friendly and easy to use. No additional training is required for the tool to operate, just a simple KT is enough.
Read full review
Return on Investment
Amazon AWS
  • very quick way of creating new infrastructure
  • low maintenance costs
  • easy to create high availability setups thus reducing costs
Read full review
IBM
  • Color feature of the alerts as per the criticality is the amazing feature.
  • Heartbeat alert is also an unique feature.
  • No additional training is required to use this tool. just a simple KT is enough.
Read full review
ScreenShots