The service profile provides a high-level view of current context on a service's details. When collaborating across teams, you can see at-a-glance who owns the service, who’s on-call, or how to contact the Team responsible for the service. To access a service’s profile, navigate to Services Service Directory and click the desired service’s name.
The name and description of the PagerDuty service. Managers of a service and Global Admins can edit a service name or description inline by clicking the Edit button. For best practices on naming your services, please see our Service Configuration Guide.
The status is the current state of the service with regards to whether there are any open incidents.
- No Open Incidents: There are currently no open incidents on the service.
- Awaiting Response: There are one or more open incidents on the service with a Triggered status that have not been Acknowledged yet.
- Response in Progress: There are one or more open incidents on the service with an Acknowledged status.
- Disabled: The service is currently disabled and will not trigger any new incidents.
- Maintenance: The service is currently in maintenance mode.
Status takes the following precedence:
Disabled Maintenance Window Active with/without incidents.
The current user(s) on call for the service. This will display the full list of users on call at the first level of the escalation policy. If no one is currently on call for the service, this information will be highlighted so that you can easily identify gaps in on-call coverage.
The escalation policy being used by the service. You may click the name of the escalation policy to view its details.
The Team that is associated with this service. If your account does not have the Teams feature available, the escalation policy associated with this service will be displayed instead.
The Communication Channel field allows you to configure a link back to your preferred communication channel where the service’s owner and/or Team can best be reached. This may be an email, URL to a Slack channel, or a link to another form of contact.
The Communication Channel added here is for your Teams’ internal use, and doesn’t impact any webhooks you may have configured.
The Activity tab gives an overview of your service’s activity related to incidents, change events, suppressed alerts and maintenance windows.
The Open Incidents table allows you to view open incidents on your service, search by incident ID and take bulk actions such as acknowledge, resolve, merge or snooze.
If your service has a change events integration configured, the Recent Changes section will provide a list of the most recent change events that have taken place on the service. You will be able to view the change event Summary, Type of integration and the Created date and time. To view more details about the change event, click the Summary title.
If your service does not have a change events integration configured, there will be an empty table with the ability to Add a Change Integration on the right.
The Resolved Incidents table allows you to view resolved incidents on your service, search by incident ID, or merge resolved incidents.
If there are event rules that suppress specific alerts for your service, you can view some of the most recent alerts in the Suppressed Alerts table.
If you have maintenance windows on your service, they will be listed in the Maintenance Windows section in order of when they are scheduled.
The Integrations tab includes any integrations and extensions that you connect to and receive PagerDuty alerts from.
In the Integrations section, you can view and configure inbound integrations to send events to the service. You can also copy an integration key by clicking the clipboard icon next to it:
- Navigate to Services Service Directory click the name of your desired service select the Integrations tab click Add a new integration.
- Enter an Integration Name in the format
- There are three integration types:
a. Select a Tool: Check to see if we have an existing integration for your service. Search for your service by clicking on the dropdown menu next to Integration Type.
b. Integrate via Email: If the tool you are integrating with this service can send email, you can create an integration email address.
c. Use our API directly: If the tool you are integrating with this service is able to make HTTP calls, you can trigger, acknowledge, and resolve incidents via our API. Our developer documentation provides several examples.
- Click Add Integration.
To edit an existing integration:
- Navigate to Services Service Directory click the name of your desired service select the Integrations tab click the Name of your desired integration click Edit Integration.
- On the next screen you may edit the Integration name, copy or Generate a new integration key and select how you would like alerts to be deduplicated in the Deduplicate on dropdown.
- Click Save changes.
To edit Alert and Incident Settings:
- Navigate to Services Service Directory click the name of your desired service select the Integrations tab click Edit next to Alert and Incident Settings.
- Select whether you would like to Create both alerts and incidents or Create incidents only.
- Click Save Changes.
The Response tab includes settings that help your team respond to incidents.
To edit these settings, you can click Edit and then change the default settings. There are four options to configure how your team is notified for an incident:
- High-urgency notifications, escalate as needed: Any incidents triggered with this setting will notify the on-call responder based on the high-urgency notification settings on their profile and the incident will escalate using escalation policy rules.
- Low-urgency notifications, do not escalate: Any incidents triggered with this setting only notify the current on-call responder based on the low-urgency notification settings on their profile, and it will not escalate the incident.
- Dynamic Notifications based on alert severity: Notify users about incidents classified as either high or low based on the criticality defined by the integrated monitoring tool.
- Based on support hours: Responders will only be notified within your predefined Support Hours. You may designate specific notification settings during and outside of Support Hours. Optional: You may also choose to check the Raise urgency of unacknowledged incidents to high checkbox.
You can learn more in our Configurable Service Settings article.
Remediate incidents faster with a link to your team’s runbook for triaging incidents, or a custom incident action.
Coordinate responders and stakeholders by automatically adding a default conference bridge to incidents on this service and immediately run a response play to engage stakeholders.
Service Dependencies can be used to define other technical or business services that your service uses or is used by your service. If an issue arises on your service or one of the dependencies you have configured, you can use the impact tab to quickly assess the scope of the impact.
You can expand each technical service to see details such as the associated escalation policy and who is currently on-call.
Navigate to Services Service Directory and click the title of your desired service.
Select the Impact tab. There are two sections: Add/Edit services that this service uses or add/edit ones that this service is used by. Click Add services or Edit Services to add/edit to your desired use case.
On the Edit Services screen, you may search by service name, or select one from the Business Services or Technical Services tabs.
- To add a service dependency: Click the button to add your preferred service(s); you may add multiple Business and Technical services. Optional: You may also create a new Business or Technical service from this screen by clicking Create a New Business Service or Create a New Technical Service from each of their corresponding tabs. This will open the Business Service or Technical Service configuration screen in a new tab.
- To remove a service dependency: Click the button next to the service name.
Click Save Changes.
You may view and add Service Dependencies from incidents using our Technical Service Dependencies for Triage feature.
Suggested Service Dependencies uses machine learning to suggest other services that may depend on your service, or that your service depends on. If incidents on your service tend to be followed by incidents on another service, or vice versa, Suggested Technical Service Dependencies will be provided. This feature ensures that a service’s dependency topography is continually up-to-date as your technical infrastructure evolves and changes. You may view Suggested Service Dependencies on individual services’ Impact tabs or on an active incident, which will have a blue pill with the number of suggested dependencies, if they are available:
- Navigate to Services Service Directory click your desired service’s name Impact tab. If your service has suggested dependencies, you will be able to view them by clicking the blue Suggested Technical Dependencies dropdown. If the machine learning algorithm has not detected any suggested dependencies, this blue dropdown will not be available.
- To add a Suggested Service Dependency: Click the next to the service name. To dismiss a Suggested Service Dependency: If you do not feel that a Suggested Service Dependency correlates with your service, click the next to the service name to dismiss the suggestion. Please Note: Once you dismiss a suggestion, it will never be shown again as a suggestion. If you change your mind, however, you may always manually add that dependency.
- We’ve replaced the view of all incidents with an Activity Timeline to better highlight the most recent changes and incidents for the service.
- We have added Suppressed Alerts as well as Maintenance windows so you can see related information that may be impacting a service.
- We’ve added Runbooks and Communication Channel metadata to enrich your Service information.
- We’ve consolidated various configuration settings on a single, user-friendly page with inline editing.
I already have a Slack channel configured for my service, why is it not appearing under Communication channel?
Communication channels are configured separately from Slack extensions for the service. You may have a channel where you’ve configured your PagerDuty notifications to appear, but the Communication channel should be where other teams can best reach out to your team. This may or may not be the same as the channel where your Slack extension is configured.
Updated 17 days ago