-
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
filebeat: improve debug logging in udp/tcp inputs #34060
Comments
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
Hi! We're labeling this issue as |
Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices) |
This seems like a pretty old ticket.
What else is missing? @efd6 |
Something like this then:
|
Yeah, I think that's good. |
While working on a customer issue in filebeat relating to the udp input I noticed that this input does very little debug logging. Examples of this are that not all transitions are logged during execution and details of the address/port are not logged making it difficult to differentiate what is logged when more than one port or address is being listened on.
It would be good to improve this situation and it may be worth looking over the other inputs to check how well useful information is being logged in them as well.
The text was updated successfully, but these errors were encountered: