PagerDuty’s status dashboard provides technical responders, business responders, and leaders a live, shared view of system health to improve awareness of operational issues. It displays the current status of key business services and sends notifications to alert users when business services are impacted. This feature improves communication between response teams and stakeholders during incidents.
The status dashboard feature is available on Business and Digital Operations plans. Please contact our Sales Team if you would like to upgrade to a plan including the status dashboard feature.
Designed with business stakeholders in mind, the status dashboard provides an overview of your business services' status, showing you at a glance whether any are being affected by incidents.
- Impacted, denoted by red : A business service will appear as impacted on the status dashboard when it is experiencing an active incident on one of its supporting services. A business service can become impacted by an incident automatically or manually.
- Operational, denoted by green : A business service will appear as operational when there are no active incidents impacting it.
To view the web Status Dashboard, log in to your PagerDuty account, navigate to Status in the top menu, or access via link at
To view the mobile Status Dashboard, log in to your PagerDuty account, tap the menu and tap Status Dashboard.
Required User Permissions
Managers, Admins and Account Owners can create multiple custom dashboard views.
Custom dashboards allow you to create multiple dashboards for different business units or teams with varying multiple Business Service views.
To create a new dashboard, navigate to Status and click the Business Services dropdown and select + New Dashboard.
Enter a meaningful Name, optionally edit the Custom URL and select which Business Services you would like to include in this dashboard view. Click Create Dashboard to save.
The Limited Stakeholder role provides users access to view and subscribe to the status dashboard, view their own user profile, and does not show any other parts of PagerDuty, whether they are using the web UI or the mobile app. This access level is great for teams who don't need to see all of the alerts, schedules, and responder details in your account.
To set up a Limited Stakeholder user, please visit our User Roles article.
Required User Permissions
Admin, Manager, Global Admin and Account Owner base roles.
To configure the status dashboard, you must:
Ideally, business services are:
- Recognizable to non-technical stakeholders
- Supported by one or more technical services in PagerDuty
You may have business services listed on an external status page, within a service catalog/CMDB, or defined in relation to existing health metrics from a monitoring tool.
- Go to Services and select Business Services.
- Click Create New Business Service.
- Enter a meaningful name that will define the business service and provide a description.
- Enter the owner as yourself or a point of contact for the business service. (Optional)
- Click Add Upstream Dependencies to add any technical services or business services that this service requires in order to be considered operational. For more information, please read our section on upstream dependencies.
- Click Create Business Service to save.
While it is possible to configure multiple levels of business service dependencies, only the top level business services currently appear on the Status Dashboard. A “top level” business service is a business service that is not listed as an upstream dependency for another business service.
Next, follow the instructions in our section on enabling incident priority. Only incidents with an assigned priority will automatically impact a business service and appear on the status dashboard.
During an incident, responders can update the status of a business service to indicate its disruption to business stakeholders via the status dashboard. A business service will appear as disrupted on the status dashboard in two circumstances:
Automatically when there is an open incident on any supporting technical service mapped to the business service and the incident has a priority assigned. Depending on your business service settings, this incident may need a priority assigned over a certain level. Incidents that have not been assigned a priority will not automatically appear on the status dashboard, so that it does not become cluttered with operational noise.
Manually when a user associates an incident with a business service by selecting the appropriate business service under the Impacted Business Services dropdown, found in the Status Updates tab of Incident Details. These manual incidents will appear on the Dashboard regardless of the Business Services setting in When should a business service show an incident.
Required User Permissions
Any user who has incident management permission should be able to add or remove an impacted business service from an incident.
Regarding which business services a user can add/remove — they should be able to see and add/remove any business services they can see elsewhere in the product (any non private business services for most users, different for restricted access users).
When the above criteria are not met, the business service will show as operational on the status dashboard.
When resolving an incident, responders have the option to add a resolution note. This note can also be sent to subscribers as a status update if:
- The incident has subscribers OR the incident is visible on the status dashboard
- AND the incident is resolved from the PagerDuty web app as a single resolve (versus a bulk resolve from the incident dashboard)
By checking the box Post resolution note as status update, the note will be sent to all subscribers on the incident, regardless of whether they were added via response play or added on demand through the UI.
Status update branding is available with our Modern Incident Response suite of features available on our Business and Digital Operations plans.
If you would like to change the logo that appears in your status update emails (it will be the PagerDuty logo by default), you may upload a custom logo with status update branding.
To upload a custom logo:
- Navigate to User Icon Account Settings and select the Status Updates tab.
- Click Replace Logo and upload the file from your device. Once uploaded, it is automatically saved. If you would like to preview how this logo will appear on your emails, click Preview.
If at any time you wish to switch back to the default PagerDuty logo, you can click Reset PagerDuty Logo on the right side of the screen.
Business service subscription is available with the PagerDuty Modern Incident Response suite of features available on our Business and Digital Operations Plans. Please contact our Sales team for information on subscriptions with Modern Incident Response.
Business stakeholders can subscribe to business services they care about to stay informed about those services. Any user who subscribes to a business service will receive a notification whenever a status update is posted to any ongoing incident impacting that business service. These notifications are sent via email, SMS, or push, depending on the user’s preferences. All status updates also appear on the status dashboard.
- There are three places where you can subscribe to business services:
- Via Status Dashboard: Status View My Subscriptions.
- Via User Profile: Profile Icon Subscriptions tab.
- Via PagerDuty Team: People Teams select your Team Subscriptions tab.
- Search and select the business services you wish to subscribe to, and then click Add Business Services.
- Notifications will be sent based on how you have configured your Status Update Notification Preferences.
There are three ways to set incident priority:
- Set priority manually from the web or mobile app.
- Set priority via the REST API. You can use this endpoint to get your priority_id values.
- Set priority via Event Rules. You need the Team, Business or Digital Operations plan to access this feature.
If I manually disassociate a business service from an incident, and then re-associate it, will upstream business service dependencies still show up on the Status Dashboard?
No. If the upstream dependency is removed, our system will remember that it had been disassociated and it will not show up on the Status Dashboard after it has been re-associated. Here’s an example to illustrate:
There’s a technical service for mobile push notifications where an incident has been triggered. This is linked to two business services: one for mobile push notifications, and one upstream business service for the whole mobile app. Initially when this incident is triggered, it will show both business services affected on the Status Dashboard.
After further analysis, the engineer determines only push notifications are affected, not the entire mobile app, so they remove the Mobile App Business service from impacted services and now only the Push Notifications Business Service shows as affected.
Now, if after removing the Mobile App Business service they decide to re-associate it, it will NOT automatically show the Mobile App Business Service as affected, even though it’s upstream and dependent. This is because our system remembers that it’s not the whole mobile app that’s affected, due to the engineer’s previous removal.
We’ve made large-scale changes via API to our Business Services and dependencies. Will there be any possible lag time in processing these changes on the Status Dashboard?
Yes, please be aware that large-scale changes to your business services and dependencies may temporarily impact the accuracy of the Status Dashboard.
Updated 6 days ago