Hi, we're seeing very high memory usage on the metrics for rate limit requests sent with a rate limit override. Currently for rate limit override the value of entries is included in the stats key https://github.com/envoyproxy/ratelimit/blob/main/src/config/config_impl.go#L679-L691. This creates high cardinality for these requests. Is there an option to choose which entry values to include in the stats keys? Something like https://github.com/envoyproxy/ratelimit#including-descriptor-values-in-metrics which exists for those entries in the configuration.
Hi, we're seeing very high memory usage on the metrics for rate limit requests sent with a rate limit override. Currently for rate limit override the value of entries is included in the stats key https://github.com/envoyproxy/ratelimit/blob/main/src/config/config_impl.go#L679-L691. This creates high cardinality for these requests. Is there an option to choose which entry values to include in the stats keys? Something like https://github.com/envoyproxy/ratelimit#including-descriptor-values-in-metrics which exists for those entries in the configuration.