PagerDuty

PagerDuty is best used for support teams and notifying the right people when there's an issue that needs to be addressed.

PagerDuty is perfect for being the hub of all monitoring channels and sending them on to the relevant teams / individuals.

PagerDuty has a well organised architecture which makes it effortless for one to use it. It employs the latest AI technologies like machine learning to help automatically monitor the product development cycle so as to pin point any incidents in the process and remedy them before they affect the performance of the product. With PagerDuty, it's not only figuring out the incidents but also evaluating their root causes so as to take measures of preventing their future occurrences. With the runbook automation feature, it makes it fast to assess incidents and resolve any identified issues.

PagerDuty is well suited for: Production support schedule management, Easy escalation setup, and Support of multiple notification mechanism. PagerDuty could improve the use of Artificial Intelligence or Machine Learning tools to suggest the best schedules and provide analytics insights.

If you're running critical business infrastructure which requires constant monitoring and on-call management, PagerDuty is go to tool which helps in alerting, on-call schedules and integrates with business apps.

Automatic alerting
Automatic incident creation and life cycle management
Smart AI based alerting matrix
Huge collection of inbound integration adapters
smooth SMS based outbound integration
Rule based alerting mechanism

PagerDuty is an incident management and response platform that provides developers, IT operations the insights they need to resolve and prevent business-impacting incidents quickly. It is well suited for any organization which works on ticketing / supports other teams/applications. The same PagerDuty can be used by multiple teams for collaboration and to resolve the issues in the enviornment.

The product works very well. It was priced higher than it's competitors.

PagerDuty is great for any team that has an on call schedule and relies on email alerts, server logs, or any other system that creates or sends messaging that can be detected by PagerDuty which will activate the escalation logic.

PagerDuty is best suited for large organizations that are monitoring numerous pieces of infrastructure and its also best suited for large teams who practice an on call rotation. PagerDuty is also best served for teams have a remote work force as it does a good job alerting when outages occur. PagerDuty would not be best suited for small teams managing small environments.

Its very much suited when you are deploying a micro-service or even a monolith projects and you are looking for a good monitoring tool that can make sure that your services are always up. If any incident happens you get real time notifications till it doesn't get resolved. It very important if the health of your service is very important and can't be compromised , then pager duty surely makes sense. If you don't have that important service and can bare little downtime then its ok to use some other tool.

PagerDuty allows you to create on-call schedules, and configure overrides that will ensure that even if the on-call engineer is unavailable, the incident will be assigned to someone else. PagerDuty is a great product, but it requires proper monitoring. For companies that either don't monitor themselves and rely on user complaints or their monitoring system mainly produces noise - this solution is less appropriate for them.

PagerDuty works great for all of our technology teams for important issue tracking but does not apply for the rest of our teams.

In case you want to get the right notifications to the right persons at the right time, PagerDuty enables you with maximum flexibility to do so. Not only will the developers be notified to solve the problems, but also management stakeholders can be informed and kept in the loop during the root cause analysis and hot fix deployment such that everyone is on the same page all the time.

Really strong, well-designed notification system. Good reliable software. I have used PD at two different employers and have also programmed notifications for PD in Python. The API was solid, straightforward, forward and simple, yet it provided the ability for more complex and robust functionality.

It can be used in different areas of companies, from technological infrastructure, business, sales, production, NOC. It is very useful in automation, escalation, incident control and service history. It is not useful for troubleshooting cases.

Standard incident management tool. Generally, PagerDuty is above market.

This is well suited to businesses who want an automated solution to inform someone when an issue arises, this can be a problem for many companies who run a 24/7 uptime service. For us this feeds into our business 24/7 escalation procedure, we have full automation, from monitoring to firing off events to fix or gather data to attach to a PagerDuty alert which engages the engineer and escalates if there is no reply along with raising an entry in our ticketing system and also embedding the data into that already for the engineer to sign off once they have logged in and done the relevant work. PagerDuty has reduced our costs in terms of staff and has allowed our IT staff to have more human-friendly hours instead of shifts which were until 10 pm in the evening from 6 am in the morning. It also bridges the gap between 10 pm and 6 am in terms of, we don't have to rely on somebody from a non-IT department noticing that there is an issue on the alert monitor as well as them not understanding what it is they are seeing. This is now an essential part of our automation system and has made the out-of-hours escalation process so much smoother.

The original meaning of "task scheduler" can eliminate the frustration of displaying crontab and saying "Well, aren't you using JP1?" It can correctly process correlations. Its graph is of very good quality and is not that difficult to enter if you have prior knowledge. If there is a free server, I would like to consider introducing it as a Task Scheduler.

Rundeck is a really good solution to formalize , standardize and automate your infrastructure operational run book. It can be also used in combination with your monitoring solution to auto heal your services. As for example when you get a specific alert, instead of triggering your notification channel to first trigger the Rundeck job to try and fix the issues (service restart etc..) and only then if the problem still persist to escalate and notify through an alert. It is also super handy to run all tasks from a central location and making sure there is no other person running the same job on the same servers at the same time, been able to see statistic about how fast or successful a job runs is also a big plus.

PaperDuty is handy when it comes to monitoring real-time infrastructure and endpoints. Also, PaperDuty provides a wide range of integration facilities for other systems as well.

I'm sure most IT support organizations need to use this tool or one like it to be able to alert people for assistance in outage situations. Multiple times we have had servers or even network devices giving us trouble and degrading service to our end customers. I am usually one of the multi-team staff that get paged to check devices for power, activity lights, and/or error logging. Not sure what else to say here. It's pretty straight forward to me.

Awesome for all things oncall, since it will send you a text, email and phone call all at once. Easy to integrate via the email setup into key tools, such as Salesforce. We have a separate case management tool, so not using it outside of its core function.

PagerDuty is best suited for reaching out to the on-call support team in case of urgent issues. we can set up a call schedule for different team members working from different locations. One can easily push notification and individuals gets notification based on their alert rules. this allows the team to jump on quickly and saves a lot of precious time. this results in eventually faster resolution of urgent issues and customer satisfaction.

It works great when managing an on-call rotation and having people on-call, especially in a corporate setting with multiple teams. It works well for issues with software and hardware being down, as well as network equipment. Works great with integration and accepts alerts via email, API, slack, etc. It may be less appropriate in very small settings where only one person is on-call.