-
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
Provided Grok expressions do not match field value #23793
Comments
Pinging @elastic/integrations (Team:Integrations) |
Still getting |
I did some testing and I can see it's tripping up on the last
|
Okay, I've solved the problem with a little bit more digging. It seems nginx ingress_controller is another kind of format and it seems to default to being enabled if you enable the nginx module and don't explicitly disable it. I noticed I had duplicate log messages - nginx.access which parsed nicely and a duplicate nginx.ingress_controller which was erroring. I would say this is a false alarm, because ingress_controller should be disabled in filebeat module configuration if one doesn't have these logs. |
Any idea how to disable nginx ingress_controller when using the Filebeat docker image? Edit:
|
Hi! We're labeling this issue as |
not stale |
Hi! We're labeling this issue as |
For confirmed bugs, please report:
Using filebeat with
nginx
module.Resulting document:
The text was updated successfully, but these errors were encountered: