<?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>article &amp;quot;Ingested log data is trimmed&amp;quot; message in Dynatrace Managed in Troubleshooting</title>
    <link>https://community.dynatrace.com/t5/Troubleshooting/quot-Ingested-log-data-is-trimmed-quot-message-in-Dynatrace/ta-p/230269</link>
    <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;P class="sc-dycYrt jwzYdG sc-kFWlue hldrCK sc-3b06fd1c-0 ivrEIu" data-testid="paragraph"&gt;If you receive a &lt;CODE class="sc-dycYrt ipJFFH sc-hTUWRQ hmrjSf" data-testid="code"&gt;Ingested log data is trimmed&lt;/CODE&gt; message, go through the following steps:&amp;nbsp;&lt;/P&gt;
&lt;DIV class="sc-6646062a-0 ivCgmd"&gt;
&lt;OL class="sc-fsvrbR jmEzKh" start="1"&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;In Cluster Management Console, go to&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Events&lt;/STRONG&gt;.&lt;/LI&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;Make sure&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Only show log events that have minimum severity level of&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;is set to&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;informational&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;or&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;warning&lt;/STRONG&gt;.&lt;/LI&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;In the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Search&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;box, search for&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE class="sc-dycYrt ipJFFH sc-hTUWRQ hmrjSf" data-testid="code"&gt;Ingested log data is trimmed&lt;/CODE&gt;.&lt;/LI&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;
&lt;P class="sc-dycYrt jwzYdG" data-testid="text"&gt;If a cluster event was created recently, check its time, affected environments, and log ingest limit.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;For each affected environment, go to&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Logs&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and set the global timeframe selector to the hour from the cluster event from the previous step.&lt;/LI&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;Inspect 1-minute intervals of log events ingest.
&lt;DIV class="sc-6646062a-0 ivCgmd"&gt;
&lt;UL class="sc-fsvrbR jmEzKh"&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;If you see that log events are trimmed to the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Maximum ingest of Log Events&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;limit set for this environment, you need to increase it.&lt;/LI&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;
&lt;P class="sc-dycYrt jwzYdG" data-testid="text"&gt;If log ingest was below the limit in subsequent intervals, your log entries will be re-ingested and should be available later, but you could consider increasing the limit to avoid a delay in data processing.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;To increase the ingest limit, in Cluster Management Console, find&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Maximum ingest of Log Events&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and edit the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Max limit&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;value for the selected environment.
&lt;DIV class="sc-6646062a-0 ivCgmd"&gt;
&lt;UL class="sc-fsvrbR jmEzKh"&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;
&lt;P class="sc-dycYrt jwzYdG" data-testid="text"&gt;We recommend that you increase the limit incrementally followed by verification of ingest volume.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;Make sure that your cluster still meets the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A class="sc-eNSrOW jIVdPj sc-68987768-0 eSCioX" title="Learn what hardware and operating system requirements need to be taken into account before installing your Dynatrace Managed cluster." href="https://docs.dynatrace.com/docs/managed-cluster/installation/dynatrace-managed-hardware-and-system-requirements#log-mon" target="_blank" rel="noopener" data-testid="link"&gt;hardware recommendations&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;for the new ingest volume.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/DIV&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
    <pubDate>Tue, 05 Dec 2023 08:20:57 GMT</pubDate>
    <dc:creator>Magda_Zarek</dc:creator>
    <dc:date>2023-12-05T08:20:57Z</dc:date>
    <item>
      <title>"Ingested log data is trimmed" message in Dynatrace Managed</title>
      <link>https://community.dynatrace.com/t5/Troubleshooting/quot-Ingested-log-data-is-trimmed-quot-message-in-Dynatrace/ta-p/230269</link>
      <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;P class="sc-dycYrt jwzYdG sc-kFWlue hldrCK sc-3b06fd1c-0 ivrEIu" data-testid="paragraph"&gt;If you receive a &lt;CODE class="sc-dycYrt ipJFFH sc-hTUWRQ hmrjSf" data-testid="code"&gt;Ingested log data is trimmed&lt;/CODE&gt; message, go through the following steps:&amp;nbsp;&lt;/P&gt;
&lt;DIV class="sc-6646062a-0 ivCgmd"&gt;
&lt;OL class="sc-fsvrbR jmEzKh" start="1"&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;In Cluster Management Console, go to&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Events&lt;/STRONG&gt;.&lt;/LI&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;Make sure&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Only show log events that have minimum severity level of&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;is set to&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;informational&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;or&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;warning&lt;/STRONG&gt;.&lt;/LI&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;In the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Search&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;box, search for&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE class="sc-dycYrt ipJFFH sc-hTUWRQ hmrjSf" data-testid="code"&gt;Ingested log data is trimmed&lt;/CODE&gt;.&lt;/LI&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;
&lt;P class="sc-dycYrt jwzYdG" data-testid="text"&gt;If a cluster event was created recently, check its time, affected environments, and log ingest limit.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;For each affected environment, go to&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Logs&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and set the global timeframe selector to the hour from the cluster event from the previous step.&lt;/LI&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;Inspect 1-minute intervals of log events ingest.
&lt;DIV class="sc-6646062a-0 ivCgmd"&gt;
&lt;UL class="sc-fsvrbR jmEzKh"&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;If you see that log events are trimmed to the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Maximum ingest of Log Events&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;limit set for this environment, you need to increase it.&lt;/LI&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;
&lt;P class="sc-dycYrt jwzYdG" data-testid="text"&gt;If log ingest was below the limit in subsequent intervals, your log entries will be re-ingested and should be available later, but you could consider increasing the limit to avoid a delay in data processing.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;To increase the ingest limit, in Cluster Management Console, find&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Maximum ingest of Log Events&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and edit the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Max limit&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;value for the selected environment.
&lt;DIV class="sc-6646062a-0 ivCgmd"&gt;
&lt;UL class="sc-fsvrbR jmEzKh"&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;
&lt;P class="sc-dycYrt jwzYdG" data-testid="text"&gt;We recommend that you increase the limit incrementally followed by verification of ingest volume.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="sc-jOnpCo cYSaOE"&gt;Make sure that your cluster still meets the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A class="sc-eNSrOW jIVdPj sc-68987768-0 eSCioX" title="Learn what hardware and operating system requirements need to be taken into account before installing your Dynatrace Managed cluster." href="https://docs.dynatrace.com/docs/managed-cluster/installation/dynatrace-managed-hardware-and-system-requirements#log-mon" target="_blank" rel="noopener" data-testid="link"&gt;hardware recommendations&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;for the new ingest volume.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/DIV&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Tue, 05 Dec 2023 08:20:57 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Troubleshooting/quot-Ingested-log-data-is-trimmed-quot-message-in-Dynatrace/ta-p/230269</guid>
      <dc:creator>Magda_Zarek</dc:creator>
      <dc:date>2023-12-05T08:20:57Z</dc:date>
    </item>
  </channel>
</rss>

