PagerDuty Operations Cloud
PagerDutyExternal reviews
914 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Good but can be better
What do you like best about the product?
UI is clear and user friendly
Easy to administrate
Easy to administrate
What do you dislike about the product?
Cannot share elements between project
No global monitoring
No global monitoring
What problems is the product solving and how is that benefiting you?
Continuous deployment automation each day for testing teams
Great product
What do you like best about the product?
Great product, good features and active development.
What do you dislike about the product?
E-mails are often ignored and remain unanswered. After multiple requests for a follow up you get a response but nothing more after that.
What problems is the product solving and how is that benefiting you?
It automates some tasks in our lab environment.
Powerful automation and control
What do you like best about the product?
Rundeck has a super clean interface allowing us to get the work done we need without getting in the way. We were able to get things setup and running with very little effort on the part of our small team. As a startup this was invaluable to us, we rarely run into a product that is as easy to use as Rundeck. We truly believe that using Rundeck will allow our small operations team to handle the growing number of tasks ahead of them as our startup grows and moves towards a production launch! Thank you Rundeck.
What do you dislike about the product?
Nothing comes to mind at this point, we will reach out to support if we have questions or suggestions on how to make the product better going forward.
What problems is the product solving and how is that benefiting you?
Rundeck has allowed us to automate processes which we taking us far too much time. We found more and more places to automate once we got started setting things up. Our ops team was spending so much time running manual processes and trying to document how everything was supposed to work, we can not believe how we used to do things.
Recommendations to others considering the product:
If you think your pile of scripts and home grown systems are working well, please give Rundeck a try. You will be amazed at what you were missing in automation and process that can streamline your business and day to day tasks.
Great core, but rough around the edges
What do you like best about the product?
Installing scheduled tasks in Rundeck, rather than individual servers, helps to centralize operations. Being able to develop forms to handle common IT tasks cuts down on our support volume - considerably, in some cases - and additionally provides an audit log. In all, it enables a greater level of transparency and access, and I'm a huge fan of the "IT self-service panel" concept.
What do you dislike about the product?
Rundeck's ACL system is powerful and granular but needlessly complex. It should be possible to assign or edit permissions using a graphical interface. There is currently no way to automatically clean out old job runs, so you either cobble something together yourself or let runs perpetually accumulate.
What problems is the product solving and how is that benefiting you?
I originally deployed Rundeck for use with my Ansible playbooks. At the time, Ansible Tower was a proprietary product without an open source equivalent. Over time, I found additional uses for it. For instance, I created a Project that lets our customer support agents add phone numbers to the phone system's blacklist without going through me.
After Red Hat acquired Ansible, it released AWX, an open source upstream for Ansible Tower, which I've begun using in place of Rundeck. AWX features deeper integration with Ansible playbooks, and the interface is, on the whole, a bit cleaner. There aren't quite so many options that I'll never use as there are with Rundeck. AWX is also written in Python, which I much prefer to Rundeck, which uses Java.
For me, AWX improves on Rundeck's annoyances enough that I plan to phase Rundeck out. However, for those who don't rely on Ansible so heavily, Rundeck is still a good product. There's nothing else quite like it - capable of running quite a lot, commercially sponsored, and open source.
But is it my first pick when given the choice of more specialized alternatives? No.
After Red Hat acquired Ansible, it released AWX, an open source upstream for Ansible Tower, which I've begun using in place of Rundeck. AWX features deeper integration with Ansible playbooks, and the interface is, on the whole, a bit cleaner. There aren't quite so many options that I'll never use as there are with Rundeck. AWX is also written in Python, which I much prefer to Rundeck, which uses Java.
For me, AWX improves on Rundeck's annoyances enough that I plan to phase Rundeck out. However, for those who don't rely on Ansible so heavily, Rundeck is still a good product. There's nothing else quite like it - capable of running quite a lot, commercially sponsored, and open source.
But is it my first pick when given the choice of more specialized alternatives? No.
Recommendations to others considering the product:
If you're trying to use Rundeck for a specific purpose, see if there's a purpose-built tool that you can use. Rundeck is a good general-purpose tool, but it may not be the best for very specific use cases.
Rundeck has saved us a lot of time.
What do you like best about the product?
The self service part, it helps users automate tasks without coding knowledge.
What do you dislike about the product?
The UI can be a bit dated.It could use a refresh.
What problems is the product solving and how is that benefiting you?
Some times the nodes would lose connection
product, feature release and support
What do you like best about the product?
Strong feature rich product helping automation except rigid and stiff on certain features. Easy installation and maintenance.
What do you dislike about the product?
tiny and least help full documentation specially on product upgrade 3.1.0 to 3.1.2 (my experience). Untested product release of 3.1.2 version. I had to spend almost two weeks to figure out workaround that to reading Rundeck .db files. (WebHook objects creation on MSSQL database had a wrong field type).
What problems is the product solving and how is that benefiting you?
Automation of azure resource maintenance, state management.
Recommendations to others considering the product:
NA
Rundeck Review
What do you like best about the product?
Features like running Ad-hoc commands, centralised management for scheduled jobs and logging user activity are making life easy. Integrations with Slack, Jira, Ansible are useful.
What do you dislike about the product?
Scaling is big issue as need to always go for the vertical scaling. No guide to tune it and plan the capacity for job scheduling and debugging/troubleshooting issue is really difficult.
What problems is the product solving and how is that benefiting you?
Centralised Scheduling of cron jobs and error handling. Enabling users to execute adhoc commands and compare the output from different instances. Also helps in auditing user activity on multiple stack of servers.
Generally good software but still quite a few bugs
What do you like best about the product?
Open source software, generally behaves how you would expect.
What do you dislike about the product?
There are still quite a few bugs in rundeck and responses from support are generally lacking technical expertise.
What problems is the product solving and how is that benefiting you?
Auto -deploying released software into our CIB and Production environments. 99% of deployments are now automated.
Rundeck Enterprise
What do you like best about the product?
Integration with other tools such as puppet and JIRA, though we are still working out how to configure it all.
What do you dislike about the product?
How hard it is to configure nodes, there should be an option via the GUI
What problems is the product solving and how is that benefiting you?
Give users the ability to restart applications without having to give them root access to the servers.
Does what you'd expect but not better than the competition
What do you like best about the product?
PagerDuty was very easy to move to and integrate with slack. For my organization, the slack integration was a must.
What do you dislike about the product?
It's more expensive and has a less verbose feature set than OpsGenie. For my organization, the move to OpsGenie has empowered better customized alert management that scales across the diverse needs of our organization.
What problems is the product solving and how is that benefiting you?
1) The ability for operations people to quickly be paged after-hours about production alarms.
2) Product teams have the freedom to rotate alert management according to whatever system they want to use (goalie, etc). We can also silence these after-hours for teams that are not on call.
2) Product teams have the freedom to rotate alert management according to whatever system they want to use (goalie, etc). We can also silence these after-hours for teams that are not on call.
Recommendations to others considering the product:
Check out the full landscape. While it will function well enough, there are better options out there that may cost your organization less money.
showing 21 - 30