This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 80
Validating WebHook-Response #49
Comments
mathewlsm
added a commit
to mathewlsm/alerting
that referenced
this issue
May 8, 2019
Reststatus.Created for WebHook-Response is also acceptable (opendistro-for-elasticsearch#49).
mathewlsm
added a commit
to mathewlsm/alerting
that referenced
this issue
May 8, 2019
Improvement for Issue opendistro-for-elasticsearch#49
mathewlsm
added a commit
to mathewlsm/alerting
that referenced
this issue
May 8, 2019
…arch#49 Reststatus.Created for WebHook-Response is also acceptable
This was referenced May 8, 2019
mathewlsm
pushed a commit
to mathewlsm/alerting
that referenced
this issue
May 9, 2019
using all 2XX response status as valid response
I'm still getting an error when a webhook destination returns a 202:
|
Hello Andrew, the improvement is not merged back to version 0.9.0.0. It's avaiable in following versions: v1.2.0.1 v1.2.0.0 v1.1.0.1 v1.1.0.0 v1.0.0.0; which means 1.0.0.0 and above. Kind regards Mathew
|
When creating alert destination getting return code 201 POST /_opendistro/_alerting/destinations/ {
"name": "test-destination-1",
"type": "slack",
"slack": {
"url": "http://www.example.com"
}
} |
Same goes for alert monitor creation, getting code 201 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
we created an alerting with an action calling a webhook. The webhook calls a restservice which creates a ticket for the responsible person. Our Ticketsystem return a 201 if the ticket was created successfull.
The Problem is that the DestinationHTTPClient just accept a 200 HTTP-Status as valid.
alerting/notification/src/main/java/com/amazon/opendistroforelasticsearch/alerting/destination/client/DestinationHttpClient.java
Line 156 in 488d63d
The HttpClient should also accept a 201 return code.
The text was updated successfully, but these errors were encountered: