Filtering by namespace/container level

[vscastro2]

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.

[atoulme]

You can see this in our documentation, you can include, exclude namespaces and deployments, as well as route the logs to different indexes and sourcetypes.