Replies: 1 comment 3 replies
-
I regenerate a label by using expressions of Envoy attributes and Peer metadata.
Then I find "dimensions" field in Envoy config_dump. Is it meaning that label "source_app" is considered as a customized label currently? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
If I removed a set of labels in Namespace-specific Telemtry API with Namespace-scoped overrides, then I want to resume them in Workload-specific Telemetry API with Workload-scoped overrides. How can I configure the new Telemtry?
In Telemtry API doc, there are some expressions about this below, I am wondering whether my requirement can be implemented:
Specified overrides will be applied in order. They will be applied on top of inherited overrides from other resources in the hierarchy in the following order:
Mesh-scoped overrides
Namespace-scoped overrides
Workload-scoped overrides
Because overrides are applied in order, users are advised to order their overrides from least specific to most specific matches. That is, it is a best practice to list any universal overrides first, with tailored overrides following them.
In EnvoyFilter, I can achieve it which "REPLACE" the "istio.stats" Filter totally.
However, in Telemetry API, the field MetricsOverrides.TagOverride.Operation can be set as "UPSERT" or "REMOVE", maybe both of Operations can't regenerate the labels removed previously?
Beta Was this translation helpful? Give feedback.
All reactions