Hi @Wolfgang B..
thanks for your prompt response!
After subscription of specific endpoint URIs at my Dynatrace tenant, I checked if I can retrieve response time of them or not, using such as the following API.
https://[your-environment-id].live.dynatrace.com/api/v1/timeseries/com.dynatrace.builtin:servicemethod.responsetime?api-token=xxxxxxxxx&includeData=true&relativeTime=hour&aggregationType=avg&entity=SERVICE_METHOD-XXXXXXXX
Using this API, I could finally do what I wanted to do.
Thank you very much!
Appendix:
In addition to the above, I made some investigations as follows.
I’m glad if they are helpful for you!
Case1: Without ‘entity’ of GET parameters
example API
https://[your-environment-id].live.dynatrace.com/api/v1/timeseries/com.dynatrace.builtin:servicemethod.responsetime?api-token=xxxxxxxxx&includeData=true&relativeTime=hour&aggregationType=avg
overview
This returns response time of all URIs subscribed as ‘Key request’ on the tenant.
This enables us to fetch all response time of ‘Key request’ at one time API call and it means that this can keep us from over-consuming API requests limit.
Case2: With entityID which is not subscribed as ‘Key request’ for ‘entity’
example API
Here, let ‘SERVICE_METHOD-YYYYYYYYYY’ be not subscribed as ‘Key request’
https://[your-environment-id].live.dynatrace.com/api/v1/timeseries/com.dynatrace.builtin:servicemethod.responsetime?api-token=xxxxxxxxx&includeData=true&relativeTime=hour&aggregationType=avg&entity=SERVICE_METHOD-YYYYYYYYYY
overview
This returns metric definitions of this timeseriesIdentifier included in this api path*.*
note) Here ‘com.dynatrace.builtin:servicemethod.responsetime’ is indicated as timeseriesIdentifier.