Ad Widget

**max.ch.88** · 04-09-2020, 17:16

If I understand you correctly, you are trying to open a web page https://api.opsgenie.com/v2/alerts/r...a-5aaaaaaa3326. Why? You get the error message because don't use authorization.
Are you having problems using the Opsgenie webhook?
If you are writing your own webhook, you could look at the Opsgenie webhook JS code as an example.

**Spectroman** · 04-09-2020, 19:38

Hi Max,

This is happening using the official OpsGenie Webhook gathered from: https://www.zabbix.com/integrations/opsgenie

I was also surprise that, this code , after sending the alert, he tries to fetch more information from the Alert in order to provide more information on the event on OpsGenie side (see screenshot below). Here he initiate the second GET cal after receiving a 202 upon creation of the working opsGenie alert:

Code:

if (resp.status === 202) {
resp = Media.getAlertId(resp.response.requestId);
if (params.event_source == 0 && params.event_value == 1 && params.event_update_status == 0) {
result.tags.__zbx_ops_issuekey = resp.response.data.alertId;
result.tags.__zbx_ops_issuelink = Media.params.web + 'alert/detail/' + resp.response.data.alertId;
}
}

And thereafter, it is not "me" who is trying to open the webpage, this call is going out from the Webhook, here:

Code:

getAlertId: function (requestId) {
do {
resp = Media.request('get', 'requests/' + requestId, undefined, true);
}
while (typeof resp.response !== 'object' || typeof resp.response.data === 'undefined'
|| resp.response.data.success === false);

if (typeof resp.response !== 'object' || typeof resp.response.data === 'undefined') {
throw 'Cannot get ' + Media.name + ' issue ID. Check debug log for more information.';
}

return resp;
}

This Code is executed right after he received the basic information of the Alert creation with the RequestID ( first call is a working POST ).

And obviously, in every call made by the WebHook he will add the Auth header with the token here:

Code:

var response,
url = Media.params.api + query,
request = new CurlHttpRequest();

request.AddHeader('Content-Type: application/json');
request.AddHeader('Authorization: ' + Media.params.token);


if (typeof data !== 'undefined') {
data = JSON.stringify(data);
}

It is also important to point out that "missing auth header" will give a 401 -- wrong body on the GET will give a 403 and throttle problems will give a 429.

I am trying to make the WebHook work as is in a Zabbix 4.4.5, and apparently, doesn't matter if I add more headers (to match with the curl or postman headers) , this won't work. I can't explain why.

I then tried to copy the exact same MediaType to a zabbix 5.2, and it worked like a charm.

But on the 4.4.5, because this second call fails, he keeps repeating the alert, as if it hadn't created on OpsGenie side ( again, he did and I got the requestID)... and after 3 tries (default) he gives up with the error 400:

After testing on the Version 5.2 I see he creates this, after successfully doing all the steps:

So yeah... I cannot explain this behavior, I really tried a zillion things , for me it seems the only solution is to remove the code that makes the second GET-Alert call and do without the tags with the link to the Alert on opsg...

Or if someone has any ideas...

**Spectroman** · 04-09-2020, 19:53

It is worth mention that the second call will create this veeeery handy and brilliant menu:

It would be a pity to break that functionality.

**max.ch.88** · 09-09-2020, 12:05

I would suggest upgrading to 5.0 and using out-of-the-box webhooks.
But if it's impossible and you very very very want to have the Opsgenie webhook in your 4.4, then take that https://git.zabbix.com/projects/ZBX/...a_opsgenie.xml, change 5.0 to 4.4 on line 3 and remove lines 165, 418-476.

Ad Widget

Error 400 on OpsGenie Webhook while getting details of Alert

Error 400 on OpsGenie Webhook while getting details of Alert

Comment

Comment

Comment

Comment