Skip to main content

Product Updates
Events
Groups

Community Forums

Ask questions, find answers, get inspired

411 Topics
517 Replies
3,972 Members

Home
Getting started

Spotlight

Jump in the discussion categories to start connecting and learning with the community

PagerDuty Operations Cloud

Ask a product question

278 topics

Commons Corner

PagerDuty University

4 topics

Community Spotlight

0 topics

Contribute

0 topics

Ops.lol

0 topics

Announcements

40 topics

Starting with PagerDuty

About the Community

3 topics

PagerDuty User Onboarding

39 topics

How-tos & Best Practices

7 topics

Recently active
Help others
Categories

PagerDuty UserDutonian

Ask a product question

Direct link to specific team oncall schedule

For groups who don’t use PD, hence don’t have login to PD, but need to lookup who is oncall for a particular team, is there a url that can be given to them to view the schedule for a team? Or if a team who has an oncall schedule and want to provide a link to someone so they can see who is oncall, is that possible?

luna.aNewbie

Ask a product question

Show On Call User in AboutCard on Backstage

I’m using the pagerduty plugin in backstage and would like to add a section in the AboutCard for entities that just shows the person who is currently on call. I’ve tried using the PagerDutyEntitySmallCard, but it’s still a bit too big for me. Is there a way I could perhaps directly call the PagerDuty Api and get this information to give to the AboutCard? Or is there an easier way to go about this?

Ask a product question

backstage plugin example request (as I'm facing issues)

Hello!Below is what I’m i’m being faced with, however if there’s simply a link to any example app configs to make sure I’m not doing anything daft, then I’m happy to start there.I’m presently trying to get the plugin working on a local test I have set up in the hopes we can use it on our production system. I’ve followed the guides in the documentation, going down the events API v2 route however I’m getting the following errors[1] 2024-09-12T13:08:40.054Z pagerduty warn No PagerDuty accounts configuration found in config file. Reverting to legacy configuration. [1] 2024-09-12T13:08:40.054Z pagerduty warn No PagerDuty API token found in config file. Trying OAuth token instead... Which then goes on to fail as I’ve not set things up as per the legacy method. This is what I have in the app config (and also the local as this is where I’m running it from):pagerDuty: oauth: clientId: ${PD_CLIENT_ID} clientSecret: ${PD_CLIENT_SECRET} subDomain: ${PD_ACCOUNT_SUBDOMAIN} region: ${PD

3dmundbartonNewbie

Ask a product question

Implementing complete PD configuration via Terraform

In the configuration as code space, I’m building infra structure as code and configuration that will manage and control our config in PD (as much as possible). The main driver is to manage the configuration of this critical piece of operations more securely and without the human-in-the-loop ClickOps via the PD portal.I’m running into trouble using the PagerDuty Terraform provider when you use it to create multiple PD resources (users, services, schedules,etc) in bulk (i.e. using for-each in the terraform resource)We get failures back from the PD provider along the lines of:│ Error: Provider produced inconsistent result after apply││ When applying changes to│ pagerduty_user.service_users["<redacted>@<email>"], provider│ "provider[\"registry.terraform.io/pagerduty/pagerduty\"]" produced an│ unexpected new value: Root object was present, but now absent.││ This is a bug in the provider, which should be reported in the provider's│ own issue tracker.Question is - has anyone exp

PagerDuty Community TeamCommunity Manager

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

PagerDuty Community TeamCommunity Manager

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

PagerDuty Community TeamCommunity Manager

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

PagerDuty Community TeamCommunity Manager

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

PagerDuty Community TeamCommunity Manager

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

PagerDuty Community TeamCommunity Manager

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

luna.aNewbie

Ask a product question

Show On Call User in AboutCard on Backstage

I’m using the pagerduty plugin in backstage and would like to add a section in the AboutCard for entities that just shows the person who is currently on call. I’ve tried using the PagerDutyEntitySmallCard, but it’s still a bit too big for me. Is there a way I could perhaps directly call the PagerDuty Api and get this information to give to the AboutCard? Or is there an easier way to go about this?

Ask a product question

backstage plugin example request (as I'm facing issues)

Hello!Below is what I’m i’m being faced with, however if there’s simply a link to any example app configs to make sure I’m not doing anything daft, then I’m happy to start there.I’m presently trying to get the plugin working on a local test I have set up in the hopes we can use it on our production system. I’ve followed the guides in the documentation, going down the events API v2 route however I’m getting the following errors[1] 2024-09-12T13:08:40.054Z pagerduty warn No PagerDuty accounts configuration found in config file. Reverting to legacy configuration. [1] 2024-09-12T13:08:40.054Z pagerduty warn No PagerDuty API token found in config file. Trying OAuth token instead... Which then goes on to fail as I’ve not set things up as per the legacy method. This is what I have in the app config (and also the local as this is where I’m running it from):pagerDuty: oauth: clientId: ${PD_CLIENT_ID} clientSecret: ${PD_CLIENT_SECRET} subDomain: ${PD_ACCOUNT_SUBDOMAIN} region: ${PD

3dmundbartonNewbie

Ask a product question

Implementing complete PD configuration via Terraform

In the configuration as code space, I’m building infra structure as code and configuration that will manage and control our config in PD (as much as possible). The main driver is to manage the configuration of this critical piece of operations more securely and without the human-in-the-loop ClickOps via the PD portal.I’m running into trouble using the PagerDuty Terraform provider when you use it to create multiple PD resources (users, services, schedules,etc) in bulk (i.e. using for-each in the terraform resource)We get failures back from the PD provider along the lines of:│ Error: Provider produced inconsistent result after apply││ When applying changes to│ pagerduty_user.service_users["<redacted>@<email>"], provider│ "provider[\"registry.terraform.io/pagerduty/pagerduty\"]" produced an│ unexpected new value: Root object was present, but now absent.││ This is a bug in the provider, which should be reported in the provider's│ own issue tracker.Question is - has anyone exp

PagerDuty Operations Cloud

Ask product questions, access official documentation, give feedback and suggest new features

Ask a product question

Ask a product question

278 topics
438 Replies

Commons Corner

Introduce yourself to the community, keep up with all things community and PagerDuty, share tech-related jokes and celebrate outstanding community members

PagerDuty University

PagerDuty University

4 topics
0 Replies

Community Spotlight

Community Spotlight

0 topics
0 Replies

Contribute

0 topics
0 Replies

Ops.lol

0 topics
0 Replies

Announcements

40 topics
Replies

Starting with PagerDuty

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

About the Community

About the Community

3 topics
0 Replies

PagerDuty User Onboarding

PagerDuty User Onboarding

39 topics
0 Replies

How-tos & Best Practices

How-tos & Best Practices

7 topics
0 Replies

Events Calendar

Leaderboard

More for you

Ops Guides

Expert-level, in-depth, and practical guides for practitioners

Knowledge Base

Learn about PagerDuty, get support and find latest releases

Developer Platform

Customize your experience with with PagerDuty APIs

PagerDuty University

Your source for on-demand PagerDuty training

Powered by Gainsight

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.

OK

This file cannot be downloaded

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

OK