# What this PR does

Refactors the PagerDuty migration script to be a bit more generic + adds
a migration script to migrate from Splunk OnCall (VictorOps)

tldr;
```bash
❯ docker build -t oncall-migrator .
[+] Building 0.4s (10/10) FINISHED
❯ docker run --rm \
-e MIGRATING_FROM="pagerduty" \
-e MODE="plan" \
-e ONCALL_API_URL="http://localhost:8080" \
-e ONCALL_API_TOKEN="<ONCALL_API_TOKEN>" \
-e PAGERDUTY_API_TOKEN="<PAGERDUTY_API_TOKEN>" \
oncall-migrator
running pagerduty migration script...

❯ docker run --rm \
-e MIGRATING_FROM="splunk" \
-e MODE="plan" \
-e ONCALL_API_URL="http://localhost:8080" \
-e ONCALL_API_TOKEN="<ONCALL_API_TOKEN>" \
-e SPLUNK_API_ID="<SPLUNK_API_ID>" \
-e SPLUNK_API_KEY="<SPLUNK_API_KEY>" \
oncall-migrator
migrating from splunk oncall...
```

https://www.loom.com/share/a855062d436a4ef79f030e22528d8c71

## Checklist

- [x] Unit, integration, and e2e (if applicable) tests updated
- [x] Documentation added (or `pr:no public docs` PR label added if not
required)
- [x] Added the relevant release notes label (see labels prefixed w/
`release:`). These labels dictate how your PR will
    show up in the autogenerated release notes.

2024-05-14 13:53:59 +00:00

852 B

Raw Permalink Blame History

title

menuTitle

description

weight

keywords

canonical

aliases

Migration from other tools

Migration guide

Learn how to migrate to Grafana OnCall from other on-call tools

200

OnCall

Migration

Pagerduty

Splunk OnCall

VictorOps

on-call tools

https://grafana.com/docs/oncall/latest/set-up/migration-from-other-tools/

/docs/grafana-cloud/alerting-and-irm/oncall/set-up/migration-from-other-tools

/docs/grafana-cloud/alerting-and-irm/oncall/migration-from-other-tools

../migration-from-other-tools/

Migration from other tools

We currently support automated migration from the following on-call tools:

PagerDuty
Splunk OnCall (VictorOps)

See our OSS Migrator for more details.

852 B Raw Permalink Blame History

Migration from other tools

852 B

Raw Permalink Blame History