I'm new on Dynatrace API and I'm trying to get automatically the same information I see on UI.
In particular I'd like to get, for any service on a host, the list of service methods with the number of requests (the same information I can see in the screenshot below).
I've the list of services on host but I haven't found an API to get the service method list.
With this info I think I can use the metric "com.dynatrace.builtin:servicemethod.responsetime" but without the service method entity id I'm stucked.
Could you help me?
Thanks a lot!
Solved! Go to Solution.
In order to pull response time data out of Dynatrace per request, you have to mark the requests that you want to pull as key requests.
Performance data for requests is aggregated at the service level and stored for that service in a manner that the Metrics API can query. Marking a request as a key request makes Dynatrace store performance data for just that request separately as well, so it can be viewed for a longer period of time and queried through the APIs.
Once you mark your request as a key request, you can use the below API to pull response time data:
The below endpoint should be what you are looking for:
All of the available metrics for Key Requests are on this page:
thanks for your reply. I've understood I need to set response.time and count.total as key requests before do any query.
But, if key requests are aggregated at the service level I've to set key requests for any service on any server?
In my case I've 5 servers and each server host about 300 services (with an average of 30 service methods each). I've to set key requests on any service of any server?
Thanks for your time
So response.time and count.total are metrics. What you want is to set SearchCustomer as a key request, then the SearchCustomer request will be given its own performance metrics aside from the service.
If all of the services are named the same and belong to the same process group, then changing Search Customer to a key request for one service should change them for all hosts.
Otherwise, you'll have to do this for each request and service pairing you want to pull data for.