topic Re: Correspondence of data resolution of timeseries api to time frame in Dynatrace API

Correspondence of data resolution of timeseries api to time frame

kohei-saito — Mon, 28 Jan 2019 06:41:45 GMT

Hi,

we'd like to know which timeframe we should set corresponding to specific data resolution.

For example, I know I can get timeseries data for 1-min resolution if I call some timeseries API with "relativeTime=hour".

As this shows, when "relativeTime" is set as "hour", the resolution is 1 min.

In another sample, we can get 10-min resolution if we choose "day" for "relativeTime".

Thus, timeframe parameter(relativeTime/startTimestamp&endTimestamp) automatically determines data resolution.

Here, we would like to know, which timeframe we choose, which data retention we get.

Is there something like a table showing their correspondence?

Example like this:

timeframe	min	hour	day
dataresolution	1-min	1-min	10-min

Regards,

Kohei

Re: Correspondence of data resolution of timeseries api to time frame

skrystosik — Mon, 28 Jan 2019 07:59:04 GMT

I didn't find any data about this. I think this is because each metrics can have different resolution in the same timeframe. So there should be such table for each of them or at least for groups. I think this is why you have field resolutionInMillisUTC in response which tells you about what you get.

Sebastian

Re: Correspondence of data resolution of timeseries api to time frame

a_gravier — Fri, 10 May 2019 09:05:57 GMT

Hello,

I have do some tests for my needeed.

In order to have the most granularity on your data points (1 minute resolution) you have to request your API with a time frame less than 2 hours.

If you do that the resolutions are the followings :

datapoints < 14days, resolution = 1 minute ("resolutionInMillisUTC":
60000)

14 days < datapoints < 1 month, resolution = 5 minutes ("resolutionInMillisUTC":
300000)

datapoints> 1 month, resolution = 1 Hour ("resolutionInMillisUTC": 3600000)

When your request the API with another timeframe (for datapoints < 14 days) :

Last hour :"resolutionInMillisUTC":
60000, (1 minute)

Last 2 hours :"resolutionInMillisUTC": 60000, (1
minute)

Last 3 hours :"resolutionInMillisUTC": 120000,(2 minutes)

Last 6 hours :"resolutionInMillisUTC": 180000,(3 minutes)

Last day :"resolutionInMillisUTC": 600000,(10 minutes)

I hope it will help some of you.

Regards, Aurélien.

Re: Correspondence of data resolution of timeseries api to time frame

kenichi_kunimot — Fri, 24 May 2019 05:14:32 GMT

HI, AURELIEN

Thank you for your comment, it is helpful me too.

Is it same as a time scale of custom chart?

Regards,

Kei

Re: Correspondence of data resolution of timeseries api to time frame

a_gravier — Fri, 24 May 2019 08:35:57 GMT

Hello,

I talked about the API data resolution for time series.

But if you talk about the resolution on the graphical view (custom chart or service view) , I have selected a custom timeframe with a duration of 3 hours and I have a point every 2 minutes, so it seems to be the same.

Regards Aurélien.