-
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
[8.16](backport #41960) Add upstream deadlock warning to the logstash output #42110
base: 8.16
Are you sure you want to change the base?
Conversation
Add an internal timeout in the Logstash output so that it logs an error when published events stop making progress for an extended time, which can indicate that the Logstash host is silently deadlocked. (cherry picked from commit 0e62bf8) # Conflicts: # libbeat/outputs/logstash/async.go
Cherry-pick of 0e62bf8 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
This pull request doesn't have a |
This pull request has not been merged yet. Could you please review and merge it @faec? 🙏 |
1 similar comment
This pull request has not been merged yet. Could you please review and merge it @faec? 🙏 |
This pull request has not been merged yet. Could you please review and merge it @faec? 🙏 |
Add an internal timeout in the Logstash output so that it logs an error when published events stop making progress for an extended time, which can indicate that the Logstash host is silently deadlocked.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related Issues
This is an automatic backport of pull request #41960 done by [Mergify](https://mergify.com).