Open ardikabs opened 7 months ago
hey @ardikabs can you share a little more info on the intent ? does this allow specific teams/apps to concentrate/filter on their relevant metrics ?
hi @arkodg , here are the objectives:
But please enlighten me, whether this can actually be done at the moment.
reg 1. before we decide to copy input labels to output, would default labels such as httproute=<name>
help ?
reg2. have you tried enabling enableVirtualHostStats
https://gateway.envoyproxy.io/v0.6.0/api/extension_types/#proxymetrics , these stats are per virtual host and EG has a 1:1 mapping b/w virtual host and hostname . Would be good to also highlight this in our dashboard https://gateway.envoyproxy.io/latest/user/grafana-integration/
cc @zirain
EG can provide mechanism support this, but IMO should be default off.
@arkodg
reg 1. before we decide to copy input labels to output, would default labels such as httproute=
help ?
I would say for my use case, doesn't seem to help. I mean, what if add an opt-in possibility for the user to add additional labels to the metric, for example, from the xRoute labels itself?
reg2. have you tried enabling enableVirtualHostStats https://gateway.envoyproxy.io/v0.6.0/api/extension_types/#proxymetrics , these stats are per virtual host and EG has a 1:1 mapping b/w virtual host and hostname. Would be good to also highlight this in our dashboard
I tried this, but it doesn't appear to align with my need, because I'm expecting any metric associated to HTTPRoute information should include additional details, because we can see in HTTPRoute spec also specify hostname. However, I would appreciate clarification if I have misunderstood this understanding.
and actually enableVirtualHostStats does not contain metric for instance duration buckets
This issue has been automatically marked as stale because it has not had activity in the last 30 days.
Description: Although metrics emitted by the envoy instance look good, it shows a very limited label in it, for example:
Subsequently, wonder about the feasibility of adding more valuable information, such as the labels from
xRoute
resources directly into the metric.An example of this could be the application of the following
HTTPRoute
manifest:As a result, the Envoy-emitted metric would appear as shown below:
[optional Relevant Links:]