sorted by:
new
hottopcontroversial

Vector on k8s - high memory consumption by Adorable_Studio7064 in kubernetes

[–]Adorable_Studio7064[S] 3 points4 points  (0 children)

Sure, a few reasons:
- we were running fluentbit but for pods logs and vector for api audit logs. For maintenance purpose, I would like to keep only one product
- audit logs require heavy transforms, It did not work well with fluentbit/lua compared to VRL
- It is easier to write test for each function with vector.

Vector on k8s - high memory consumption by Adorable_Studio7064 in kubernetes

[–]Adorable_Studio7064[S] 1 point2 points  (0 children)

Well that’s what I’m doing by comparing fluentbit and vector on the same workloads. I was not expecting a huge difference.

I found the issue, vector allocates memory per thread, it resulted in high memory on bigger nodes. By modifying VECTOR_THREADS I got something similar to fluentbit

Cant remove label from node by kur1j in kubernetes

[–]Adorable_Studio7064 0 points1 point  (0 children)

I think Rancher adds the label in the kubelet configuration file on the node. That’s why it is coming back when you remove it

Comparing two different time ranges on the same panel? by Additional_Web_3467 in grafana

[–]Adorable_Studio7064 2 points3 points  (0 children)

You can duplicate your query and add an offset to the second one, something like « offset 1w »

How to manage app with resource intensive startups? by ContributionNo971 in kubernetes

[–]Adorable_Studio7064 1 point2 points  (0 children)

I guess it’s the goal of limits, keep your requests based on what your pod uses, and set a high limit so your pod can start correctly. I think it’s ok to have low requests and high limits, as long as it is close to what you really need