You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We always get logs with stream set to stderr for our own components in k8s cluster (workload pods) and for Kubernetes kube-system pods. It's very strange that it's always stderr. Of course it depends on app but we suppose that all apps could not write to stderr instaed of stdout.
Smaple output from logs:
We were going to use stream to split between info and critical logs but now it seems not possible. Is it expected Kubernetes source Vector.dev behavior or do we misconfigure something? The config was tested on 2 different clusters (on prem and cloud). We use 0.34.1 Vector.dev version and 0.29.0 Vector.dev chart.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi al!!
We use Kubernetes source with the following config:
We always get logs with stream set to stderr for our own components in k8s cluster (workload pods) and for Kubernetes kube-system pods. It's very strange that it's always stderr. Of course it depends on app but we suppose that all apps could not write to stderr instaed of stdout.
Smaple output from logs:
We were going to use stream to split between info and critical logs but now it seems not possible. Is it expected Kubernetes source Vector.dev behavior or do we misconfigure something? The config was tested on 2 different clusters (on prem and cloud). We use 0.34.1 Vector.dev version and 0.29.0 Vector.dev chart.
Maybe it's related somehow relate to future enhancement in k8s (kubernetes/enhancements#3288).
Any suggestion would be appriciated.
Beta Was this translation helpful? Give feedback.
All reactions