Bring the power of PagerDuty to Backstage! The PagerDuty plugin reduces the cognitive load on developers responsible for maintaining services in production. Instead of having to go to PagerDuty's console, you can now access the necessary information directly within Backstage. This includes finding active incidents or opening a new incident, reviewing recent changes made to the service, and checking who is on-call.
- Trigger New Incident - Easily create new incidents for your service directly from Backstage. This feature saves time and reduces the need for context switching.
- See Active Incidents - View all active incidents for a service directly in Backstage.
- Check for Recent Changes - Identify recent changes that may be the root cause of potential issues with your service.
- Identify On-Call Personnel - Quickly determine who is responsible for a failing service and resolve the incident as quickly as possible. This feature allows companies to spend more time solving problems rather than determining who should solve them.
- Map existing PagerDuty services to Backstage entities - Leverage PagerDuty's Advanced Configuration page to map existing PagerDuty services to Backstage entities without code changes.
Find the complete project's documentation here.
The installation of the PagerDuty plugin for Backstage is done with yarn as all other plugins in Backstage. This plugin follows a modular approach which means that every individual component will be a separate package (e.g. frontend, backend, common). In this case, you are installing a frontend plugin.
To install this plugin run the following command from the Backstage root folder.
yarn add --cwd packages/app @pagerduty/backstage-plugin
To configure this frontend plugin follow the instructions on the Getting Started
section of the project's documentation here.
If you need help with this plugin, please open an issue in GitHub, reach out on the Backstage Discord server or PagerDuty's community forum.
If you are interested in contributing to this project, please refer to our Contributing Guidelines.