Need Dashboard for Requests that are not marked as key request

[sa_gopalm]

i need to get the requests response time average, min and max but i couldnt do it for the non key request , how can it be done either via DQL or data explore , Please share any JSON for dashboard or DQL Queries if possible 

[p_devulapalli · Accepted solution]

@sa_gopalm I think you need to first mark them as key requests to get the expected data and endpoint details or else they would be showing up as NON_KEY_REQUESTS in dashboard which is not much helpful . You can use a DQL query similar to below 

timeseries { avg(dt.service.request.response_time), ResponseTime = avg(dt.service.request.response_time, scalar: true) }, by: { endpoint.name, dt.entity.service }
| fieldsAdd dt.entity.service.name = entityName(dt.entity.service)

[Julius_Loman]

In addition to @p_devulapalli answer  (which is the recommended method), you might want to use spans as a source for your dashboards, or define span metrics in OpenPipeline.

[paolo_fumanelli]

Multidimensional analysis is an option for such cases

[Theodore_x86]

I was under the impression that on GRAIL, every service metric would be able to be split per request.

😞

[p_devulapalli]

@Theodore_x86 I think that's now possible in Grail if you have the below enabled 

https://docs.dynatrace.com/docs/observe/application-observability/services/service-detection/service...

[sujit_k_singh]

Hi @Theodore_x86 

Confirming @p_devulapalli  is right — Enhanced endpoints for SDv1 is exactly the fix for this. It replaces the old NON_KEY_REQUESTS bucket with individual dt.service.request.* metrics for every detected endpoint, no manual key request marking needed.

@sa_gopalm  if you're revisiting this: go to Settings > Process and contextualize > Services > Enhanced endpoints for SDv1, and turn it on. After that, this kind of query works for every endpoint, not just key requests:

timeseries { avg(dt.service.request.response_time), min(dt.service.request.response_time), max(dt.service.request.response_time) }, by: { endpoint.name, dt.entity.service }
| fieldsAdd dt.entity.service.name = entityName(dt.entity.service)

One heads-up: enabling it can change endpoint naming and may affect existing dashboards/alerts tied to the old NON_KEY_REQUESTS or GET /* names, so worth a quick audit first.

Thanks,

Sujit

[Theodore_x86]

Thanks @p_devulapalli  and @sujit_k_singh for your comments! That option did the trick.

As you mentioned, the request name changes in a lot of cases so be cautious. For us it adds the "POST/GET/DELETE" before the endpoint name....

BR