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
In Kubernetes clusters under my control, some installations of Vector consume a lot of CPU and memory (3 cores and 7Gb RAM top). Probably, the problem is with the configuration, but I want to find exactly where.
Do you have any tips or tricks how I can shed more light on why vector has such an appetite? It would be nice if there is the way to extract the date from a running process, but not required.
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
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, Vector team!
In Kubernetes clusters under my control, some installations of Vector consume a lot of CPU and memory (3 cores and 7Gb RAM top). Probably, the problem is with the configuration, but I want to find exactly where.
Do you have any tips or tricks how I can shed more light on why vector has such an appetite? It would be nice if there is the way to extract the date from a running process, but not required.
Beta Was this translation helpful? Give feedback.
All reactions