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

Edit docs for PagerDuty migrator scripts (#662)

Browse source 
* add docs on add_users_pagerduty_to_grafana.py

* spelling
This commit is contained in:
Vadim Stepanov 2022-10-19 12:33:59 +01:00 • committed by GitHub
parent e67d3519fe
commit 427c6c95c5
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 11 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -37,7 +37,8 @@ pd-oncall-migrator
Please read the generated report carefully since depending on the content of the report, some PagerDuty resources could not be migrated and some existing Grafana OnCall resources could be deleted.
Note that users are matched by email, so if there are users in the report with "no Grafana OnCall user found with this email" error, it's possible to fix it by adding these users to your Grafana organization.
Note that users are matched by email, so if there are users in the report with "no Grafana OnCall user found with this email" error, it's possible to fix it by adding these users to your Grafana organization.
If there is a large number of unmatched users, please also [see the script](scripts/README.md) that can automatically create missing Grafana users via Grafana HTTP API.
### Example migration plan

14
tools/pagerduty-migrator/scripts/README.md
View file

@ -1,12 +1,16 @@
# PagerDuty migrator scripts
When we run MODE="plan" we can notice that there is escalation, integration in pagerduty that needs to be linked to a user.
When running the migrator in `plan` mode, it can potentially show that some users cannot be matched (meaning that there are no users in Grafana with the same email as in PagerDuty).
To solve this problem, we can run the add_users_pagerduty_to_grafana.py script
If there is a large number of unmatched users, it can be easier to use the following script that automatically creates missing Grafana users:
```bash
docker run -it --rm -e PAGERDUTY_API_TOKEN="mytoken" -e GRAFANA_URL="http://localhost:3000" -e GRAFANA_USERNAME="admin" -e GRAFANA_PASSWORD="admin" pd-oncall-migrator python /app/scripts/add_users_pagerduty_to_grafana.py
docker run --rm \
-e PAGERDUTY_API_TOKEN="<PAGERDUTY_API_TOKEN>" \
-e GRAFANA_URL="http://localhost:3000" \
-e GRAFANA_USERNAME="admin" \
-e GRAFANA_PASSWORD="admin" \
pd-oncall-migrator python /app/scripts/add_users_pagerduty_to_grafana.py
```
It is worth remembering that this script will create a user with a random password.
To access with the user created, it will be necessary to change the password in grafana web.
The script will create users with random passwords, so they will need to reset their passwords later in Grafana.