Hi,

We expose ObserviumV2 and deprecated the old one.

Regards, Cagla

On 9 Dec 2016, at 16:22, Adam Armstrong adama@memetic.org wrote:

Hi,

This is changed on our side, but this does mean that at the moment the API doesnt' work at all, as you're not exposing the v2 API at your side, only the old one.

adam.

...

On 09/12/2016 12:57:15, Çağla Arıkan cagla@opsgenie.com wrote:

Hi Adam,

We talked about OpsGenie Observium Integration before. As you stated we developed a new integration that does not use generic webhook. By using the payload you sent to runscope we developed ObserviumV2. You can inform your clients that they can reach from "https://app.opsgenie.com/integration#/add/ObserviumV2 https://app.opsgenie.com/integration#/add/ObserviumV2" address. The integration is live now. You should fix the endpoint that you send the payload as https://api.opsgenie.com/v1/json/observiumv2 https://api.opsgenie.com/v1/json/observiumv2. When you fix that we will deprecate the old one.

Regards, Cagla ARIKAN

---

observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

Hi Cagla,

Yeah, I think this should be possible by allowing the user to configure the instance.

adam. On 2018-02-19 13:03:45, Çağla Arıkan cagla@opsgenie.com wrote: Hi,

I work as a software engineer at OpsGenie. Observium has a native integration with OpsGenie, and we have a request for you about configuration of this integration.

We are introducing EU OpsGenie. When the customers start using EU OpsGenie, they will not be able to use the integration. When an OpsGenie integration is being configured, Observium sends an HTTP request to https://api.opsgenie.com/v1/json/observiumv2?apiKey=$apikey [https://api.opsgenie.com/v1/json/observiumv2?apiKey=$apikey], but our OpsGenie EU instance will use another endpoint which is https://api.euopsgenie.com/v1/json/observiumv2 [https://api.opsgenie.com/v1/json/monitis?apiKey=$apikey%5D?apiKey=$apikey [https://api.euopsgenie.com/v1/json/observiumv2?apiKey=$apikey]. And we're thinking of adding more instances like this. Thus, can you change the OpsGenie integration configuration in a way to let the endpoints to be configurable by users?

Best Regards, Çağla from OpsGenie

On 9 Dec 2016, at 16:22, Adam Armstrong <adama@memetic.org [mailto:adama@memetic.org]> wrote:

Hi,

This is changed on our side, but this does mean that at the moment the API doesnt' work at all, as you're not exposing the v2 API at your side, only the old one.

adam. On 09/12/2016 12:57:15, Çağla Arıkan <cagla@opsgenie.com [mailto:cagla@opsgenie.com]> wrote: Hi Adam,

We talked about OpsGenie Observium Integration before. As you stated we developed a new integration that does not use generic webhook. By using the payload you sent to runscope we developed ObserviumV2. You can inform your clients that they can reach from "https://app.opsgenie.com/integration#/add/ObserviumV2 [https://app.opsgenie.com/integration#/add/ObserviumV2]" address. The integration is live now. You should fix the endpoint that you send the payload as https://api.opsgenie.com/v1/json/observiumv2 [https://api.opsgenie.com/v1/json/observiumv2]. When you fix that we will deprecate the old one.

Regards, Cagla ARIKAN _______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium