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.

Sign up for GitHub

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

Jump to bottom

Don't rely on a time period for determining that Logstash TCP plugin is ready #1

Open
rcoundon opened this issue Aug 21, 2018 · 2 comments
Open

Don't rely on a time period for determining that Logstash TCP plugin is ready #1

rcoundon opened this issue Aug 21, 2018 · 2 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@rcoundon
Copy link
Owner

No description provided.

@rcoundon rcoundon added enhancement New feature or request help wanted Extra attention is needed labels Aug 21, 2018
@bikov
Copy link
Contributor

bikov commented Mar 16, 2020

why you setting this timeout (60 sec)? why not processLogQueue right away?

@rcoundon
Copy link
Owner Author

I think, at the time, I couldn't find a way to know that the logstash plugin was ready so introduced a wait period to be safe. This issue was opened to see if I (or someone else) could find a way to do this more robustly. Any ideas?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rcoundon @bikov