On 21/01/2022 14:09, Ramachandra Bhaskar Ayalavarapu wrote:
We have some data points like this
{
"__name__": "http_request_duration_seconds_bucket",
"endpoint": "apssd",
"instance": "10.10.77.218:8080 <http://10.10.77.218:8080>",
"job": "api-service",
"le": "0.05",
"method": "GET",
"namespace": "foo",
"pod": "bar",
"route": "/localhsdssds/v1/project/<unique
projectid>/provider/WmRESTProvider/blasdsdsd/fummssd/icon",
"service": "api-service",
"status": "4XX"
}
unfortunately though we understand its not best practice to add
"route" in the label name which is driving cardinality we cannot do
anything as team is not ready to change code. Can i put a first aid
any way to reduce the cardinality. (this metric) is too important to drop
some thing like project wise etc by writing rewrite rule. if yes
please advice how ?
You could drop that label in metrics relabling.
--
Stuart Clark
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/prometheus-users/bfc08af7-59c9-4193-4260-8b4d60862a90%40Jahingo.com.
