-
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/module/nginx/ingress_controller: Add unix socket log parsing #34732
Conversation
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for contribution!
@gsantoro could you please review as well? do you think it is smth that we should backport to https://github.com/elastic/integrations/tree/main/packages/nginx_ingress_controller? |
Co-authored-by: Tetiana Kravchenko <tanya.kravchenko.v@gmail.com>
This pull request is now in conflicts. Could you fix it? 🙏
|
…#34732) * Add unix socket log parsing for nginx ingress_controller * Update CHANGELOG.next.asciidoc - added pull request id Co-authored-by: Tetiana Kravchenko <tanya.kravchenko.v@gmail.com> --------- Co-authored-by: Tetiana Kravchenko <tanya.kravchenko.v@gmail.com>
What does this PR do?
Adds unix socket log parsing for nginx ingress_controller
Why is it important?
Nginx ingress_controller pipeline can not parse kubernetes nginx ingress controller logs if unix socket used.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs