You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the above example, the only metric I want to keep is envoy_cluster_external_upstream_rq, but when adding this except clause, I am also forced to keep every other metric with the prefix envoy_cluster_external_upstream_rq, so I'll end up having other metrics I don't want, like envoy_cluster_external_upstream_rq_time for example.
Acceptance Criteria
Add regex support, instead of only supporting metrics prefixes.
Estimates
T-shirt size: S = 1-3 days
The text was updated successfully, but these errors were encountered:
Description
Currently, when metrics are excluded and we want to add an exception for a subset of metrics, the only option is to add an exception for a prefix.
This is a problem, as it forces us to keep metrics we don't necessarily want. For example, let's look at the following rules:
In the above example, the only metric I want to keep is
envoy_cluster_external_upstream_rq
, but when adding thisexcept
clause, I am also forced to keep every other metric with the prefixenvoy_cluster_external_upstream_rq
, so I'll end up having other metrics I don't want, likeenvoy_cluster_external_upstream_rq_time
for example.Acceptance Criteria
Add regex support, instead of only supporting metrics prefixes.
Estimates
T-shirt size: S = 1-3 days
The text was updated successfully, but these errors were encountered: