You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the CEL program returns a state.status_code that is non HTTP 200 then the input will repeat the request rapidly. This occurs for status codes that are outside the range that are handled by go-retryablehttp like [201, 499] except 429. If I omit the status_code then it basically works as expected by making a request, reporting the error, and then waiting for the next interval. So perhaps when a non-200 status_code is reported then the auto-generated error.message could include information about the status code and it would wait for the next interval?
In 6.231 sec the input made 10893 requests. That's ~1700 request per second. 😨
When the CEL program returns a
state.status_code
that is non HTTP 200 then the input will repeat the request rapidly. This occurs for status codes that are outside the range that are handled by go-retryablehttp like [201, 499] except 429. If I omit thestatus_code
then it basically works as expected by making a request, reporting the error, and then waiting for the next interval. So perhaps when a non-200status_code
is reported then the auto-generatederror.message
could include information about the status code and it would wait for the next interval?In 6.231 sec the input made 10893 requests. That's ~1700 request per second. 😨
Version: filebeat version 8.7.0 (arm64), libbeat 8.7.0 [f08eed8 built 2022-12-08 15:32:00 +0000 UTC]
Reproduction
The text was updated successfully, but these errors were encountered: