-
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
After upgraded to 7.6 filebeat doesn’t work as expected with config from 7.5.x #16464
Comments
You have changed default k8s fields and it isn't on docs. Example: become: So, my processor condition would never matched. Is it by design or a bug/typo? |
This is a regression and we need to fix it, sorry for the inconvenience |
@ChrsMark could you please have a look to this one? |
I think that problems occur because of this:
Maybe we need something similar to
What we need is to cure metadata accordingly so as to bring the labels in first level like this: dba8f74#diff-15420f06ef66547336cabd3cab40dd04L151 Pushing a patch soon. |
I've found the erros:
But I didn't set any |
Thanks @nerddelphi ! @exekias does this sound sound familiar? |
As you guessed @nerddelphi, your issue should be fixed by #16450 |
Hi there,
I've found the erros: thanks for help. |
Hi there.
I'm using Filebeat 7.5.2 to read pod/container logs of GKE (k8s) using official Elastic Helm Charts. After upgrading to 7.6.0 it doesn't read pod/container logs anymore. There isn't any error in Filebeat logs (It runs as daemonset in all k8s nodes). No another config was changed in all environment and I've double checked that log files from pods are mounted correctly inside Filebeat pods as well.
Is the new autodiscover
scope
setting needed?My filebeat config:
The text was updated successfully, but these errors were encountered: