Pagerduty.com
Knowledge Base
OPS Guides
Developer
PagerDuty University

Product Updates
Events
Groups

Introducing PagerDuty Commons - Your New Digital Ops Community Hub!

2 months ago

Home
Getting started
Starting with PagerDuty

Starting with PagerDuty

Onboarding materials and best practices for new PagerDuty users, admins and managers

43 Topics

Recently active

Most replies Most views Newest first

PagerDuty Community TeamCommunity Manager

published in About the Community

Introducing PagerDuty Commons - Your New Digital Ops Community Hub!

Whether you’re building an incident workflow, a CI/CD pipeline and need help with an issue, integrating PagerDuty with monitoring tools and want to check out best practices, or just finished tackling a critical incident and could use some time to relax and chat with fellow digital operations professionals that understand your challenges, PagerDuty Commons is the place for you.The rebranded PagerDuty community is designed to be a common space where PagerDuty practitioners, developers, and digital operations enthusiasts get together to collaborate, learn, and share all things about real-time critical work management – besides getting up to speed with latest trends and technologies in the DevOps, sysadmin, SRE, and platform engineering fields. By joining and actively participating in the community, members open doors to a box of opportunities and resources that can enhance their career and technical expertise.All resources in one stopNeed help with a tricky issue? Want to swap tips and tr

1541

1 month ago

PagerDuty Community TeamCommunity Manager

published in PagerDuty User Onboarding

Retrieving Service Graph via the PagerDuty REST APITutorial

We had an interesting question on the PagerDuty Community forums regarding how to retrieve the list of services that make up a service graph using the PagerDuty REST API.Service graphs can be made up of a mix of technical and business services, called dependencies, but the most common starting place for them is with a business service. How you organize your business service is really a matter of what makes sense for your teams. There is no single endpoint query that will dump an entire service graph supporting a business service, so to get access to the whole graph, you’ll need to walk the graph. Sample GraphIn my test account I have a set of services that make up my “Fabulous Shop”. Fabulous Shop is my business service. It is supported by another business service, Shipping Service. Fabulous shop has 5 technical dependencies: a frontend, a search backend, a cache, a shopping cart, and a database. The cache and the shopping cart both depend directly on the database. The service graph l

210

2 months ago

PagerDuty Community TeamCommunity Manager

published in PagerDuty User Onboarding

Reporting: Using PagerDuty API to Create Custom Reports

Our customers have created all kinds of reports using our REST API to drill down on metrics and data that are important to them. Here are some examples:REST API v2 Incident details and body – This Python script exports all incident details for a specific incident or range of incidents and includes the incident body. Opsweekly – Etsy created this handy, multi-purpose tool with the premise that on-call time should be quantified. It generates a weekly report and lets on-call engineers track their notifications to assess the signal-to-noise ratio of the alerting system.Over time, your team can gather enough data to get in depth reports like, for example, what alerts wake people up the most, the average alert volume per day, and on-call improvements over the last year.Engineers can also integrate their Opsweekly to their Fitbits or Jawbone UPs to provide insight into how being on-call is affecting them. It tracks lost sleep time and Mean Time to get back to Sleep (MTTS), and provides data t

330

2 months ago

PagerDuty Community TeamCommunity Manager

published in How-tos & Best Practices

Response Cycle - Step 4: Resolving Incidents Through Collaboration

There are 5 steps in the Incident Response Cycle: Response Cycle - Step 1: Optimizing your Alerting ↗️Response Cycle - Step 2: Notifying the right people at the right time ↗️Response Cycle - Step 3: Assessing the impact of an incident ↗️Response Cycle - Step 4: Resolving Incidents Through Collaboration ↗️Response Cycle - Step 5: Preventing problems from recurring ↗️Addressing each step in the incident response cycle will ultimately help your team drive down incident resolution times by (1) focusing on actionable alerts, (2) getting the right people to review those alerts, and (3) understanding the full impact of the problem so that (4) the appropriate remediation steps can be taken and (5) reviewed to make sure the same problem does not happen again.In this article, we will discuss Step 4: Resolve.What does “Resolve” mean?Resolving means coordinating a response, collaborating with others, and surfacing as much information as possible to try to resolve an incident quickly. When you maxi

180

2 months ago

PagerDuty Community TeamCommunity Manager

published in How-tos & Best Practices

The Value of Analytics

Analytics are a great way to provide additional insights regarding metrics and numbers into your incident management cycle. Through our Analytics in our lite plans, users can view reports in regards to their notifications and incidents and through Analytics in our Standard and Enterprise plans, users can view data on Systems, Teams, and Users.The value that analytics can bring to teams includes being able to track: How long someone has been on-call forAre they on-call too frequently? How many incidents have they been notified for? Are they at any risks of experiencing alert fatigue? Managers can use this information to track and see how their users are feeling while they are on-call and make the appropriate adjustments.See the noisiest services to modify their alerting through email filters/event rules or high/low urgenciesThis will help ensure that all incidents that on-call users receive will be actionable and prevent them from alert fatigue.Compare the MTTR/MTTA with other teams, se

2 months ago

PagerDuty Community TeamCommunity Manager

published in PagerDuty User Onboarding

PagerDuty University: Instructor-Led Training

PagerDuty offers tailored instructor-led training sessions that cover both foundational and advanced topics, ensuring flexibility in scheduling and location to meet your team’s specific needs! Browse all instructor-led trainings and enroll: PagerDuty University Instructor-Led Training

2 months ago

PagerDuty Community TeamCommunity Manager

published in PagerDuty User Onboarding

PagerDuty University: Certifications

Whether you’re an IT professional, a developer, or a business leader, PagerDuty certifications validate your expertise in optimizing your organization’s response to incidents, ensuring maximum uptime, and minimizing downtime.PagerDuty University offers a unique blend of product and thought-leadership certifications, focused on skills that are highly sought after in today’s digital world. Join the community of certified PagerDuty professionals who are shaping the future of real-time operations! Learn more and enroll: PagerDuty University Certification

150

2 months ago

PagerDuty Community TeamCommunity Manager

published in How-tos & Best Practices

Response Cycle - Step 2: Notifying the right people at the right time

There are 5 steps in the Incident Response Cycle: Response Cycle - Step 1: Optimizing your Alerting ↗️Response Cycle - Step 2: Notifying the right people at the right time ↗️Response Cycle - Step 3: Assessing the impact of an incident ↗️Response Cycle - Step 4: Resolving Incidents Through Collaboration ↗️Response Cycle - Step 5: Preventing problems from recurring ↗️Addressing each step in the incident response cycle will ultimately help your team drive down incident resolution times by (1) focusing on actionable alerts, (2) getting the right people to review those alerts, and (3) understanding the full impact of the problem so that (4) the appropriate remediation steps can be taken and (5) reviewed to make sure the same problem does not happen again. In this article, we will discuss Step 2: Notify.What does “Notify” mean?Notifying means alerting the right people at the right time about an alert. When you leverage tools to notify your team properly, the right people can come together qu

180

2 months ago

PagerDuty Community TeamCommunity Manager

published in PagerDuty User Onboarding

Best practices with Using Advanced Permissions

Advanced Permissions allow you to specify different levels of permissions for users across your PagerDuty account and within your team. These levels of permissions include object-level permissions, team-level permissions, and account-level permissions. You can read more about advanced permissions here.If you’re interested in adopting advanced permissions within your organization, consider the following best practices tips:1. Follow the principle of least privilege: Grant users as much access as they need to be effective in their role. In practice, this means you’ll want to limit the number of users with a Global Admin or Manager base role, especially at larger organizations. Everybody else should have either an observer, responder , or restricted access base role with additional permissions given at either the team or object level.2. Add all users and escalation policies to a team to set team roles: Team roles give users specific access to a team, especially when they have limited acce

2 months ago

PagerDuty Community TeamCommunity Manager

published in How-tos & Best Practices

Response Cycle - Step 1: Optimizing your Alerting

There are 5 steps in the Incident Response Cycle. Response Cycle - Step 1: Optimizing your Alerting ↗️Response Cycle - Step 2: Notifying the right people at the right time ↗️Response Cycle - Step 3: Assessing the impact of an incident ↗️Response Cycle - Step 4: Resolving Incidents Through Collaboration ↗️Response Cycle - Step 5: Preventing problems from recurring ↗️ Addressing each step in the incident response cycle will ultimately help your team drive down incident resolution times by (1) focusing on actionable alerts, (2) getting the right people to review those alerts, and (3) understanding the full impact of the problem so that (4) the appropriate remediation steps can be taken and (5) reviewed to make sure the same problem does not happen again.In this article, we will discuss Step 1: Optimize. What does "Optimize" mean?Optimizing means configuring your monitoring and alerting such that only actionable events receive immediate attention and non-actionable events are categorized d

400

2 months ago

PagerDuty Community TeamCommunity Manager

published in PagerDuty User Onboarding

Responding to IncidentsTutorial

This article walks through how to respond to an incident when you’re on call. First, make sure your user profile is set up to receive notifications. You’ll define your contact methods (where you want to be contacted) and your notifications rules (how you want to be contacted).Next, let’s review how incidents are created. Typically a monitoring tool will detect an issue and send an event to PagerDuty. PagerDuty receives this event and creates an incident against a PagerDuty service. Tools can integrate with PagerDuty via API or email, or incidents can be manually triggered in the web app. If you are on-call for the service with the triggered incident, you will receive a notification via your preferred notification rules 1.Acknowledge or ReassignWhen you receive the notification, the first step is to acknowledge the incident if you are going to be taking ownership. This will assign the incident to you and stop it from escalating to the next person on call.If the incident belongs to anoth

190

2 months ago

PagerDuty Community TeamCommunity Manager

published in PagerDuty User Onboarding

PagerDuty University: On-Demand FREE Courses

PagerDuty University offers a self-paced and fully on-demand learning resource that brings together dozens of free courses that walk learners through every step of the process of using PagerDuty. The entirely free courses detail the setting up, the scheduling, the mobile app, and more.From PagerDuty 101 to Thought Leadership, learn at your own pace with PagerDuty University’s on-demand courses! Find more and enroll: PagerDuty University On-Demand

110

2 months ago

PagerDuty Community TeamCommunity Manager

published in About the Community

What Other Channels Can I Use to Engage with the PagerDuty Community?

Looking to connect with the PagerDuty community beyond this online hub? Here are some great channels to consider:YouTube and LinkedIn Lives: Tune into our live sessions on YouTube and LinkedIn for real-time discussions, demos, and community updates. These platforms offer a dynamic way to interact with experts and fellow users.Social Media: Follow us on Twitter, Facebook, and Instagram for the latest news, tips, and community spotlights. Engaging with our social media accounts is a great way to stay informed and join conversations.In-Person Conferences & Meetups: Attend our conferences and local meetups to network with other PagerDuty enthusiasts, participate in workshops, and gain hands-on experience.Page it to the Limit Podcast: Don’t miss our Page it to the Limit podcast for in-depth discussions on industry trends, expert insights, and community stories. It’s an excellent way to stay engaged while on the go.Explore these channels to expand your connections, deepen your knowledge,

130

2 months ago

PagerDuty Community TeamCommunity Manager

published in PagerDuty User Onboarding

Integrations: Setting up Services and IntegrationsTutorial

A PagerDuty Service may represent an application, component, or team you wish to open incidents against.PagerDuty enables you to model your services as they actually exist within your infrastructure. You can drive more clarity and accountability by aligning services with component ownership so that the alerts your responders receive are not just from siloed tools.We recommend keeping the following items in mind when setting up your services:Reduce confusion with services and integrations by agreeing on naming conventionsIt’s common for multiple teams across an organization to use the same tools. Thus, it wouldn’t be very helpful for each team to name one of their services “Datadog”. Get together with your team and come up with naming conventions that everyone can use to differentiate their service with another team’s service.Some things you might want to include in your service names:Team namesBusiness UnitProduction environmentsProduct/featurePriority levelIntegration/Monitoring tool

190

2 months ago

PagerDuty Community TeamCommunity Manager

published in PagerDuty User Onboarding

Sample WorkflowsTutorial

PagerDuty can be integrated into different kinds of workflows. When thinking about how you want to integrate PagerDuty into your workflow, consider 2 things: How PagerDuty incidents will be triggered How users should respond to PagerDuty incidentsHere we document a few sample workflows for different types of teams:Workflow for a DevOps team Workflow for a CentralOps organizational structure Workflow for a NOC Workflow for a support/helpdesk/MSP team Workflow for a DevOps teamDevOps teams have direct ownership over the services that they build and deploy, meaning they are also responsible for being on-call should any issues arise.PagerDuty incidents are immediately assigned to the team who owns the impacted servicePagerDuty incidents are escalated to back-up on-call responders and managers How PagerDuty incidents are triggered?For a DevOps team, PagerDuty incidents are mostly triggered automatically either via email or via the API.How users respond to PagerDuty incidents?Generally, user

120

2 months ago

PagerDuty Community TeamCommunity Manager

published in How-tos & Best Practices

Response Cycle - Step 5: Preventing problems from recurring

There are 5 steps in the Incident Response Cycle: Response Cycle - Step 1: Optimizing your Alerting ↗️Response Cycle - Step 2: Notifying the right people at the right time ↗️Response Cycle - Step 3: Assessing the impact of an incident ↗️Response Cycle - Step 4: Resolving Incidents Through Collaboration ↗️Response Cycle - Step 5: Preventing problems from recurring ↗️ Addressing each step in the incident response cycle will ultimately help your team drive down incident resolution times by (1) focusing on actionable alerts, (2) getting the right people to review those alerts, and (3) understanding the full impact of the problem so that (4) the appropriate remediation steps can be taken and (5) reviewed to make sure the same problem does not happen again.In this article, we will discuss Step 5: Prevent.What does “Prevent” mean?Preventing means reviewing metrics, uncovering trends and patterns, and making improvements to your infrastructure, monitoring thresholds, or team performance. When

200

2 months ago

PagerDuty Community TeamCommunity Manager

published in PagerDuty User Onboarding

Integrations: Making it Easier for Teams to Trigger Incidents

Incidents can come to PagerDuty in many different ways. Often times, events are automatically sent to PagerDuty via the Events API when certain thresholds are met in your monitoring tools. However, there may be some instances when a user needs to manually trigger an incident, or perhaps you need a way for other teams (outside PagerDuty) to page the on-call responder for a critical issue.Check out the below suggestions to make it easier for teams to trigger incidents and notify on-call responders.Send an email from your inbox to trigger an incidentThe easiest way to trigger an incident (without logging in or being a user in PagerDuty) is by sending an email.If you have an email integration 1 set up on your account, you can have people within your organization (or even your customers) send an email to one of your integration’s email addresses. This will then trigger an incident in PagerDuty and notify who is on-call.Here are some ideas for managing these email addresses: Post the relevan

2 months ago

PagerDuty Community TeamCommunity Manager

published in How-tos & Best Practices

Response Cycle - Step 3: Assessing the impact of an incident

There are 5 steps in the Incident Response Cycle: Response Cycle - Step 1: Optimizing your Alerting ↗️Response Cycle - Step 2: Notifying the right people at the right time ↗️Response Cycle - Step 3: Assessing the impact of an incident ↗️Response Cycle - Step 4: Resolving Incidents Through Collaboration ↗️Response Cycle - Step 5: Preventing problems from recurring ↗️Addressing each step in the incident response cycle will ultimately help your team drive down incident resolution times by (1) focusing on actionable alerts, (2) getting the right people to review those alerts, and (3) understanding the full impact of the problem so that (4) the appropriate remediation steps can be taken and (5) reviewed to make sure the same problem does not happen again.In this article, we will discuss Step 3: AssessWhat does "Assess" mean?Assessing means understanding the full scale and impact of an alert or wide-spread incident. It answers the question “How bad is it?” and determines how the alert or inc

2 months ago

PagerDuty Community TeamCommunity Manager

published in PagerDuty User Onboarding

Incidents: Creating Transparency Across Teams

Often times, it’s not just the people on-call who need to know about an incident. Managers and other parts of the business (Support, Sales, etc) may also need to be aware of incidents that arise. Whether these teams are in PagerDuty or not, there are many ways to keep others informed about incidents and events that are triggered in PagerDuty.Here are some of our recommendations and best practice tips for creating transparency in your organization:Creating transparency for users that exist in PagerDuty Add managers to escalation policiesTo increase visibility into alerts on certain services and escalation policies, a manager (or any other user/schedule) can be added to the first-level of an escalation policy along with the first user/schedule on-call so that the manager is notified about incidents that are triggered.Additionally, if the manager added status update notification rules to their profile, they can gain even more visibility into incidents with alerts, but setting up notificat

2 months ago

PagerDuty Community TeamCommunity Manager

published in PagerDuty User Onboarding

Integrations: Using Multiple Integrations Per Service to Represent your Systems

With the ability to add more than one integration per service, PagerDuty enables you to model your services as they actually exist within your infrastructure. Benefits include:The ability to drive more clarity and accountability by aligning services with component ownership so that alerts are not just from siloed tools Creating a single, consolidated service dashboard in PagerDuty for each of your internal systems Better control of maintenance windows for a particular service Responders will be able to more easily diagnose which system is having problems, leading to lower resolution times Better leverage PagerDuty’s analytics capabilities for a more complete view of which systems are having problems. Reporting by service on the System Report will show accurate incident counts, MTTA, MTTR, and escalation counts for all monitoring tools tied to each system, not just one. This also allows you to see which components are healthy, and which are having consistent problems that may need to be

2 months ago

PagerDuty Community TeamCommunity Manager

published in PagerDuty User Onboarding

Some Opinions on “How should I set up my Pager Notifications?”

An extremely common question that I receive when introducing a new team to PagerDuty (or any notification tool, really), is “how should I set up my notifications?”Here’s an answer that has worked well for me.A Sample Notification Escalation policyNotify on AssignmentThis is a sample notification policy to alert me when an incident is assigned to me. It’s intention is to be “helpfully persistent”. This is catered to my order-of-notification preference, as well as my “dexterity issues” during the wee hours. Feel free to tweak as desired.| Timeframe | Method || ----------- | ------ || Immediately | Email || Immediately | Push || 1 Minute | Push || 2 Minutes | SMS || 3 Minutes | Call |One common mistake is to have all notification types trigger at the same time. Unfortunately, what ends up happening is that in the time that it takes you to start responding to the one notification, another will trigger on top of the first. You can’t acknowledge the Push Notification before the SMS comes in,

2 months ago

PagerDuty Community TeamCommunity Manager

published in PagerDuty User Onboarding

PagerDuty Analytics Best Practices

Table of ContentsPagerDuty Analytics features are powered by use of the PagerDuty product platform. While all customers can get value from PagerDuty Analytics, proper use and configuration of certain features that are available in all plans can enhance the value of this add-on product.User TimezonesThroughout the various PagerDuty Analytics user experiences, metrics are often surfaced by time of day. In order to understand the true impact of incidents on responders, all users should ensure that the timezone is set accordingly in their user profile.TeamsOperational Review Analytics uses PagerDuty’s Teams feature to segment views into the data. Ensuring that teams are defined, match your org chart, and all users are a member of at least one team will result in a richer PagerDuty Analytics experience. Check out our Knowledge Base article on Team On-Call Handoff Reviews for more details.ServicesThe Service object in PagerDuty can be used in a variety of ways, but it is a best practice to s

2 months ago

PagerDuty Community TeamCommunity Manager

published in PagerDuty User Onboarding

Reporting: Operational Metrics You Should Track

Note: The content below was originally published on our PagerDuty blog.Living in a data-rich world is a blessing and a curse. Flexible monitoring systems, open APIs, and easy data visualization resources make it simple to graph anything you want, but too much data quickly becomes noisy and un-actionable.We’ve blogged, spoken, and thought hard about what you should monitor and why from a systems perspective, but what about monitoring data on your operations performance? We worked with with a large number of PagerDuty customers as we built out our new Advanced Reporting feature, including some of the most sophisticated operations teams out there. We’d like to share some specific metrics and guidelines that help teams measure and improve their operational performance.Raw Incident CountA spike or continuous upward trend in the number of incidents a team receives tells you two things: either that team’s infrastructure has a serious problem, or their monitoring tools are misconfigured a

2 months ago

PagerDuty Community TeamCommunity Manager

published in PagerDuty User Onboarding

Activity Report Metrics - What They Mean and How to Use Them

Welcome! This page is intended to shed more light on your Activity Report metrics - what we recommend as best practice and why these data points matter.Your email might contain some of the following data points:1. Number of high-urgency incidents - Incidents that require immediate responseMTTA (Mean time to Acknowledge): The average time between when an incident is triggered, and it is acknowledged by a user. Reassign, resolve, and escalation actions do not imply acknowledgement.MTTR (Mean time to Resolve): The average time between when an incident is acknowledged, and when it is resolved by a user.*Tip: You can view this at anytime by going to: https://YOURSUBDOMAIN.pagerduty.com/analytics/dashboards/operational-maturity2. Responders added to an incident - This includes actions like escalating, reassigning, and/or adding additional responders.What does your data point mean?NULL : No incident collaboration, could be signs of a siloed workflowTip: Try leveraging Response Plays to loop i

2 months ago

PagerDuty Community TeamCommunity Manager

published in PagerDuty User Onboarding

Notifications: Suggestions on When to Notify One vs Many

Multi-User Alerting is the ability to notify multiple users (up to 10 users/schedules on Lite and Basic plans, up to 50 on Standard and Enterprise plans) at once when an incident has been triggered within a service. Multi-User Alerting looks like this in an escalation policy, with multiple people and schedules listed for one escalation rule:Single-User Alerting notifies one person or one on-call schedule when an incident is triggered. Single-User Alerting looks like this in an escalation policy, with one person or schedule listed for one escalation rule:So when should you use one type of notification over the other? Single-User AlertingSingle-User Alerting works best for:Notifying one person at a timeIf one person tends to be the main escalation point for an open incident, then you will want to use Single-User Alerting. Single-User Alerting works best when you have a clearly definable escalation path that would only notify one person at a time.Allowing one person to focus on an issueWi

130

2 months ago

Page 1 / 2

Badge winners

confusedhas earned the badge First Responder
bschiffhas earned the badge First Responder
Christian VanderZielhas earned the badge First Responder
Vitohas earned the badge First Responder
ajsumohas earned the badge First Responder

Show all badges

Terms & Conditions Cookie settings

Sign up to PagerDuty Commons

Already have an account? Login

Username *

E-mail address *

I want to receive marketing from PagerDuty Marketing.

(Private)

Your selection will not be visible to other community members.

Yes No

Password *

I agree to the PagerDuty Website Terms of Use, Privacy Policy, and Community Policy.

loginBox.register.email_repeat

Login to PagerDuty Commons

No account yet? Create an account

Username or Email

Password

Remember me

Forgot password?

Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.

Enter your e-mail address

Back to overview

Scanning file for viruses.

Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.

This file cannot be downloaded

Sorry, our virus scanner detected that this file isn't safe to download.

Platform

Incident Management AIOps Automation Business Operations Developer Platform Enterprise-Class Platform Digital Operations Management Generative AI What's New

Solutions

Incident Management Transformation Operations Center Modernization Automation Standardization Customer Experience Operations Digital Operations Resiliency Scaled Service Ownership Remote-Location Operations

Resources

Resources Library Community Forum Ops Guides Customer Stories Integration Guides PagerDuty University Knowledge Base Blog Demo All Use Cases

Company

About PagerDuty Leadership Newsroom Events PagerDuty.org Investor Relations Suppliers Careers Awards

Support

System Status Help & Support Partner with PagerDuty Contact Us Legal Services FAQs Accessibility