Replies: 1 comment
-
|
Your configuration is likely wrong as the utilization metric and file source show that nothing is being written and no files are being observed. It is possible no files are present in I also suggest following the official redhat guide if you're using openshift 4: https://developers.redhat.com/articles/2025/09/04/how-migrate-fluentd-vector-openshift-4?sc_cid=RHCTG0240000434042#migrate_fluentd_to_vector_in_openshift |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Question
Vector doesn't process k8s/Openshift pod logs, like at all. I have one source of kubernetes_logs configured, but vector is idling, logging nothing even in debug mode. The console test input/sink to the same place successfully ships logs to victoriametrics server.
I ran an nginx pod after deploying vector (although there's tons of other pods running whose logs aren't checkpointed) which produced the following logs:
Below I attach the vector pod log from the same node that nginx pod was scheduled at. As you can see there's nothiing about the newly created pod logs in it.
Vector also did not checkpoint any of the logs in it's data directory:
Vector DaemonSet
Vector Config
Vector Logs
Beta Was this translation helpful? Give feedback.
All reactions