Closed NiasSt90 closed 4 years ago
Hi @NiasSt90 Since release 2.5.0, prom2teams returns same status code from Teams response, so Alertmanager should handle 429 by itself instead of retrying because of 500 error from prom2teams.
I am also getting the same error..
prom2teams send few alerts after that microsoft teams endpoint returns HTTP error 429..
Please let us know how to fix this...
Hi, I'm getting HTTP error 429 also. After some research it looks like we are getting HTTP error 429 due to SharePoint throttling.
Here https://docs.microsoft.com/en-us/sharepoint/dev/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online#how-to-decorate-your-http-traffic-to-avoid-throttling they are suggesting to decorate HTTP request via appropriate UserAgent string to avoid throttling.
Is there a way to get this done through configuration?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Description
Alertmanager sends some alerts and prom2teams tries to forward them to MS-Teams. But after some successfully forwarded messages to the MS-Teams service it replies with http status code 429.
the prometheus alertmanager gets back http status code 500
and tries so resend after a short timeout...this triggers the error again and again....
The major problem: the first alerts are come thru MS-Teams (can see them in the channel). But with http return code 500 to alertmanager it tries to resend all 42 alerts....we got >500 alerts message last night from 42 real alerts. Only restarting alertmanager stopped these endless loop.
the status code 429 from teams should be handled carefully (send slower...).
Versions
2.4.0