Pagerduty Escalations
A Charlesbot plugin to create an incident in Pagerduty and assign it to a specific service.
How does this work
This plugin adds the following two !help targets:
!lassie <service> [optional message] - Triggers a Pagerduty incident and assigns it to that service
!lassie services - Lists all the available Pagerduty services
Creating an escalation event triggers an incident in Pagerduty and assigns it to the specified service. Using a Slack interface that people are already comfortable with, this could be a very useful and efficient way of getting the attention of the right people during an emergency.
Installation
pip install charlesbot-pagerduty-escalations
Instructions for how to run Charlesbot are over at https://github.com/marvinpinto/charlesbot!
Configuration
First off, create one or more services in Pagerduty of type Generic API. This plugin makes use of a service’s Integration Key to trigger escalation events.
In your Charlesbot config.yaml, enable this plugin by adding the following entry to the main section:
main:
enabled_plugins:
- 'charlesbot_pagerduty_escalations.pagerdutyescalations.PagerdutyEscalations'
Then add a pdescalations dictionary block that looks something like:
pdescalations:
service_mappings:
service_one_name: 's1_pd_key'
service_two_name: 's2_pd_key'
The name that you assign your service will be the name that shows up when a person issues the !lassie services command. The corresponding key here is the Integration Key associated with that service (in Pagerduty).
Sample config file
main:
slackbot_token: 'xoxb-1234'
enabled_plugins:
- 'charlesbot_pagerduty_escalations.pagerdutyescalations.PagerdutyEscalations'
pdescalations:
service_mappings:
service_one_name: 's1_pd_key'
service_two_name: 's2_pd_key'
License
See the LICENSE.txt file for license rights and limitations (MIT).
Metadata
Release files for charlesbot-pagerduty-escalations 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| charlesbot-pagerduty-escalations-0.2.0.tar.gz | 4.4 kB | Without provenance | Details for charlesbot-pagerduty-escalations-0.2.0.tar.gz |
Release files / charlesbot-pagerduty-escalations-0.2.0.tar.gz
| Download URL | charlesbot-pagerduty-escalations-0.2.0.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4378c6e9dd07968b57d2cabc76ac405201806a8d9c8fc93fb8c92a964f2ebc94
|
|
BLAKE2b-256 checksum How to use checksums |
709a62b4db05167704896d84431abba81049eaab1a7d75af2698fc1ca8aced4d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for charlesbot-pagerduty-escalations 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.