Nguyen Phuc Khang
09/24/2025, 5:11 AMkube.* and Parser cri, and an OUTPUT to stdout.
I’m not using any additional filters or anything else.
The result is that my logs contain fields like message, time, … and also a kubernetes field (which includes labels, annotations, container info, …). While that’s what I expect, I only need a few fields from it.
I’ve already tried add FILTER kubernetes, modify, and record_modifier, but they don’t seem to have any effect (nothing changes in the OUTPUT).
inputs: |
[INPUT]
Name tail
Path /var/log/containers/mybunkerweb-default.log
Parser cri
Tag kube.*
outputs: |
[OUTPUT]
Name stdout
Is there a hidden part of the pipeline that automatically adds these fields and cannot be modified? If my INPUT tag is not kube.* (e.g. myappp.*), then there is no kubernetes field in the log. But if the INPUT tag is kube.*, the Kubernetes fields appear, and I don’t know how to remove the unnecessary fields from them.Pat
09/24/2025, 8:06 AMPat
09/24/2025, 8:07 AMPat
09/24/2025, 8:07 AMPat
09/24/2025, 8:08 AMPat
09/24/2025, 8:08 AMPat
09/24/2025, 8:22 AMNguyen Phuc Khang
09/24/2025, 9:55 AMinputs: |
[INPUT]
Name tail
Path /var/log/containers/myapp-*_default_*.log
Parser cri
Tag kube.*
## <https://docs.fluentbit.io/manual/pipeline/outputs>
filter: |
[FILTER]
Name kubernetes
Match kube.*
[FILTER]
Name nest
Match *
Operation lift
Nested_Under kubernetes
[FILTER]
Name record_modifier
Match *
Record hostname $kubernetes['host]
outputs: |
[OUTPUT]
Name stdout
Match *Pat
09/24/2025, 9:56 AMhost?Pat
09/24/2025, 9:56 AMNguyen Phuc Khang
09/24/2025, 9:57 AMdocker_id, labels, annotation, etc.Pat
09/24/2025, 9:57 AMPat
09/24/2025, 9:58 AMNguyen Phuc Khang
09/24/2025, 9:58 AMPat
09/24/2025, 9:58 AMPat
09/24/2025, 9:59 AMPat
09/24/2025, 9:59 AMPat
09/24/2025, 10:00 AM[FILTER]
name kubernetes
match kube.*
labels off
annotations off
use_tag_for_meta onNguyen Phuc Khang
09/24/2025, 10:05 AMinputs: |
[INPUT]
Name tail
Path /var/log/containers/myapp-*_default_*.log
Parser cri
Tag kube.*
## <https://docs.fluentbit.io/manual/pipeline/outputs>
filter: |
[FILTER]
name kubernetes
match kube.*
labels off
annotations off
use_tag_for_meta on
outputs: |
[OUTPUT]
Name stdout
Match *Nguyen Phuc Khang
09/24/2025, 10:05 AMPat
09/24/2025, 10:06 AMPat
09/24/2025, 10:06 AMPat
09/24/2025, 10:07 AMPat
09/24/2025, 10:10 AMNguyen Phuc Khang
09/24/2025, 10:11 AMcurl <http://127.0.0.1:2020/api/v1/metrics/> | jq, but it seems to be processed.
Actually, I need kubernetes.host and pod_name.Nguyen Phuc Khang
09/24/2025, 10:11 AMPat
09/24/2025, 10:12 AMPat
09/24/2025, 10:12 AMNguyen Phuc Khang
09/24/2025, 10:12 AMPat
09/24/2025, 10:12 AMPat
09/24/2025, 10:16 AM${VAR_NAME} syntax for the value.
For pod name you can extract it from the filename using tag_regex in the tail input: https://docs.fluentbit.io/manual/data-pipeline/inputs/tail
You can also add the whole filename automatically with path_keyNguyen Phuc Khang
09/24/2025, 10:16 AMPat
09/24/2025, 10:22 AMenvFrom:
- name: MY_NODE_NAME
valueFrom:
fieldRef:
fieldPath: spec.nodeName
config:
inputs: |
[INPUT]
name tail
tag kube.*
path /var/log/containers/*.log
multiline.parser docker, cri
tag_regex (?<pod_name>[a-z0-9](?:[-a-z0-9]*[a-z0-9])?(?:\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*)_.*\.log$
filters: |
[FILTER]
name modify
match *
add nodename ${MY_NODE_NAME}
something like this - I've not tested