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

Beats common backoff behavior #6791

Closed
urso opened this issue Apr 6, 2018 · 3 comments
Closed

Beats common backoff behavior #6791

urso opened this issue Apr 6, 2018 · 3 comments
Labels

Comments

@urso
Copy link

urso commented Apr 6, 2018

The different outputs have different backoff settings and behaviour on error and when to backoff. The redis output does not even support exponential backoff.

Update all outputs, in order to have similar backoff behaviour.

@urso
Copy link
Author

urso commented Jul 27, 2018

#7781 adds backoff support to the redis output.

@ppf2
Copy link
Member

ppf2 commented Aug 17, 2018

While this is not an "output" per say, the Beats monitoring connection to Elasticsearch (#7966) can use an exponential backoff policy as well.

@urso
Copy link
Author

urso commented Aug 15, 2019

Closing. There has been some improvements thanks to @ph.

@urso urso closed this as completed Aug 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants