Is your feature request related to a problem? Please describe.
I’d like to write a data export script that can ignore traffic originating from the Vizier itself, and not export those events. I'm thinking it would make sense to match on the Kubernetes namespace of the traffic source. But I would rather not hardcode the install namespace into the script: I'd like a single re-usable script that could be used across any cluster, regardless of the choice of installation namespace for Vizier.
Describe the solution you'd like
Ideally I could call a function from within the PxL script that would return the Kubernetes namespace into which Vizier is currently installed and running.
Describe alternatives you've considered
The only alternatives would require customizing my export script on a per-cluster basis, which would be a big operational burden.
Additional context
Discussed in Pixie slack here, Michelle suggested:
I think we can add a pretty simple UDF similar to the vizier_name UDF:
|
class VizierNameUDF : public ScalarUDF { |
.
Is your feature request related to a problem? Please describe.
I’d like to write a data export script that can ignore traffic originating from the Vizier itself, and not export those events. I'm thinking it would make sense to match on the Kubernetes namespace of the traffic source. But I would rather not hardcode the install namespace into the script: I'd like a single re-usable script that could be used across any cluster, regardless of the choice of installation namespace for Vizier.
Describe the solution you'd like
Ideally I could call a function from within the PxL script that would return the Kubernetes namespace into which Vizier is currently installed and running.
Describe alternatives you've considered
The only alternatives would require customizing my export script on a per-cluster basis, which would be a big operational burden.
Additional context
Discussed in Pixie slack here, Michelle suggested: