How to exclude 403 from fourxx errors in Metric selector

padarthimanoj — Thu, 18 Dec 2025 10:57:02 GMT

i want to exclude 403 from this metric selector of query queryDefinition for API yaml

builtin:service.keyRequest.errors.fourxx.count:filter(and(or(in("dt.entity.service_method",entitySelector("type(service_method),entityName.equals(~"<my-api-url>~")"))))):splitBy():sort(value(auto,descending)):limit(20)

i have tried this

builtin:service.keyRequest.errors.fourxx.count:filter(and(ne("http.status",403),or(in("dt.entity.service_method",entitySelector("type(service_method),entityName.equals(~"<my-api-url>~")"))))):splitBy():sort(value(auto,descending)):limit(20)

but i am getting error that http.status is not a valid dimension. we are using dyntrace classic

is it possible through queryDefinition or any other setting configuration is required?

Re: how to exclude 403 from fourxx error for metric selector

Julius_Loman — Wed, 08 Oct 2025 06:12:12 GMT

It simple - you cannot. This classic metric sums all 4xx codes already.
If you need any other behaviour, there are multiple ways. Probably I'd go with defining a calculated service metric for this purpose.

If you are on SaaS, the Grail metric has the dimension:

timeseries sum(dt.service.request.failure_count), by: { http.response.status_code }

topic Re: how to exclude 403 from fourxx error for metric selector in Dashboarding

How to exclude 403 from fourxx errors in Metric selector

Re: how to exclude 403 from fourxx error for metric selector