<?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 Understanding Data Architecture in Dynatrace Managed: How is indexing handled? in Dynatrace Managed Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Understanding-Data-Architecture-in-Dynatrace-Managed-How-is/m-p/300266#M4787</link>
    <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I have a quick architectural question regarding &lt;STRONG&gt;Dynatrace Managed&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;I know that Dynatrace SaaS leverages &lt;STRONG&gt;Grail&lt;/STRONG&gt; for a schema-less/index-less architecture. However, since Dynatrace Managed traditionally runs on &lt;STRONG&gt;Elasticsearch and Cassandra&lt;/STRONG&gt;, I want to better understand how data handling works under the hood here.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;How does Dynatrace Managed achieve high-speed, flexible queries on historical data (like Traces and RUM) without the typical heavy indexing overhead and storage bloom seen in traditional index-based tools?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Are there any automated data optimization patterns or "schema-on-read" behaviors happening even within the Elastic/Cassandra layer?&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Just trying to deeply understand the underlying philosophy for our Managed deployment.&lt;/P&gt;&lt;P&gt;Thanks in advance for your insights.&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Aboud&lt;/P&gt;</description>
    <pubDate>Wed, 03 Jun 2026 10:07:18 GMT</pubDate>
    <dc:creator>Aboud1</dc:creator>
    <dc:date>2026-06-03T10:07:18Z</dc:date>
    <item>
      <title>Understanding Data Architecture in Dynatrace Managed: How is indexing handled?</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Understanding-Data-Architecture-in-Dynatrace-Managed-How-is/m-p/300266#M4787</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I have a quick architectural question regarding &lt;STRONG&gt;Dynatrace Managed&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;I know that Dynatrace SaaS leverages &lt;STRONG&gt;Grail&lt;/STRONG&gt; for a schema-less/index-less architecture. However, since Dynatrace Managed traditionally runs on &lt;STRONG&gt;Elasticsearch and Cassandra&lt;/STRONG&gt;, I want to better understand how data handling works under the hood here.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;How does Dynatrace Managed achieve high-speed, flexible queries on historical data (like Traces and RUM) without the typical heavy indexing overhead and storage bloom seen in traditional index-based tools?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Are there any automated data optimization patterns or "schema-on-read" behaviors happening even within the Elastic/Cassandra layer?&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Just trying to deeply understand the underlying philosophy for our Managed deployment.&lt;/P&gt;&lt;P&gt;Thanks in advance for your insights.&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Aboud&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jun 2026 10:07:18 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Understanding-Data-Architecture-in-Dynatrace-Managed-How-is/m-p/300266#M4787</guid>
      <dc:creator>Aboud1</dc:creator>
      <dc:date>2026-06-03T10:07:18Z</dc:date>
    </item>
  </channel>
</rss>

