In the most recent version of mattermost + Graylog 3 I am not able to send notification, not even test. I have pinned down the problem down to getting 404 on my Nginx reverse proxy pointing to mattermost server. I need to mention that I have other incoming webhooks working just fine.
In the current version of mattermost, webhook can be defined with predetermined and locked channel, and I have wintessed similar behaviour of getting 404's when having channel name defined. Simple option to omit channel name in POST request would suffice I think.
83.12.190.58 - - [13/May/2019:18:42:10 +0200] "POST /hooks/HOOK_ID HTTP/1.1" 404 163 "-" "Java/1.8.0_212"
83.12.190.58 - - [13/May/2019:18:43:39 +0200] "POST /hooks/HOOK_ID HTTP/1.1" 404 163 "-" "Java/1.8.0_212"
83.12.190.58 - - [13/May/2019:18:49:45 +0200] "POST /hooks/HOOK_ID HTTP/1.1" 404 163 "-" "Java/1.8.0_212"
In the most recent version of mattermost + Graylog 3 I am not able to send notification, not even test. I have pinned down the problem down to getting 404 on my Nginx reverse proxy pointing to mattermost server. I need to mention that I have other incoming webhooks working just fine.
In the current version of mattermost, webhook can be defined with predetermined and locked channel, and I have wintessed similar behaviour of getting 404's when having channel name defined. Simple option to omit channel name in POST request would suffice I think.