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

Filebeat Httpjson input needs to handle Rate-limit error gracefully #17734

Closed
alakahakai opened this issue Apr 15, 2020 · 2 comments
Closed

Filebeat Httpjson input needs to handle Rate-limit error gracefully #17734

alakahakai opened this issue Apr 15, 2020 · 2 comments
Assignees
Labels
Filebeat Filebeat

Comments

@alakahakai
Copy link

Filebeat Httpjson input needs to handle Rate-limit error (Http Error code 429) gracefully when the proposed time delay by Okta ends up not sufficient.

@alakahakai alakahakai self-assigned this Apr 15, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/siem (Team:SIEM)

@andrewkroh
Copy link
Member

So it seems like with the org wide rate limit, that the rate limit headers are not fully reliable since all applications are sharing from the same token bucket. So even if Filebeat honors the X-Rate-Limit-Reset, other concurrently running applications might have already used up the available requests. So Filebeat will have to keep trying.

Additionally, the X-Rate-Limit-Reset time for concurrent rate limits is only a suggestion. There's no guarantee that enough requests will complete to stop exceeding the concurrent rate limit at the time indicated.

Source: https://developer.okta.com/docs/reference/rate-limits/#check-your-rate-limits-with-okta-s-rate-limit-headers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Filebeat Filebeat
Projects
None yet
Development

No branches or pull requests

4 participants