-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Logging: Log attempts from Beats to re-establish connections #5175
Labels
Comments
Hi @ppf2 seems like it's a low hanging fruit issue, can I take it? 😄 |
@liketic Of course, all contributions are welcome. |
tsg
added
the
good first issue
Indicates a good issue for first-time contributors
label
Oct 12, 2017
Hi, I'm currently looking at beats source code and getting familiar with it. I'm interested to give this a try. |
Merged
This was referenced Aug 29, 2018
leweafan
pushed a commit
to leweafan/beats
that referenced
this issue
Apr 28, 2023
Cherry-pick of PR elastic#6404 to 6.4 branch. Original message: Closes elastic#5175 Logs an info line "Attempting to reconnect" at every reconnect attempt.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Currently, at the default logging level, we are not logging entries on when Logstash attempts to re-establish connections (eg. due to DNS for downstream servers not available). For example, after these messages when the DNS issue is resolved:
Having this information logger at the default level can help with troubleshooting.
The text was updated successfully, but these errors were encountered: