An enterprise-grade configuration management system that provides controlled access to software assets.
N/A
Ansible
Score 9.1 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
SolarWinds Pingdom
Score 9.9 out of 10
N/A
SolarWinds Pingdom is a website uptime monitoring and alert tool, with additional reporting and Real User Monitoring capabilities. Pingdom is part of SolarWinds’s DevOps package, enabling full-stack monitoring as a service.
IBM Rational ClearCase might be better suited for a smaller / simpler code base. Larger code bases really slow it down... but then again there are better alternatives out there for source control
I think it's the best defacto orchestrator for automation because it's so easy to integrate in other tools to it (dynatrace, cyberark, terraform, etc). It is a lot for a new or smaller team to use so I wouldn't recommend it to a new team using Ansible, in that case using Ansible navigator is a better start to understanding playbooks/inventories before diving into the complexity of Red Hat Ansible Automation Platform. EDA also takes a lot of connectivity between Red Hat Ansible Automation Platform and target systems to get working which can be difficult in very locked down envs unless you have approval from many other teams like networking and security.
I believe the scenarios we used it for were quite well covered, from the executive perspective. The downtime alarms worked very well and were easy to setup, uptime monitoring tools were clear and easy to use, even for non-technical people (C-level) and the SLA management tools allowed us to spend less time, and have less friction, with our clients
Rational ClearCase is excellent for handling versioning and branching. No other tool I've used has the depth that ClearCase has when it comes to handling complex branching scenarios and identifying where certain versions of particular files are within a particular configuration.
Rational ClearCase handles parallel development of many dependent applications really well.
The use of ClearCase Views to switch between projects and configurations is extremely convenient as opposed to the local workstation model of the competitors.
The PagerDuty integration could be a lot better. When you use the PagerDuty integration, it doesn't send any information about which check failed! It just sends a message like "Timeout (> 30s)" -- this isn't very helpful when we have hundreds of checks. We've worked around this by using both the PagerDuty and Slack integrations and having them both post to the same Slack channel. But this means that when an engineer is paged from PagerDuty, they have to go to Slack (or Pingdom) to find the details about the page; it's not available on the page itself.
We are extremely happy with the use of AAP. It's better than expected, There is almost no limit when thinking of automation. The only problem is that the day to day is consuming a big part of our time. Patching and checking vulnerabilities are virtually killing us. But we can only improve with AAP.
Recently added features have made Pingdom less intuitive for our requirements. While Pingdom has a broad offering and remains a good value, it is becoming more than we need. Our customer base is becoming more and more global and Pingdom still lacks Asia-Pacific monitoring, which we will need within a year.
Everything has room for improvement, but Ansible is the best tool out there for what it does and what it can do. There are plenty of features and capabilities that can be added, but it's just a matter of time before it happens.
Pingdom is easy to use, very intuitive and has a very short learning curve. From the onset, we've been able to jump in and leverage the tool to accomplish our goals for page speed performance and discover the insights we need to make improvements. Its a well-designed tool and makes for a good user experience.
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.
Support responded the same day to my query, as I was setting the product up but couldn't find the setting I needed. This was successfully resolved in a short time frame, so I was pleased with how quickly we were able to get this resolved. I haven't needed to contact support since.
If development is centrallized to one location and your company releases hundreds of customized versions of your software per year, then ClearCase is the best tool for managing the complexity of multiple versions of customized software. If your company has globally distributed development, then I'd recommend Team Foundation Server over ClearCase. If your organization uses Agile Methodologies, then I'd recommend TFS with GIT.
AAP compares favorably with Terraform and Power Automate. I don't have much experience with Terraform, but I find AAP and Ansible easier to use as well as having more capabilities. Power Platform is also an excellent automation tool that is user friendly but I feel that Ansible has more compatibility with a variety of technologies.
PRTG Network Monitor was a far more complicated tool to use and set up albeit it does both Internal and External monitoring. The setup wasn't intuitive and there are too many configuration options to complete to form an alert
Amazon CloudWatch is specific to AWS resources and cannot be easily use outside of the AWS Ecosystem
First, it keeps our entire server infrastructure aligned with our standards and reduces the time and effort needed to maintain our systems.
Automate routine IT tasks to save time, reduce errors, and ensure every server is configured and updated consistently.
Tasks that used to take our teams weeks to complete manually now run automatically and reliably, with full visibility, making our infrastructure management more effective and our compliance tracking much easier.
Honestly, we have 4 other products that overlap this functionality whose organizations provide far superior support. At this point it is an unnecessary expense.
In my opinion, their lack of support responsiveness and commitment has impacted our IT agility.