Try our new research platform with insights from 80,000+ expert users

AutoSys Workload Automation vs PagerDuty Operations Cloud comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

AutoSys Workload Automation
Average Rating
8.4
Number of Reviews
79
Ranking in other categories
Workload Automation (8th)
PagerDuty Operations Cloud
Average Rating
8.8
Number of Reviews
36
Ranking in other categories
Process Automation (15th), IT Alerting and Incident Management (1st), AIOps (13th), Critical Event Management (CEM) (2nd)
 

Mindshare comparison

AutoSys Workload Automation and PagerDuty Operations Cloud aren’t in the same category and serve different purposes. AutoSys Workload Automation is designed for Workload Automation and holds a mindshare of 16.1%, down 18.8% compared to last year.
PagerDuty Operations Cloud, on the other hand, focuses on IT Alerting and Incident Management, holds 29.5% mindshare, down 32.7% since last year.
Workload Automation
IT Alerting and Incident Management
 

Featured Reviews

Antony Askew - PeerSpot reviewer
Mar 18, 2024
Helps us manage complex workloads, reduce our workload failure rates, and save us time
The visibility and control features are somewhat limited. This is a recognized weakness, but thee vendor is currently revamping the user interface to address it. While the current UI is a bit outdated, it's undergoing improvement. AutoSys Workload Automation has some areas for improvement, particularly in housekeeping and product maintenance. These tasks are currently quite manual and labor-intensive for our team. Additionally, the reporting and forecasting functionalities could be more robust. One area for improvement with AutoSys Workload Automation is that it comprises several distinct tools configured to work together. This necessitates familiarity with multiple tools for effective solution management. Consequently, it can sometimes lack a sense of cohesiveness as a unified solution.
Ashish  Paikrao - PeerSpot reviewer
Sep 8, 2023
Effectively generates alerts for incidents, making it suitable for 24/7 monitoring of infrastructure
We were exploring ManageEngine ServiceDesk. So, we need a feature where we can, like, when an alert triggers, we should alert the recipient by on-call. So, when an alert is detected, a ticket is generated in the management team, and we want to notify them on-call. Like, this ticket has been generated and stuff. So, I would like to see a similar feature in this solution. This is why we want an alternative to PagerDuty. We want an alternative to PagerDuty. So we are getting on-call notifications using PagerDuty, but now we want to replace PagerDuty with ManageEngine ServiceDesk. So whenever some incident happens in the cloud infrastructure, we get data alerts from cloud security. We want to integrate a service that will provide us with notifications on-call. That this server is down, or this website is down, or this thing is going wrong. Another area of improvement is integration. It cannot be integrated with our upgraded Jira system. That's why we are dropping PagerDuty. We won't continue using it due to integration issues.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"This solution has made my clients' workplaces a lot less labor-intensive."
"It is a fairly stable solution."
"It can run an object on our Windows systems or our Unix systems, and then send messages to the other system when they are complete."
"Integration with multiple services and applications across the enterprise."
"I find that it provides better agility in regards to job execution features."
"It is very valuable for us when we are trying to arrange or orchestrate jobs into a system. It is helpful for triggering jobs for a scheduled task."
"The ability to create calendars, calendering for batch jobs to run on a scheduled frequency."
"This solution enables us to improve our daily processing times. We can do everything faster than before we used this solution."
"The most valuable features of PagerDuty are customization, access, policies, and different rules regarding the path of escalation. Additionally, it's easy to use and create overrides. For example, if you all are on a call for one week each, but somebody wants to go on PTO, the team needs to swap shifts in PagerDuty. This is easy to do by creating overrides to switch up the set schedules. It's very user-friendly in that aspect. It works well for monitoring and alerting."
"The initial setup is a simple process."
"It reduces the amount of white noise. If something comes through, then it will alert somebody. However, if it's a bit of white noise that comes through at night, then it gets dealt with the next day. Everything is visible to everybody. It's not just a single person getting an SMS, then going, "Oh, I'm not going to worry about that." The visibility to everybody on the team is one of the great things about it because it reduces the white noise."
"The most valuable feature of PagerDuty is its integration with other tools, such as Amazon AWS, to receive notifications or create automatic instances."
"The inbound integrations that PagerDuty provides with most of the DevOps tools are valuable."
"PagerDuty helps you bifurcate teams and redirect alerts to specific teams"
"PagerDuty's notification process is the most valuable feature."
"Alert deduplication and noise reduction for alerts are the major features that I found useful."
 

Cons

"In terms of what should be in the next release, I want integration and AI and so on. I'd like easy reporting where you can compare information, for example, "that job normally takes three minutes and last time it took six minutes or 10 minutes." Then you can get the information to the engineer of which job is taking more time than normal - understanding strange behavior compared to the baseline."
"CA Workload Automation is not part of CA's strategic vision going forward."
"Performance improvements in the UI would be appreciated."
"To make it a lot more user-friendly, in order to make it so other people can use it without having to do much training with it; the more user-friendly it is, the easier it is to work with."
"We are trying to see if we can use this from a cloud perspective with AWS, Azure, and other clouds, but it seems that there is no cloud integration in this product. We would like to see cloud integration. We are very pleased with this solution, but we are moving our application to the cloud, and we found out that it doesn't support any cloud features. So, we are trying to find a replacement."
"​CA installation processes are never anything but complex.​"
"Documentation and cross-application externals could be improved."
"I am not sure whether it is our limitation or a tool limitation because we haven't yet explored it, but whenever we look for different types of reporting, we have some limitations in getting those. It could be because of the way we have set it up internally in our enterprise, but it would be helpful if we can customize the reporting features and some of the alerts that can go out. When we connect enterprise systems, each one looks for a different use case, and if we can get different types of reporting, it will be helpful."
"The biggest area for improvement with PagerDuty is noise suppression. There have been a handful of incidents through our use of PagerDuty over the years where one incident may lead to 30 to 50 pages because you're monitoring all these different things, and each thing is an individual page. There should be the ability to set up paging tiers and group correlations between some of the different pages. That is something that would be really valuable. We should be able to say this one page may have a group or a tree of effective other pages that may tier off of it. So, if you see those pages independently, go ahead and alarm, but if you see this plus that, don't do that."
"I am not a direct end user of PagerDuty. It's hard to consider its shortcomings in that sense."
"This solution works best in conjunction with a proper logging system, which can be an additional cost to organizations."
"It is a very non-customizable product, so you cannot add things like root cause analysis or the classification of incidents based on the area where you are getting more incidents. For example, if you're getting a lot of database issues, that may be an are you want to probe."
"PagerDuty's webhooks need some improvement."
"The solution's analytics are okay. I don't think the features, at this point, give you a lot of insights. We have actually been trying to get insights from it but it hasn't really given us a lot of extra points to explore. We were looking at the number of alerts to see where many of the alerts were coming from. We never managed to get many insights on this."
"It is difficult to send underlying trace files or statuses using PagerDuty."
"They could include incident merging and alert grouping features in the product."
 

Pricing and Cost Advice

"I don't have information on the exact licensing cost of AutoSys Workload Automation because that's managed by the tools and financing teams. For agents, it's close to $4,00, but for the server setup, it's usually a one-time license initially, and it's AMC which is paid every year and comes close to $8,000 to $10,000."
"I certainly think the pricing is worth the value."
"The pricing needs to be improved. Some of my client's complained that it was too expensive."
"CA pricing has been a problem, and not looked upon favorably here at all."
"The price of this solution is reasonable and there is an annual license required."
"People need to pay attention to how they use their ESP agents on the distributed platform. That's where some of the cost comes in, based on how many you need or how many you use."
"Validate how many agents you need beforehand."
"It is overpriced."
"PagerDuty has monthly and yearly licenses available, the costs of which can get quite high if you have a large number of users."
"There is a license needed to use PagerDuty."
"The cost is based on the package you select."
"The solution is paid on a monthly basis and represents about 1% of the platform's budget."
"If we wanted phone calls or additional SMSs, we would have to pitch up for those. They give us so many per month per user, then we have to pay extra if it goes over that."
"Licensing costs are around $700 a month, and the only additional costs, are phone costs in some instances."
"The cost is quite high. But if you want to get a full-featured application and you have a big team..."
"The price is very high."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
814,649 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
47%
Manufacturing Company
12%
Computer Software Company
6%
Insurance Company
5%
Computer Software Company
21%
Financial Services Firm
13%
Manufacturing Company
7%
Retailer
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

How does Control-M compare with AutoSys Workload Automation?
Control-M acts as a single, centralized interface for monitoring and managing all batch processes, which is helpful because nothing gets left unattended since it is all visible in one place, and th...
What do you like most about AutoSys Workload Automation?
The most valuable aspects of AutoSys Workload Automation are its performance, scalability, and ease of getting started for new users.
What do you like most about PagerDuty?
The product easily integrates with other solutions.
What is your experience regarding pricing and costs for PagerDuty?
The price is very high. I rate the pricing a six out of ten. The license for stakeholders is very limited.
What needs improvement with PagerDuty?
It is difficult to send underlying trace files or statuses using PagerDuty. You can set up email alerts, but you cannot build any triggers using those email alerts. There are limitations; you canno...
 

Also Known As

CA Workload Automation, CA Workload Automation AE
No data available
 

Overview

 

Sample Customers

Gaumont, Mercantil do Brasil, CCEE, Hanwha Life
40% of the Fortune 100 TrustPagerDuty. Customers include: Slack, Intuit, Zendesk, Panasonic, Pinterest, Airbnb, eHarmony, McKesson, Comcast
Find out what your peers are saying about BMC, Redwood Software, Broadcom and others in Workload Automation. Updated: October 2024.
814,649 professionals have used our research since 2012.