Apache Airflow is an open source tool that can be used to programmatically author, schedule and monitor data pipelines using Python and SQL. Created at Airbnb as an open-source project in 2014, Airflow was brought into the Apache Software Foundation’s Incubator Program 2016 and announced as Top-Level Apache Project in 2019. It is used as a data orchestration solution, with over 140 integrations and community support.
N/A
BMC FootPrints
Score 7.5 out of 10
N/A
BMC FootPrints is an IT service management (ITSM) solution featuring workload automation.
N/A
Pricing
Apache Airflow
BMC FootPrints
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Apache Airflow
BMC FootPrints
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Apache Airflow
BMC FootPrints
Features
Apache Airflow
BMC FootPrints
Workload Automation
Comparison of Workload Automation features of Product A and Product B
Apache Airflow
9.8
10 Ratings
15% above category average
BMC FootPrints
-
Ratings
Multi-platform scheduling
10.010 Ratings
00 Ratings
Central monitoring
10.010 Ratings
00 Ratings
Logging
10.010 Ratings
00 Ratings
Alerts and notifications
10.010 Ratings
00 Ratings
Analysis and visualization
10.010 Ratings
00 Ratings
Application integration
9.010 Ratings
00 Ratings
Incident and problem management
Comparison of Incident and problem management features of Product A and Product B
Apache Airflow
-
Ratings
BMC FootPrints
8.1
9 Ratings
1% below category average
Organize and prioritize service tickets
00 Ratings
9.09 Ratings
Expert directory
00 Ratings
7.04 Ratings
Service restoration
00 Ratings
6.02 Ratings
Self-service tools
00 Ratings
7.07 Ratings
Subscription-based notifications
00 Ratings
10.06 Ratings
ITSM collaboration and documentation
00 Ratings
9.06 Ratings
ITSM reports and dashboards
00 Ratings
9.07 Ratings
ITSM asset management
Comparison of ITSM asset management features of Product A and Product B
Apache Airflow
-
Ratings
BMC FootPrints
7.9
7 Ratings
4% below category average
Configuration mangement
00 Ratings
7.77 Ratings
Asset management dashboard
00 Ratings
8.05 Ratings
Policy and contract enforcement
00 Ratings
8.04 Ratings
Change management
Comparison of Change management features of Product A and Product B
For a quick job scanning of status and deep-diving into job issues, details, and flows, AirFlow does a good job. No fuss, no muss. The low learning curve as the UI is very straightforward, and navigating it will be familiar after spending some time using it. Our requirements are pretty simple. Job scheduler, workflows, and monitoring. The jobs we run are >100, but still is a lot to review and troubleshoot when jobs don't run. So when managing large jobs, AirFlow dated UI can be a bit of a drawback.
BMC Footprints is so well suited to keep the documentation easy to read and find, as same as typification. You can find specific documentation for an audit so fast and export a report using the specific criteria that you need to comply with your boss or audit needs. As I told before, BMC footprints need to be more friendly to the end users because they get lost many times trying to track some ticket or typing documentation.
Documentation. We try to reduce the amount of paperwork needed for staff to do their job, so by automating certain tasks, we are able to speed up the resolution process for trouble tickets.
Reporting. We'll use the reporting tool to get the number of tickets opened, response times and can go into granular reports.
Surveys. When tickets are closed, we automatically send out surveys to end users to get valuable feedback on how we did and what we can improve.
Purpose based configuration- It would be beneficial to see a more purposed based, out of the box, configuration option. For example, if you need PCI compliance, more intuitive reporting would make managing compliance much easier.
Initial design and implementation- Don't think that your experience as an IT professional will allow you to stand this system up on your own. To properly configure Footprints and set yourself up for success down the road, get Professional Services with this one.
Somewhat behind the times- Service Core is making a huge leap forward with the latest version, 12, but Asset Core is far behind. There are quite a few quirks to how the application works and how it is used.
It has been the business decision to go with them and that is what we will do. Going back, this would have not been the choice, but nothing can be done about it now. We are stuck with this application for years to come. Wish there were other possibilities that could be done.
It's so simple to use and customize however you want. You can create new workspaces and workflows with ease, set up new users, incoming email rules, customize the layout of the forms, and even change the colors and logos. It's just very easily customizable overall. It's also really straightforward to figure out how to use, you really almost don't have to show somebody how to use it. If you just sit them down in front of it and let them look it over, they could figure it out themselves easily.
I've had no issues with the support for FootPrints. We haven't really had to use them all that much over the years, but when needed they have always been prompt and knowledgeable at dealing with any issue. I've worked with a lot of different support teams over the years, and they have been one of my favorites to work with.
There are a number of reasons to choose Apache Airflow over other similar platforms- Integrations—ready-to-use operators allow you to integrate Airflow with cloud platforms (Google, AWS, Azure, etc) Apache Airflow helps with backups and other DevOps tasks, such as submitting a Spark job and storing the resulting data on a Hadoop cluster It has machine learning model training, such as triggering a Sage maker job.
I was not involved in the selection process but in my opinion either SQL or Access databases would have worked just as well without the same amount of cost. These two systems would have been much easier to manage and would have tracked the same information in a less convoluted process and expense.