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
Hey!
Assuming linkerd sidecar container has access to the main container’s system info,
I want to implement my own metrics polling system in the sidecar container and publish them to Prometheus. That way the main container wont get affected. This implementation on paper doesn’t seem to be tough task. Can someone please tell me how feasible this idea is and if so what are the pros and cons? One of the cons seems to be the security concern of main container exposing sys info.
Reasons to want to implement this change:
not satisfied with k8s pod metrics, want to have control over the collected metrics
While changes can be made to the k8s metrics APIs, taking the k8s updates to production takes a lot of time
updates in linkerd meanwhile could be taken to production relatively fast
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
-
Hey!
Assuming linkerd sidecar container has access to the main container’s system info,
I want to implement my own metrics polling system in the sidecar container and publish them to Prometheus. That way the main container wont get affected. This implementation on paper doesn’t seem to be tough task. Can someone please tell me how feasible this idea is and if so what are the pros and cons? One of the cons seems to be the security concern of main container exposing sys info.
Reasons to want to implement this change:
Beta Was this translation helpful? Give feedback.
All reactions