From e63374db1907917c45488901a360f606f657596a Mon Sep 17 00:00:00 2001 From: Vadim Stepanov Date: Wed, 7 Sep 2022 11:05:46 +0100 Subject: [PATCH] Update README.md --- tools/pagerduty-migrator/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/pagerduty-migrator/README.md b/tools/pagerduty-migrator/README.md index a59c39b5..b83f550d 100644 --- a/tools/pagerduty-migrator/README.md +++ b/tools/pagerduty-migrator/README.md @@ -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 - \ No newline at end of file +