PagerDuty

PagerDuty allows for our required routing at a fair cost based on our needs.

I would highly recommend using PagerDuty because it is extremely useful in priority based alerting that can be configured to catch, mitigate and triage bottleneck reducing loads on server as well as other crucial key components. It helps in seggregating and defining the alerts based on specific paging keys giving external integrations a chance to utilize them is the best possible way to reduce the time spent in idle state. For me, PagerDuty is like a protective wrapper.

Onsite support workflow

PagerDuty is well suitable for monitoring production critical real time systems.

I've used ICM in the past which has been a very Microsoft product with everything thrown into a blender. So, PD implementation is a breath of fresh air with focused pages to achieve the end goal. If the goal is to collaborate on issues across the organization, PD might not be the best solution but within specific teams, PD excels at it.

its best suited for the team which are operational heavy and where folks are situated around the globe, using pagerduty its easy to create follow the sun model for managing your on-call schedules and since its very popular and offer a good use-experience its easy to onboard new team members to pagerduty platform.

This is very useful for anyone looking to automate most of the monitoring/altering tasks, get AI based recommendations on alerts and reduce the need to people manually monitoring the INC queues. It also gives an option to get an overview of services impacted and stakeholders can get timely notifications. Incident response and resolution times are also reduced as only the right people are involved in the flow.

It is best suited for numerous Support Teams with different on-call schedules. That is the scenario where we use it - so it's hard to imagine any "less appropriate" scenarios.

Well Suited: On call teams getting alerted in a timely fashion. It eliminates the need to sit by your computer all night & day refreshing you screen. you know when you need to take action

No Appropriate: i dont see the need for it in my role to be used unless on call

We utilise PagerDuty to alert on-call staff of application failures, infrastructure issues. security alerts and on-call roster management. It's very versatile and has excellent integration options including the ability to establish unique email addresses for each service. Sending an email to that address will process this email and trigger an alert that corresponds to this email. Setting this up takes minimal time, and allows the scope of the product to be expanded dramatically.

We have also utilised the PagerDuty AI to aggregate alerts, reducing alert fatigue.

If an organization lacks consistency in how on-call operations are handled or does not have a centralized way to mobilize resources quickly then PagerDuty is a fantastic option. While the platform was not originally designed for managed service providers, it can be adopted and adjusted to support multiple customers and partners. For organizations with a larger resource footprint with a wide variety of skillsets, PagerDuty makes it a breeze to get organized and get the right people on the phone when it matters.

Scenarios where PagerDuty is well suited:
If you're working on a critical environment which will eventually affect B2C then you need a really strong alerting system so that you can setup alerting and make sure the availability of systems/resources without any interruptions.

Scenarios where PD is appropriate:
When you're working on something research base projects than having a pagerduty is not appropriate.

It is very good at consolidating alerting and having a centralized location for handling all alerting across all teams. It gives good flexibility in terms of user functionality. The escalation process seems to be very mature is very configurable. It seems limited in its ability to do complex routing of alerts, if you are wanting to rule based alerting that would need to be a feature based on the application that is triggering it and not some feature in PagerDuty.

We use the opensource version as such we dont see the workflow management part of it.
We have used it extensivley for schedulling of maintenance tasks of our systems. It also helped us a lot of triggering ansible scripts to completely deploy and/or configure nodes on our cirtual infrastructure. We also use it for reporting- It becomes very diffcult ot use if you have a bunch of scripts with interdependency on passing dynamic variables between them

What more can I say? The solution is robust and reliable. The best case I have is where PD didn't only get a tech involved at the right timing but saved a fortune in IT and Electrical Controls equipment and allowed us to prevent the risk of a wastewater treatment plant in the desert from shutting down due to extensive damage. PD paged a tech after an environment management system notified us that AC went down and the temperature was rapidly rising. Had the room gotten too hot, millions of dollars of equipment would have been lost, and the water supply for a city impacted. We got the page just in time, got a tech on-site to repair the AC, and there was no impact to the city or monetary loss.

In our stacks we want to monitor for things like extreme latency, CPU usage, Memory Usage, etc. and these monitors/metrics are then sent to PagerDuty when they break certain thresholds which then allows PagerDuty to send alerts only to the on-call engineer who can go look at the issue and troubleshoot/fix as needed.

PagerDuty is well suited for business-impacting incidents that need to be tackled by developers, DevOps, SREs, IT operations, and Customer Support. The ease of integration with ticketing platforms saves time, and the escalation system allows for collaboration between people specialized in different areas. So far, the only downside I have seen to it is the lack of a straightforward way to integrate it with the sundeck community edition with a plugin for example.

PagerDuty is really well suited for support and engineering, getting an incident response team aware of what is going on -- especially after hours -- and it integrates really easily. For what the tool does, I don't know that there is a less suited use. Very happy with the alerting and the integrations.

Well suited for many microservices, we have many teams owning multiple microservices hosted on AWS. PagerDuty is perfect for engineers and SRE to keep tabs on their services 247, in particular as each service does a specific function so it's easier to tune alerts. It's less well suited for large, heavy systems where many things could be going wrong and issues are less predictable. This requires more tuning of the alerts over time to reduce noise.

Using pagerduty provides a SaaS solution ready to use, however, other (open source) solutions seem to be better suited such as the Elastic seach, Logstash and Kibana stack or Loki and Grafana. The main issue around pagerduty is the documentation. Once the documentation figured out, the implementation is pretty eazy.

PagerDuty works well when your company or your customers expect 24/7 support from engineering or other departments. It's great for managing a support rotation and tracking incidents. However, I currently work in a different organization that doesn't need production-level support on our systems, and PagerDuty is seen as more of an annoyance there. In my new organization other "low-tech" solutions like Slack push notifications are lower friction and feel more appropriate to our team.

PagerDuty is very flexible allowing users and teams to manage who is oncall, and for what escalation policies. It also provides a very robust set of APIs that allows the organization to do just about anything you can do from the PagerDuty UI. While the flexibility is great, and the API would effectively allow an organization to enforce whatever governance it wanted on how it's teams leverage PagerDuty, it doesn't have much governance out of the box. If an organization doesn't have a robust engineering team, and they want governance over how things are configured, PagerDuty may not be the solution for them. There also may not be any better options in the market.

PagerDuty is a great solution for large teams that require immediate action when things aren't going right. If your business needs urgent support provided to customers if your product fails, PagerDuty allows you to empower your team to only engage when a set of triggers are met. It also gives you back up layers to ensure issues are responded to, even if the main on-call person isn't able to be reached.

PagerDuty is great if you want a tool that integrates well with your existing infrastructure to provide digital forensics and incident responses. It is easy to set up, and has decent API integrations. It does a good job of notifying/escalating incidents to the right teams expediently, allowing for SMS, mobile app, and other options for notifying. It is also easy to set up and configure out of the box.
It's not the tool that allows for total granularity and control, but if you want that, you're probably better off building it in house. The UI and some reporting functionalities can be improved, but all in all its a solid tool for its convenience.

PagerDuty is very suitable for IT management purposes when it comes to alerting and notification about any issues in the infrastructure. The notification can be in multiple ways email, application, text message, etc.