<?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: The meaning of each type of stored data  in Dynatrace Managed. in Dynatrace Managed Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/The-meaning-of-each-type-of-stored-data-in-Dynatrace-Managed/m-p/121037#M657</link>
    <description>&lt;P&gt;In a nutshell, service code level refers to your PurePath data, while service request level refers to dynamic requests. Both adds up to the transaction storage. So the longer you set the retention period for both (or either one), the bigger your transaction storage will be. More details see: &lt;A href="https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/capabilities/data-retention-periods/"&gt;https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/capabilities/data-retention-periods/&lt;/A&gt; &lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 18 Jul 2019 15:46:34 GMT</pubDate>
    <dc:creator>Christopher_Cha</dc:creator>
    <dc:date>2019-07-18T15:46:34Z</dc:date>
    <item>
      <title>The meaning of each type of stored data in Dynatrace Managed</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/The-meaning-of-each-type-of-stored-data-in-Dynatrace-Managed/m-p/121036#M656</link>
      <description>&lt;P&gt;In this screenshot of mine, while those that highlighted by yellow marker are pretty self-explanatory from its name, I find that those pointed by the red arrow aren't.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can anyone help me to clarify what are they actually and what's the difference?&lt;/P&gt;
&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/21357-types-of-data.png" border="0" /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Wai Keat&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Apr 2023 12:41:35 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/The-meaning-of-each-type-of-stored-data-in-Dynatrace-Managed/m-p/121036#M656</guid>
      <dc:creator>waikeat_chan</dc:creator>
      <dc:date>2023-04-11T12:41:35Z</dc:date>
    </item>
    <item>
      <title>Re: The meaning of each type of stored data  in Dynatrace Managed.</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/The-meaning-of-each-type-of-stored-data-in-Dynatrace-Managed/m-p/121037#M657</link>
      <description>&lt;P&gt;In a nutshell, service code level refers to your PurePath data, while service request level refers to dynamic requests. Both adds up to the transaction storage. So the longer you set the retention period for both (or either one), the bigger your transaction storage will be. More details see: &lt;A href="https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/capabilities/data-retention-periods/"&gt;https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/capabilities/data-retention-periods/&lt;/A&gt; &lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 18 Jul 2019 15:46:34 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/The-meaning-of-each-type-of-stored-data-in-Dynatrace-Managed/m-p/121037#M657</guid>
      <dc:creator>Christopher_Cha</dc:creator>
      <dc:date>2019-07-18T15:46:34Z</dc:date>
    </item>
  </channel>
</rss>

