<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Using starttimestamp and endtimestamp in API in Dynatrace API</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-API/Using-starttimestamp-and-endtimestamp-in-API/m-p/65830#M275</link>
    <description>&lt;P&gt;Hi Patrick,&lt;/P&gt;&lt;P&gt;thank you for a very fine answer. I looked into it &lt;BR /&gt;in greater details, and it seems there actually was no datapoints in the&lt;BR /&gt; given timeperiod, so dynatrace was rigth.&lt;/P&gt;&lt;P&gt;Thats probably also why dynatrace use resolution as the difference between start and end time.&lt;/P&gt;&lt;P&gt;Makes sense.&lt;/P&gt;&lt;P&gt;Thanks again for your investigation and resolving of my issue.&lt;/P&gt;&lt;P&gt;Carl&lt;/P&gt;</description>
    <pubDate>Thu, 26 Apr 2018 08:16:24 GMT</pubDate>
    <dc:creator>cbruhn2</dc:creator>
    <dc:date>2018-04-26T08:16:24Z</dc:date>
    <item>
      <title>Using starttimestamp and endtimestamp in API</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Using-starttimestamp-and-endtimestamp-in-API/m-p/65828#M273</link>
      <description>&lt;P&gt;When I use the starttimestamp and endstimestamp in a call to API like in&lt;/P&gt;
&lt;PRE&gt;n&amp;amp;startTimestamp=1522540974000&amp;amp;endTimestamp=1524528174000&amp;amp;aggregationType=median&amp;amp;queryMode=series&lt;/PRE&gt;
&lt;P&gt;I just get&lt;/P&gt;
&lt;PRE&gt;result&lt;BR /&gt;dataPoints&lt;BR /&gt;timeseriesId"com.dynatrace.builtin:appmethod.useractionduration"&lt;BR /&gt;unit"MicroSecond (µs)"&lt;BR /&gt;entities:&lt;BR /&gt;resolutionInMillisUTC   1987210000&lt;BR /&gt;aggregationType"MEDIAN"&lt;/PRE&gt;
&lt;P&gt;And no datapoinst because the resolution is jus the difference between end and starttime.&lt;/P&gt;
&lt;P&gt;Is this a bug ?&lt;/P&gt;
&lt;P&gt;When I use relativetime&lt;/P&gt;
&lt;PRE&gt;n&amp;amp;relativeTime=month&amp;amp;aggregationType=median&amp;amp;&lt;/PRE&gt;
&lt;P&gt;i get datapoints but with a resolution of 6 hours. (Thats a long time resolution and only 4 measurement per day)&lt;/P&gt;
&lt;P&gt;I have voted for the RFE to be able to specify resolution in the API call&lt;/P&gt;</description>
      <pubDate>Tue, 25 May 2021 14:35:39 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Using-starttimestamp-and-endtimestamp-in-API/m-p/65828#M273</guid>
      <dc:creator>cbruhn2</dc:creator>
      <dc:date>2021-05-25T14:35:39Z</dc:date>
    </item>
    <item>
      <title>Re: Using starttimestamp and endtimestamp in API</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Using-starttimestamp-and-endtimestamp-in-API/m-p/65829#M274</link>
      <description>&lt;P&gt;That is strange, which version are you on? SaaS or Managed?&lt;/P&gt;&lt;P&gt;I tried it with the same timestamp in my environment an it works fine, the resoltion I get is:  14400000&lt;/P&gt;&lt;PRE&gt;xxx.dynatrace-managed.com/e/xxx/api/v1/timeseries?startTimestamp=1522540974000&amp;amp;endTimestamp=1524528174000&amp;amp;timeseriesId=com.dynatrace.builtin:appmethod.useractionduration&amp;amp;queryMode=series&amp;amp;aggregationType=MEDIAN&lt;/PRE&gt;&lt;P&gt;p.s. Great to hear you have voted for our RFE &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Apr 2018 13:58:42 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Using-starttimestamp-and-endtimestamp-in-API/m-p/65829#M274</guid>
      <dc:creator>pahofmann</dc:creator>
      <dc:date>2018-04-25T13:58:42Z</dc:date>
    </item>
    <item>
      <title>Re: Using starttimestamp and endtimestamp in API</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Using-starttimestamp-and-endtimestamp-in-API/m-p/65830#M275</link>
      <description>&lt;P&gt;Hi Patrick,&lt;/P&gt;&lt;P&gt;thank you for a very fine answer. I looked into it &lt;BR /&gt;in greater details, and it seems there actually was no datapoints in the&lt;BR /&gt; given timeperiod, so dynatrace was rigth.&lt;/P&gt;&lt;P&gt;Thats probably also why dynatrace use resolution as the difference between start and end time.&lt;/P&gt;&lt;P&gt;Makes sense.&lt;/P&gt;&lt;P&gt;Thanks again for your investigation and resolving of my issue.&lt;/P&gt;&lt;P&gt;Carl&lt;/P&gt;</description>
      <pubDate>Thu, 26 Apr 2018 08:16:24 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Using-starttimestamp-and-endtimestamp-in-API/m-p/65830#M275</guid>
      <dc:creator>cbruhn2</dc:creator>
      <dc:date>2018-04-26T08:16:24Z</dc:date>
    </item>
    <item>
      <title>Re: Using starttimestamp and endtimestamp in API</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Using-starttimestamp-and-endtimestamp-in-API/m-p/65831#M276</link>
      <description>&lt;P&gt;Glad I could help, good to know that the resolution is equal to timeframe when there are no datapoints, could have fallen into this myself &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Apr 2018 14:48:20 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Using-starttimestamp-and-endtimestamp-in-API/m-p/65831#M276</guid>
      <dc:creator>pahofmann</dc:creator>
      <dc:date>2018-04-26T14:48:20Z</dc:date>
    </item>
  </channel>
</rss>

