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][websocket] - Add retry mechanism to socket connections #40271

Closed
ShourieG opened this issue Jul 17, 2024 · 1 comment · Fixed by #40601
Closed

[filebeat][websocket] - Add retry mechanism to socket connections #40271

ShourieG opened this issue Jul 17, 2024 · 1 comment · Fixed by #40601
Assignees
Labels
enhancement Filebeat Filebeat Team:Security-Service Integrations Security Service Integrations Team

Comments

@ShourieG
Copy link
Contributor

Describe the enhancement: Add a retry mechanism to socket connections.

Describe a specific use case for the enhancement or feature: Initially a retry mechanism did exist but it was removed during the review process after discussions that it might not be required for websockets due to it's inherent nature to be able to resume connection state after disconnects, unlike a normal http connection. But with recent findings that some scenarios demand retries to exist, we need to add this back in.

Related issues : elastic/elastic-package#1977, elastic/integrations#9926,
elastic/integrations#10472.

@ShourieG ShourieG self-assigned this Jul 17, 2024
@ShourieG ShourieG added the Team:Security-Service Integrations Security Service Integrations Team label Jul 17, 2024
@elasticmachine
Copy link
Collaborator

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Filebeat Filebeat Team:Security-Service Integrations Security Service Integrations Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants