centralcloud/oncall-engine
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update README.md

Browse source
This commit is contained in:
Vadim Stepanov 2022-09-07 11:05:46 +01:00 • committed by GitHub
parent b68dd9bc92
commit e63374db19
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
tools/pagerduty-migrator/README.md
View file

@ -20,7 +20,7 @@ Resources that can be migrated using this tool:
1. Make sure you have `docker` installed
2. Build the docker image: `docker build -t pd-oncall-migrator .`
3. Obtain a PagerDuty API token: https://support.pagerduty.com/docs/api-access-keys
3. Obtain a PagerDuty API user token: https://support.pagerduty.com/docs/api-access-keys#generate-a-user-token-rest-api-key
4. Obtain a Grafana OnCall API token and API URL on the "Settings" page of your Grafana OnCall instance
## Migration plan
@ -84,4 +84,4 @@ It's possible to specify a default contact method type for user notification rul
* Connect integrations (press the "How to connect" button on the integration page)
* Make sure users connect their phone numbers, Slack accounts, etc. in their user settings
* At some point you would probably want to recreate schedules using Google Calendar or Terraform to be able to modify migrated on-call schedules in Grafana OnCall