Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can we limit retries to the webhook output? #2203

Closed
domwhewell-sage opened this issue Jan 23, 2025 · 0 comments
Closed

Can we limit retries to the webhook output? #2203

domwhewell-sage opened this issue Jan 23, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@domwhewell-sage
Copy link
Contributor

domwhewell-sage commented Jan 23, 2025

Describe the bug
When a timeout occurs on the teams webhook it keeps retrying indefinitely preventing the scan from completing

 - teams.handle_event(VULNERABILITY(<redacted>) running for 4 hours, 28 minutes, 17 seconds:
[98460.862176] cloud-init[1376]: [VERB] HTTP timeout to URL: https://prod-105.westus.logic.azure.com:443/<redacted>
[98460.862218] cloud-init[1376]: [VERB] output.teams: Error sending VULNERABILITY(<redacted>): status code 0, response: , retrying in 1 seconds
[98462.463847] cloud-init[1376]: [VERB] HTTP timeout to URL: https://prod-105.westus.logic.azure.com:443/<redacted>
[98462.463906] cloud-init[1376]: [VERB] output.teams: Error sending VULNERABILITY(<redacted>): status code 0, response: , retrying in 1 seconds

In the case where throttling happens retry_after is not obtained from the "Retry-After" header

Expected behavior
Maybe the output module can have a configurable number of retries before it gives up so as not to hold up the scan?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant