Check_mk still uses v1 default api for the opsgenie integration

Troubleshooting
,
1

2.1.0p29
Ubuntu 18

No error message, but instead of using the v2 api, checkmk uses the old v1 default api if you
try to configure it like in the check_mk docs described.

Also described here:
https://forum.checkmk.com/t/check-mk-uses-default-api-for-opsgenie/25007

It works if you use this workaround:
https://support.atlassian.com/opsgenie/docs/integrate-opsgenie-with-checkmk/

But there it only sets the priority to 3 (crit,warn) and you cant change it so you have to filter afterwards and change the priority in opsgenie.

2

Hello Marcel!
Thank you for bringing this to our attention. We opened a case internally to look into it.

3

Hi Sara,

It’s great that checkmk is addressing this long known issue.

As diligent Opsgenie users, we have been waiting for a while for an improvement of the Opsgenie notification function so that our customers do not have to rely on self-implemented workarounds.

Your market companion from Nuremberg is already a bit further ahead and also supports reporting of acknowledgements in Opsgenie back to there monitoring system.

I am in any case curious about your solution :slight_smile:

2 Likes
4

@Sara some news about this?

5

Nothing yet. Me or my colleagues will let you know when there are any changes.

6

Hi Sara, is there anything new regarding this issue?

I also saw this.

7

Hi Marcel,

it was an advice of the Opsgenie team that the Checkmk notification script should use the Default API instead of the integration. The integration within Opsgenie is not provided by us, it was an old implementation and was deprecated by Opsgenie.