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 Server & Application Monitor
Score 8.5 out of 10
N/A
SolarWinds Server & Application Monitor (SAM) delivers application and server monitoring capabilities. SAM allows for self-service for easy setup, 1200+ monitoring templates, and customization options, as well as integrate with other SolarWinds products.
It has helped save us so much time, as it was designed to automate mundane and repetitive tasks that we were using other tools to perform and that required so much manual intervention. It does not work very well within Windows environments, understandably, but I would love to see more integration. I want it to be sexy and attractive to more than just geeky sysadmins.
For monitoring applications that run on Windows hosts on VMware or HyperV virtualization, SolarWindows offers a nice, vertical view of both the loads and the resources. In such an environment, this makes life really good! But if you have something else -- for example, Linux hosts -- you're on your own to some extent. That is, the things it does well, it does very well -- but everything else is much less polished.
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.
YAML is hard for many to adopt. Moving to a system that is not as white space sensitive would likely increase uptake.
AAP and EDA should be more closely aligned. There are differences that can trip users of the integration up. An example would be the way that variables are used.
Event-driven Ansible output is not as informative as AAP.
Provides basic monitoring/visibility. Visibility into detailed/fine-grained issues best suited for more specialized/expensive solutions.
Licensing per monitored application rapidly uses up purchased license count.
More out-of-the-box templates or easier setup of monitoring less-common applications would make the solution more appealing given the target audience of the product.
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.
We are heavily invested in Solarwinds products for a reason. They are generally easy to setup and run with, requiring only some interfacing with support or help articles on rare occasions. They do what we bought them to do and we can't ask for more.
SolarWinds Server & Application Monitor is quite easy to use and super versatile. It allows you to do just about anything you can through premade templates or through scripting. You can use an agent on the servers if you want to, or you can monitor through WMI or SNMP credentials. You can customize thresholds for alerting quickly, and you can configure alerts to be as complex or as simple as you want.
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.
The graphical interface and the performance of the database leave a little to be desired, they could be better explored.Some functionality and screens do not work well depending on the browser used. The integrations never had any problems or caused crashes in other systems.
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.
I think there was only a couple times I had to open a support case for SAM and one time they got multiple engineers on the phone to get a better idea what I was trying to monitor and was able to point me in the best direction to monitor that system.
I haven't thought of any right now other than just doing our own home-brewed shell scripts. Command line scripts. And how does this compare? It's light years ahead, especially with the ability to share credentials without giving the person the actual credentials. You can delegate that within, I guess what used to be called Ansible Tower, which is now the Ansible Automation platform. It lets you share, I can give you the keys without you being able to see the keys. It's great
It has been a while since we first purchased SolarWinds, but I looked over several other products that I can't remember now. Many other products tried to scan the network to find computers but given that our computers are located in various places across campus with other computers in our buildings that are not ours that type of network scanning was not what we needed. Other services have extra services that we had no need of and I liked the ability to add custom fields in SolarWinds so we can track the information on each computer that we need to know.
Less time spent investigating causes of issues. We are alerted straight away and can find the root cause of the issue in less time.
We have been able to ditch all our previous individual monitoring solutions, none of which integrated with each other for a single solution which fully integrates with each of the different modules to provide a single portal for monitoring and alerting.
