Migration of opsgenie api correct url

[Cornelius Maximen]

Hi we currently reference 

  apiUrl: api.eu.opsgenie.com

to integrate application monitoring within JIRA. With the migration can you please confirm what the replacement url should be. I foound a page earlier which specificed that the url had changed to app.opsgenie.com

Can you please confirm as we need to test and approve change in UAT before going live.

[Lucas Modzelewski _Lumo_]

Based on the documentation:

• Opsgenie APIs will continue to work even while you move to Jira Service Management. However, once you complete your move, we recommend that you start using the Jira Service Management Ops REST API.

Source: https://support.atlassian.com/jira-service-management-cloud/docs/start-shifting-from-opsgenie-to-jira-service-management/#What-happens-after-starting-your-shift-from-Opsgenie 

I believe the current URL should use api.atlassian.com/jsm/ops/api/, as mentioned in the API documentation.

[Sören König]

I've came across the same question during our migration from Opsgenie to Jira Service Management and the replacement API endpoint is https://api.atlassian.com/jsm/ops/integration/


A minimal configuratio for Prometheus Alertmanager would look like:

```

global:
resolve_timeout: 5m

route:
  group_by: ['alertname']
  group_wait: 30s
  group_interval: 5m
  repeat_interval: 1h
  receiver: base-receiver
receivers:
-   name: base-receiver
    opsgenie_configs:
    - api_key: 3878fcab-c2b8-4123-b5ed-0f4b6caadc6d
       api_url: https://api.atlassian.com/jsm/ops/integration/
        message: '{{ printf "%.130s" .CommonLabels.alertname }}'
```