Filebeat autodiscoverkubernetes appender error bug #9817
Labels
bug
containers
Related to containers use case
Filebeat
Filebeat
libbeat
Team:Integrations
Label for the Integrations team
Please post all questions and issues on https://discuss.elastic.co/c/beats
before opening a Github Issue. Your questions will reach a wider audience there,
and if we confirm that there is a bug, then you can open a new issue.
For security vulnerabilities please only send reports to security@elastic.co.
See https://www.elastic.co/community/security for more information.
Please include configurations and logs if available.
For confirmed bugs, please report:
reference Filebeat kubernetes autodiscover Multiple conditions 1
The problem is When the condition has “kubernetes.labels.log-index” ,fields:log_topic: 'labels-{data.kubernetes.labels.log-index}', otherwise fields: log_topic: 'aip-{data.kubernetes.namespace}-${data.kubernetes.pod.name}'
The default condition not.equals.kubernetes.container.name: "filebeat" 。
Currently in use appenders ,But error is ERROR instance/beat.go:691 Exiting: unknown autodiscover appender config
Reference : Filebeat autodiscovery appenders , But there are still ERROR instance/beat.go:691 Exiting: unknown
filebeat run kubernetes daemonset.
filebeat docker image
docker.elastic.co/beats/filebeat:6.5.4
or
docker.elastic.co/beats/filebeat-oss:6.5.3
filebeat.yaml
The text was updated successfully, but these errors were encountered: