kwatch icon indicating copy to clipboard operation
kwatch copied to clipboard

MS Teams Bad request issue

Open akoken opened this issue 3 years ago • 5 comments

Describe the bug Although I set MS Teams channel webhook address in config.yaml file, I didn't get any notifications.

Expected behavior Should get kwatch notification to my MS Teams channel.

Actual behavior When I checked the pod logs, it gives the following error:

time="2022-02-23T13:23:01Z" level=error msg="failed to send msg with Microsoft Teams: call to teams alert returned status code 400: Bad payload received by generic incoming webhook."

Version/Commit 0.4.0

akoken avatar Feb 23 '22 13:02 akoken

I'm facing the same error using the 0.4.0 I've tested the webhook with a simple curl and works nice. Any thoughts?

ibannieto avatar Feb 28 '22 13:02 ibannieto

I think corporate proxy causes this issue. I rebuilt the docker image by setting proxy and it worked. Guess what? Now Kubernetes API requests are failing with TLS handshake error. Notification-only proxy configuration would most likely work.

akoken avatar Mar 16 '22 13:03 akoken

Thank you so much @akoken , my webhook is now working properly :-)

ibannieto avatar Mar 17 '22 12:03 ibannieto

I'm glad that it worked for you @ibannieto :)

akoken avatar Mar 17 '22 16:03 akoken

I think corporate proxy causes this issue. I rebuilt the docker image by setting proxy and it worked. Guess what? Now Kubernetes API requests are failing with TLS handshake error. Notification-only proxy configuration would most likely work.

Hi, @akoken

I'm facing the same issue. kwatch don't work with proxy

TLS handshake error with enterprise proxy or i/o timeout when I removed it

BK-STAR77 avatar Apr 07 '22 13:04 BK-STAR77