<?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: Data Storage in Dynatrace Managed Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Data-storage-information/m-p/214041#M2551</link>
    <description>&lt;P&gt;Hello,&lt;BR /&gt;About Cassandra you will find here :&amp;nbsp;&lt;A href="https://www.dynatrace.com/support/help/setup-and-configuration/technology-support/dynatrace-extensions/supported-out-of-the-box/cassandra" target="_blank"&gt;Cassandra monitoring | Dynatrace Docs&lt;/A&gt;&lt;BR /&gt;About ElasticSearch&amp;nbsp; :&amp;nbsp;&lt;A href="https://www.dynatrace.com/support/help/setup-and-configuration/technology-support/dynatrace-extensions/supported-out-of-the-box/elasticsearch" target="_blank"&gt;Elasticsearch monitoring | Dynatrace Docs&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Please be aware on the following fact :&amp;nbsp;&lt;BR /&gt;There are no sync transaction store so this means ElasticSearch and Cassandra sync between nodes which can also have an overall impact on storage as well; Thus the suggestion&amp;nbsp;would be to spread this out and give each node its own storage type (a mount for cassandra, a mount for ElasticSearch and a mount for transaction storage for instance) as a minimum recommendation.&lt;EM&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;BR /&gt;&amp;nbsp;For example, where Elastic storage and Cassandra all storages are on the same disk then reserved disk space is calculated as the sum of minimum required free disk space required by the respective data contributors (plus a 10% safety margin).&lt;BR /&gt;The individual calculation is done as:&lt;BR /&gt;For Cassandra reserved disk space: Current Cassandra usage * 0.6 (enough space for cassandra to do reorganization). Consequently take care during the backup operation due to disk compaction.&amp;nbsp;&lt;EM&gt;&lt;BR /&gt;interesting post :&amp;nbsp;&lt;A href="https://community.dynatrace.com/t5/Open-Q-A/Backup-Size-Ratio-Cassandra-vs-Elasticsearch/m-p/210115" target="_blank"&gt;Solved: Re: Backup Size Ratio Cassandra vs. Elasticsearch - Dynatrace Community&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/EM&gt;More info hardware requirements :&amp;nbsp;&lt;BR /&gt;&lt;A href="https://www.dynatrace.com/support/help/managed-cluster/installation/dynatrace-managed-hardware-and-system-requirements#storage" target="_blank"&gt;Managed hardware requirements | Dynatrace Docs&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I hope that answered&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jun 2023 10:40:26 GMT</pubDate>
    <dc:creator>uros_djukic1</dc:creator>
    <dc:date>2023-06-05T10:40:26Z</dc:date>
    <item>
      <title>Data storage information</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Data-storage-information/m-p/213982#M2547</link>
      <description>&lt;P&gt;Where in documentation can I find the purpose of the Cassandra, nginx and Elasticsearch in Dynatrace Managed cluster?&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2023 13:05:54 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Data-storage-information/m-p/213982#M2547</guid>
      <dc:creator>natanael_mendes</dc:creator>
      <dc:date>2023-06-20T13:05:54Z</dc:date>
    </item>
    <item>
      <title>Re: Data Storage</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Data-storage-information/m-p/213983#M2548</link>
      <description>&lt;P&gt;Dynatrace Managed has to be considered as a packaged solution with several components.&lt;BR /&gt;&lt;BR /&gt;Cassandra stores configuration data and metrics. Elasticsearch stores RUM data and log files for Log Monitoring v2 (logs classic). NGINX servers as load balancer and routes communication to particular endpoints and between cluster nodes.&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jun 2023 22:17:42 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Data-storage-information/m-p/213983#M2548</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2023-06-03T22:17:42Z</dc:date>
    </item>
    <item>
      <title>Re: Data Storage</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Data-storage-information/m-p/213990#M2549</link>
      <description>&lt;P&gt;thanks for the answer but where in documentation i can find the purpose of cassandra and elastic?&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jun 2023 18:05:00 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Data-storage-information/m-p/213990#M2549</guid>
      <dc:creator>natanael_mendes</dc:creator>
      <dc:date>2023-06-04T18:05:00Z</dc:date>
    </item>
    <item>
      <title>Re: Data Storage</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Data-storage-information/m-p/213998#M2550</link>
      <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/30468"&gt;@natanael_mendes&lt;/a&gt;&amp;nbsp;in my previous post - it's a boxed solution, so you should not care about what data is stored in which technology as it may change between versions. Also you should not make any changes in the Cassandra or Elastic setting on the Managed node unless instructed to do so from the Dynatrace support.&lt;BR /&gt;&lt;BR /&gt;About the data - I don't think this is documented in the public docs, but you can find relevant data &lt;A href="https://community.dynatrace.com/t5/Alerting/what-are-the-different-type-of-data/td-p/122675" target="_blank"&gt;in this post&lt;/A&gt;.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jun 2023 06:23:05 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Data-storage-information/m-p/213998#M2550</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2023-06-05T06:23:05Z</dc:date>
    </item>
    <item>
      <title>Re: Data Storage</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Data-storage-information/m-p/214041#M2551</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;About Cassandra you will find here :&amp;nbsp;&lt;A href="https://www.dynatrace.com/support/help/setup-and-configuration/technology-support/dynatrace-extensions/supported-out-of-the-box/cassandra" target="_blank"&gt;Cassandra monitoring | Dynatrace Docs&lt;/A&gt;&lt;BR /&gt;About ElasticSearch&amp;nbsp; :&amp;nbsp;&lt;A href="https://www.dynatrace.com/support/help/setup-and-configuration/technology-support/dynatrace-extensions/supported-out-of-the-box/elasticsearch" target="_blank"&gt;Elasticsearch monitoring | Dynatrace Docs&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Please be aware on the following fact :&amp;nbsp;&lt;BR /&gt;There are no sync transaction store so this means ElasticSearch and Cassandra sync between nodes which can also have an overall impact on storage as well; Thus the suggestion&amp;nbsp;would be to spread this out and give each node its own storage type (a mount for cassandra, a mount for ElasticSearch and a mount for transaction storage for instance) as a minimum recommendation.&lt;EM&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;BR /&gt;&amp;nbsp;For example, where Elastic storage and Cassandra all storages are on the same disk then reserved disk space is calculated as the sum of minimum required free disk space required by the respective data contributors (plus a 10% safety margin).&lt;BR /&gt;The individual calculation is done as:&lt;BR /&gt;For Cassandra reserved disk space: Current Cassandra usage * 0.6 (enough space for cassandra to do reorganization). Consequently take care during the backup operation due to disk compaction.&amp;nbsp;&lt;EM&gt;&lt;BR /&gt;interesting post :&amp;nbsp;&lt;A href="https://community.dynatrace.com/t5/Open-Q-A/Backup-Size-Ratio-Cassandra-vs-Elasticsearch/m-p/210115" target="_blank"&gt;Solved: Re: Backup Size Ratio Cassandra vs. Elasticsearch - Dynatrace Community&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/EM&gt;More info hardware requirements :&amp;nbsp;&lt;BR /&gt;&lt;A href="https://www.dynatrace.com/support/help/managed-cluster/installation/dynatrace-managed-hardware-and-system-requirements#storage" target="_blank"&gt;Managed hardware requirements | Dynatrace Docs&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I hope that answered&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jun 2023 10:40:26 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Data-storage-information/m-p/214041#M2551</guid>
      <dc:creator>uros_djukic1</dc:creator>
      <dc:date>2023-06-05T10:40:26Z</dc:date>
    </item>
    <item>
      <title>Re: Data storage information</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Data-storage-information/m-p/233719#M3045</link>
      <description>&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do you have the info of how exactly the sync and the contribution of each nodes,&lt;/P&gt;&lt;P&gt;Lets assume that we have a set up with 6 nodes...&lt;/P&gt;&lt;P&gt;How the data is balanced and distributed, and what Dynatrace mange in case we have , 1, 2, or 3 nodes lost.&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jan 2024 09:40:17 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Data-storage-information/m-p/233719#M3045</guid>
      <dc:creator>Malaik</dc:creator>
      <dc:date>2024-01-09T09:40:17Z</dc:date>
    </item>
    <item>
      <title>Re: Data storage information</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Data-storage-information/m-p/233724#M3046</link>
      <description>&lt;P&gt;Dynatrace Managed uses a balanced distribution of data across the cluster. Data is replicated and distributed to ensure high availability and fault tolerance. If nodes are lost, Dynatrace automatically adapts to the new configuration, maintaining system operation and data access. However, some historical data (especially trace) may be lost. The number of nodes that can be lost without affecting operation depends on the cluster configuration and data replication settings.&lt;/P&gt;&lt;P&gt;Radek&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jan 2024 10:13:53 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Data-storage-information/m-p/233724#M3046</guid>
      <dc:creator>radek_jasinski</dc:creator>
      <dc:date>2024-01-09T10:13:53Z</dc:date>
    </item>
  </channel>
</rss>

