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

Refactor any custom backoff strategy to use common.Backoff #10178

Closed
ph opened this issue Jan 18, 2019 · 2 comments
Closed

Refactor any custom backoff strategy to use common.Backoff #10178

ph opened this issue Jan 18, 2019 · 2 comments
Labels
bug libbeat Stalled Team:Integrations Label for the Integrations team

Comments

@ph
Copy link
Contributor

ph commented Jan 18, 2019

The current monitoring code implements his own retry or backoff strategy, it should be refactored to use the common.Backoff struct so it benefits from jitter and any other improvements that can come.

We will need to audit the code to detect any other custom implementation.

@ph
Copy link
Contributor Author

ph commented Jan 18, 2019

Adding #10172 to keep a trace to the original problematic.

@andresrc andresrc added Team:Integrations Label for the Integrations team and removed Team:Beats labels Mar 6, 2020
@botelastic
Copy link

botelastic bot commented Feb 4, 2021

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.

@botelastic botelastic bot added the Stalled label Feb 4, 2021
@botelastic botelastic bot closed this as completed Mar 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug libbeat Stalled Team:Integrations Label for the Integrations team
Projects
None yet
Development

No branches or pull requests

3 participants