cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Query request count ( time series data ) using HTTP headers / attributes in Dynatrace DQL

Butchi
Newcomer

I have a java application with bunch of API end points and each end point has a unique identifier in the HTTP header header ( for example : sourceID as one identifier in the request header).  Whats the best way to get the  request count ( as time series data ) for each endpoint using service name and HTTP header attributes ?

In this case :

my service name = XYX_Service

Endpoint  = processRequest

URL path  = /api/my_request

HTTP request header attribute sourceID =abc

 

3 REPLIES 3

dannemca
DynaMight Guru
DynaMight Guru

You could enable the business events capture for these requests, and extract the HTTP header as attribute, then you can easily summarize it.

https://docs.dynatrace.com/docs/observe/business-observability/bo-events-capturing#examples-of-data-... 

Or, you could create a request attribute from classic settings, and create a calculated service metric from MDA app, using the created request attribute as dimension.

https://docs.dynatrace.com/docs/observe/applications-and-microservices/services/request-attributes/c... 

https://docs.dynatrace.com/docs/observe/applications-and-microservices/multidimensional-analysis#cal... 

Site Reliability Engineer @ Kyndryl

Hi @dannemca Yes we enabled those business events to capture business level metrics but we're not able to capture response times, failures and request counts via business events unless we're missing some additional steps in business events config.

From classic setting page, we have a request attribute rule to capture those headers ( using HTTP Request header as attribute source ) but those request attribute are not showing up as dimension although we have some traffic. Not sure what the issue was and whats causing it not to show up. 

 

 

Butchi
Newcomer

Just to add , From classic setting page, with request attribute rule, Dynatrace shows ( Under Explore view ) those attributes under HTTP Headers as opposed to showing it under Request attributes. This is preventing us to create a calculated service metric using those dimensions.

Featured Posts