ActiveBatch Workload Automation vs PagerDuty

• File management - moving, archiving, and folder cleanup are a drag-and-drop breeze. The visual representation of file management steps includes date/time filtering, file/folder/both specification, and recursion all in an easy and intuitive unit.
• FTP/SFTP/FTPS - while one must still write the FTP scripts, the interface simplifies much of the infrastructure, allowing the developer to encapsulate the script text in a graphical package that is easy and intuitive.
• PowerShell integration - for anything that isn't easy in ActiveBatch's GUI, simply drop in a PowerShell step and write the task in PoSh - anything returned from PoSh can then be used by the following steps.

Read full review

• Alerting notifications is its best attribute; it will continue to make contact until the alert is acknowledged by a user.
• The calendar view provides valuable information regarding who is on call by the team and their full contact information.
• The application also lets you initiate a tech bridge meeting instantly and notifies all on-call users.

Read full review

• While I like being able to reuse scheduling objects and the like, more work needs to be done to help one not reinvent the same scheduling object without realizing it and to then find scheduling objects that have similar schedules even if they are worded slightly differently than what I'm expecting. It needs to be "smarter". It was easy to accumulate a pool of scheduling objects that while named differently, had exactly the same schedule. It was also hard to sift through to find the little differences between similarly named scheduling objects.
• The logger had a clean enough interface but it could be more legible and offer contextual help to describe the messages one is reading. I remember trying to read black text on a medium gray background with Courier size 10-11 font. Not so easy to read quickly and to parse through the relevant parts. I think some selective color coding would be good and links to message definitions or any form of further information would be nice. Maybe the ability to export the log file to various formats would also be helpful.
• I don't remember a dashboard that at a glance on the top level would highlight what jobs failed completely and which jobs might have warnings or non-critical errors. I got emails because I defined to get them. Maybe again if there was a way to color-code the type of error would be good nice-to-have.

Read full review

• When getting a phone call, PagerDuty doesn't seem to allow acknowledgments of alerts through the phone, which it says it does. I constantly receive a message that it was updated by another person - when in reality, it wasn't.
• Smarter notifications. If an alert was snoozed for a time, when it comes back, it sends out another alert. It should, I think, send a message asking if the alert is still an issue and give the option to close.
• Make schedule changes more intuitive.
• One button to acknowledge and close an alert.

Read full review

• ActiveBatch [Workload Automation] has increased our nightly processing stability exponentially. Our prior automation software was unreliable and often failed without explanation. Since moving to ActiveBatch [Workload Automation] we have had incredible stability, and any nightly processing errors that happen now are attributed to a cause other than automation. It's the most reliable software we currently use at our company.

Read full review

• Saved about $50k USD per annum on event management only. This does not include all the additional benefits of things like on-call, automated escalations, etc. we did not have previously.
• Reduced on prem infrastructure footprint by about $6k USD a month.

Read full review