You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`MIGRATING_FROM`| Set to `opsgenie`| String | N/A |
615
-
|`OPSGENIE_API_KEY`|OpsGenie API key. To create a key, refer to [OpsGenie docs](https://docs.opsgenie.com/docs/api-key-management). | String | N/A |
616
-
|`OPSGENIE_API_URL`|OpsGenie API URL. Use `https://api.eu.opsgenie.com/v2` for EU instances. | String |`https://api.opsgenie.com/v2`|
615
+
|`OPSGENIE_API_KEY`|Opsgenie API key. To create a key, refer to [Opsgenie docs](https://docs.opsgenie.com/docs/api-key-management). | String | N/A |
616
+
|`OPSGENIE_API_URL`|Opsgenie API URL. Use `https://api.eu.opsgenie.com/v2` for EU instances. | String |`https://api.opsgenie.com/v2`|
617
617
|`ONCALL_API_URL`| Grafana OnCall API URL. This can be found on the "Settings" page of your Grafana OnCall instance. | String | N/A |
618
618
|`ONCALL_API_TOKEN`| Grafana OnCall API Token. To create a token, navigate to the "Settings" page of your Grafana OnCall instance. | String | N/A |
619
619
|`MODE`| Migration mode (plan vs actual migration). | String (choices: `plan`, `migrate`) |`plan`|
620
620
|`UNSUPPORTED_INTEGRATION_TO_WEBHOOKS`| When set to `true`, integrations with unsupported type will be migrated to Grafana OnCall integrations with type "webhook". When set to `false`, integrations with unsupported type won't be migrated. | Boolean |`false`|
621
621
|`MIGRATE_USERS`| If `false`, will allow you to import all objects while ignoring user references in schedules and escalation policies. In addition, if `false`, will also skip importing User notification rules. | Boolean |`true`|
622
622
|`OPSGENIE_FILTER_TEAM`| Filter resources by team name. Only resources associated with this team will be migrated. | String | N/A |
623
-
|`OPSGENIE_FILTER_USERS`| Filter resources by OpsGenie user IDs (comma-separated). Only resources associated with these users will be migrated. | String | N/A |
623
+
|`OPSGENIE_FILTER_USERS`| Filter resources by Opsgenie user IDs (comma-separated). Only resources associated with these users will be migrated. | String | N/A |
624
624
|`OPSGENIE_FILTER_SCHEDULE_REGEX`| Filter schedules by name using a regex pattern. Only schedules whose names match this pattern will be migrated. | String | N/A |
625
625
|`OPSGENIE_FILTER_ESCALATION_POLICY_REGEX`| Filter escalation policies by name using a regex pattern. Only policies whose names match this pattern will be migrated. | String | N/A |
626
626
|`OPSGENIE_FILTER_INTEGRATION_REGEX`| Filter integrations by name using a regex pattern. Only integrations whose names match this pattern will be migrated. | String | N/A |
@@ -630,41 +630,41 @@ Configuration is done via environment variables passed to the docker container.
630
630
631
631
#### User notification rules
632
632
633
-
The tool is capable of migrating user notification rules from OpsGenie to Grafana OnCall.
634
-
Notification rules from OpsGenie will be migrated to both default and important notification rules in Grafana OnCall
633
+
The tool is capable of migrating user notification rules from Opsgenie to Grafana OnCall.
634
+
Notification rules from Opsgenie will be migrated to both default and important notification rules in Grafana OnCall
635
635
for each user. Note that delays between notification rules may be slightly different in Grafana OnCall.
636
636
637
637
By default (when `PRESERVE_EXISTING_USER_NOTIFICATION_RULES` is `true`), existing notification rules in Grafana OnCall will
638
-
be preserved and OpsGenie rules won't be imported for users who already have notification rules configured in Grafana OnCall.
638
+
be preserved and Opsgenie rules won't be imported for users who already have notification rules configured in Grafana OnCall.
639
639
640
-
If you want to replace existing notification rules with ones from OpsGenie, set `PRESERVE_EXISTING_USER_NOTIFICATION_RULES`
640
+
If you want to replace existing notification rules with ones from Opsgenie, set `PRESERVE_EXISTING_USER_NOTIFICATION_RULES`
641
641
to `false`.
642
642
643
643
See [Migrating Users](#migrating-users) for some more information on how users are migrated.
644
644
645
645
#### On-call schedules
646
646
647
-
The tool is capable of migrating on-call schedules from OpsGenie to Grafana OnCall.
647
+
The tool is capable of migrating on-call schedules from Opsgenie to Grafana OnCall.
648
648
Schedules are migrated with their rotations. The following features are supported:
649
649
650
650
- Daily, weekly, and hourly rotations
651
651
- Multiple rotations per schedule
652
652
- Schedule overrides
653
653
654
-
On-call schedules will be migrated to new Grafana OnCall schedules with the same name as in OpsGenie.
654
+
On-call schedules will be migrated to new Grafana OnCall schedules with the same name as in Opsgenie.
655
655
Any existing schedules with the same name will be deleted before migration.
656
-
Any on-call schedules that reference unmatched users won't be migrated. Any OpsGenie schedule which
656
+
Any on-call schedules that reference unmatched users won't be migrated. Any Opsgenie schedule which
657
657
uses time restrictions will not be migrated as migrating these is not supported.
658
658
659
659
#### Escalation policies
660
660
661
-
The tool is capable of migrating escalation policies from OpsGenie to Grafana OnCall.
661
+
The tool is capable of migrating escalation policies from Opsgenie to Grafana OnCall.
662
662
Every escalation policy will be migrated to a new Grafana OnCall escalation chain with name convention of
663
663
`{team name} - {escalation policy name}`.
664
664
665
665
Caveats:
666
666
667
-
- Only the "Notify user" and "Notify on-call user(s) in schedule" rule types are supported. If an OpsGenie Escalation
667
+
- Only the "Notify user" and "Notify on-call user(s) in schedule" rule types are supported. If an Opsgenie Escalation
668
668
Policy references a rule other than these, those rule steps are simply ignored in the migration
669
669
- Any existing escalation chains with the same name will be deleted, in Grafana OnCall, before migration.
670
670
Note that delays between escalation steps may be slightly different in Grafana OnCall
@@ -673,8 +673,8 @@ be done manually
673
673
674
674
#### Integrations
675
675
676
-
The tool is capable of migrating integrations from OpsGenie to Grafana OnCall.
677
-
For every integration in OpsGenie, the tool will migrate it to a Grafana OnCall integration.
676
+
The tool is capable of migrating integrations from Opsgenie to Grafana OnCall.
677
+
For every integration in Opsgenie, the tool will migrate it to a Grafana OnCall integration.
678
678
679
679
Any integrations with unsupported type won't be migrated unless `UNSUPPORTED_INTEGRATION_TO_WEBHOOKS` is set to `true`.
680
680
@@ -701,7 +701,7 @@ The following integration types are supported:
701
701
702
702
- Connect integrations (press the "How to connect" button on the integration page)
703
703
- Make sure users connect their phone numbers, Slack accounts, etc. in their user settings
704
-
- Review and adjust any webhook integrations that were migrated from unsupported OpsGenie integration types
704
+
- Review and adjust any webhook integrations that were migrated from unsupported Opsgenie integration types
0 commit comments