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
Did anyone already worked on some sort of configuration/customization of OTEL to, based in a list of namespaces and containers, define what gets forwarded to Splunk or not? Some sort of "gatekeeper" that can be maintained and ideally (but not mandatorily) won't require pod restart on every list update?
My scenario:
I install this OTEL in a huge shared cluster, but I don't want to monitor all namespaces and containers there, just a handful of those. How can I make sure I only stream what I need?
Today I stream anything, and filter out at the Splunk Heavy Forwarder level.
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.
-
Hi all,
Did anyone already worked on some sort of configuration/customization of OTEL to, based in a list of namespaces and containers, define what gets forwarded to Splunk or not? Some sort of "gatekeeper" that can be maintained and ideally (but not mandatorily) won't require pod restart on every list update?
My scenario:
I install this OTEL in a huge shared cluster, but I don't want to monitor all namespaces and containers there, just a handful of those. How can I make sure I only stream what I need?
Today I stream anything, and filter out at the Splunk Heavy Forwarder level.
Beta Was this translation helpful? Give feedback.
All reactions