opsgenie -- failed to create incident

[adejesus-mt]

Hello All,

I have been wracking my brain for too long on this project. I am attempting to hook in OpsGenie as a handler as well as integrate alerting through OpsGenie Dashboard and mobile app. I have the following errors pop up on the sensu-server.logs regarding the creation of events:

{"timestamp":"2018-01-05T19:22:56.756654+0000","level":"info","message":"handler output","handler":{"type":"pipe","command":"/usr/local/share/gems/bin/handler-opsgenie.rb","name":"opsgenie"},"event":{"id":"2a615c3a-de55-4f03-91b0-a5aab2d0fd60"},"output":["opsgenie -- failed to create incident -- host_alias/app_scriptname\n"]}

Whats the procedure to figure out whats going on here? I have not been able to find anything online.

In addition. On the OpsGenie Dashboard how do we go about creating Alerting Fields? I was. told by support to use Dynamic Fields but i have no idea what kind of parameters we are supposed to use for sensu -> opsgenie.

Any assistance would be appreciated.

Thanks!

[jwatroba]

Just ran into this as well, it looks like it might be message size limit for the OpsGenie API. If the message is over 130 characters it fails to create the alert.
https://docs.opsgenie.com/docs/alert-api#section-create-alert

[majormoses]

Ouch that is an annoying limitation, are you using a custom template? If so I am wondering what the actual response code back was and if we can rescue and attempt applying standard template if the custom fails.

[jwatroba]

I tried to replicate this behavior on a test system by having event messages over the limit but was not able to replicate the issue. I've added some some logging to the opsgenie.rb on my production system to try to catch this when it happens next but haven't had the troublesome events occur yet. Once I get some logging on some failed attempts I'll reply back to this with what I find.

[majormoses]

Thanks, ya I don't use it myself so anything you can give to help us understand what is going on is appreciated.