Hi Team,
I'm evaluating moving our Windows workloads to Kubernetes and would like to use filebeat for logs shipment. I've created DaemonSet where I mounted hostPathes:
- /var/log
- /ProgramData/docker/containers
My filebeat configuration looks like:
filebeat.autodiscover:
providers:
- type: kubernetes
hints:
enabled: true
default_config:
type: container
paths:
- "C:\\var\\log\\containers\\*"
output.console:
pretty: true
processors:
- add_host_metadata: ~
- add_cloud_metadata: ~
- add_kubernetes_metadata: ~
logging:
level: debug
I can confirm that I can read from logs file from container context, but add_kubernetes_metadata
processor is failing with following errors:
2020-08-19T13:10:37.084Z DEBUG [input] log/input.go:494 Start harvester for new file: C:\var\log\containers\open-app-8fd9f9fcb-htbs8_default_open-app-09c468ee2146e47ec601e37dccbbabca246ee52dff196b2e573965225149b3ea.log
2020-08-19T13:10:37.138Z ERROR [kubernetes] add_kubernetes_metadata/matchers.go:91 Error extracting container id - source value does not contain matcher's logs_path 'C:\ProgramData\Docker\containers\'.
- Version:
filebeat version 7.8.1 (amd64), libbeat 7.8.1 [94f7632be5d56a7928595da79f4b829ffe123744 built 2020-07-21 15:12:43 +0000 UTC]
- Operating System:
Windows Server 2019 10.0.17763 N/A Build 17763