Dynatrace Managed Timeseries API month granularity

[david_sipos]

Hi,

I case I fetch timeseries data via API with post data like

{u'aggregationType': u'avg', u'relativeTime': u'month', u'timeseriesId': u'com.dynatrace.builtin:host.cpu.user', entity...

in api response I get only 4 datapoints/day - meaning data from every 6th hours.

request url:https://XYZ.dynatrace-managed.com/e/72bfd0af-3695-XXXX-adff-XXXXXXXXXXXX/api/v1/timeseries">https://XYZ.dynatrace-managed.com/e/72bfd0af-3695...<br><br>data retrieved:
                     entity                time     value
0     HOST-6315BA776DCE52A8 2018-12-21 12:00:00  0.632505
1     HOST-6315BA776DCE52A8 2018-12-21 18:00:00  0.607286
2     HOST-6315BA776DCE52A8 2018-12-22 00:00:00  0.618426
3     HOST-6315BA776DCE52A8 2018-12-22 06:00:00  0.630906
4     HOST-6315BA776DCE52A8 2018-12-22 12:00:00  0.638086
5     HOST-6315BA776DCE52A8 2018-12-22 18:00:00  0.598434
6     HOST-6315BA776DCE52A8 2018-12-23 00:00:00  0.609002
...

So my question: If I am fetching 1 month data as relative time do I have the option to get finer granularity- eg. hourly data. If yes, how?

[wolfgang_beer · Accepted solution]

The timeseries API delivers the result in 'auto' resolution. If you want to get minute resolution for a metric beyond 120 data points you have to query it with multiple calls going back in time. Minute resolution is available for 14days and will then be aggregated to 5min resolution. At the moment we are working on a new metric api that will simplify the query for custom resolutions. We plan to release that new metric API before summer and it will come with some major enhancements.

[david_sipos]

Thanks for the quick answer. For a relative time of 1 month period hourly resolution would be fine for me so I don't need minute or 5 min based one - so 1 month period with hourly data is also not possible?

The limit 120 points / query is regardless the amount of entities in scope?

[wolfgang_beer]

Sure you can do that, just request an absolute timeframe for 120 hours and you will get the hour resolution. Then you simply iterate back in time in 120 hour steps.