Queue processor could not get initial token and will terminate.

[opsgenie]

Queue processor could not get initial token and will terminate.

[GamerGun]

Thank you guys.
We managed to set-up the connection with the endpoint, but now have the following issue
FATAL[2021-02-18T09:32:53.57704062Z] Token could not be received from Opsgenie, status: 403 Forbidden, message: {"message":"UnauthorizedClientException: API Key should belong to an owner to perform this action.","took":0.0,"requestId":"xxx"}
We followed this instruction: https://docs.opsgenie.com/docs/opsgenie-edge-connector-oec-action-channel
Also tried a API key from Opsgenie’s OEC Integration page as stated in https://docs.opsgenie.com/docs/oec-configuration but that didn't work either (same error).

[GamerGun]

Anyone?

[cemkucuk]

Hi @GamerGun! Unfortunately, we don't not provide any support for custom implementations but it may because of your outbound rules. It seems you can not reach out that endpoint.

[metehanozturk]

Could you please be sure you provide correct apiKey and baseUrl? Also you should guarantee that your client is able to reach the endpoint as @cemkucuk said. The endpoint returns the security token which is an internal logic and if the apiKey is correctly provided, no need to worry about the token.

[cemkucuk]

@GamerGun, it should work with given api key after creation of OEC Action Channel. Please use that one because irrelevant api keys of your account can not work with OEC client.

[metehanozturk]

Hi @GamerGun, I hope you solved API Key issue. API Keys that belong to Opsgenie Actions or Integrations would work with OEC. Also, please be sure your configuration file is updated correctly.

You can find open bugs and suggestions for OEC on our public issue tracker. If you are experiencing an issue with OEC, or if you want to raise a new bug or suggestion you can reach out Opsgenie support.