<?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: Service request level retention	vs. Timeseries metrics in Real User Monitoring</title>
    <link>https://community.dynatrace.com/t5/Real-User-Monitoring/Service-request-level-retention-vs-Timeseries-metrics/m-p/124443#M2339</link>
    <description>&lt;P&gt;Multidimensional data has only service level metrics available from transactions. You can create Custom Metrics (or soon will be able to) based on those data and than you will have better data retention.&lt;/P&gt;&lt;P&gt;Sebastian &lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 14 Jan 2020 11:49:59 GMT</pubDate>
    <dc:creator>skrystosik</dc:creator>
    <dc:date>2020-01-14T11:49:59Z</dc:date>
    <item>
      <title>Service request level retention	vs. Timeseries metrics</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/Service-request-level-retention-vs-Timeseries-metrics/m-p/124442#M2338</link>
      <description>&lt;P&gt;Dear All,&lt;/P&gt;
&lt;P&gt;Service request level retention by default is configured for 35 days and the following is documented for Timeseries metrics.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;0-14 days: 1-minute interval granularity available for dashboarding and API access.&lt;/LI&gt;
&lt;LI&gt;14-28 Days: 5-minute interval granularity available for dashboarding and API access.&lt;/LI&gt;
&lt;LI&gt;28-400 days: 1-hour interval granularity available for dashboarding and API access.&lt;/LI&gt;
&lt;LI&gt;400+ days: 1-day interval granularity available for dashboarding and API access.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;A web service that is configured as '&lt;STRONG&gt;Key Request&lt;/STRONG&gt;' as well as '&lt;STRONG&gt;Multidimensional analysis views&lt;/STRONG&gt;'.&lt;/P&gt;
&lt;P&gt;We do not have metrics data of that web service for more than 35 days which tells us that the Service request level retention is applied to this request.&lt;/P&gt;
&lt;P&gt;When and how the Timeseries will be applied to Key Request and Multidimensional analysis views?&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Babar&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 30 Sep 2022 11:14:38 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/Service-request-level-retention-vs-Timeseries-metrics/m-p/124442#M2338</guid>
      <dc:creator>Babar_Qayyum</dc:creator>
      <dc:date>2022-09-30T11:14:38Z</dc:date>
    </item>
    <item>
      <title>Re: Service request level retention	vs. Timeseries metrics</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/Service-request-level-retention-vs-Timeseries-metrics/m-p/124443#M2339</link>
      <description>&lt;P&gt;Multidimensional data has only service level metrics available from transactions. You can create Custom Metrics (or soon will be able to) based on those data and than you will have better data retention.&lt;/P&gt;&lt;P&gt;Sebastian &lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 14 Jan 2020 11:49:59 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/Service-request-level-retention-vs-Timeseries-metrics/m-p/124443#M2339</guid>
      <dc:creator>skrystosik</dc:creator>
      <dc:date>2020-01-14T11:49:59Z</dc:date>
    </item>
  </channel>
</rss>

