<?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 Splunk Cloud Dropping Events in Splunk Cloud Platform</title>
    <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-Dropping-Events/m-p/681872#M2909</link>
    <description>&lt;P&gt;This is more of an advisory than a question.&amp;nbsp; I hope it helps.&lt;/P&gt;
&lt;P&gt;If you are a Splunk Cloud customer I strongly suggest you run this search to ensure that Splunk Cloud is not dropping events.&amp;nbsp; This info is not being presented in the Splunk Cloud monitoring console and is an indicator that indexed events are being dropped.&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;index=_internal host=idx* sourcetype=splunkd log_level IN(ERROR,WARN) component=SQSSmartbusInputWorker "Error parsing events from message content"
| eval bytesRemaining=trim(bytesRemaining,":")
| stats sum(bytesRemaining) as bytesNotIndexed&lt;/LI-CODE&gt;
&lt;P&gt;What these errors are telling us is that some&amp;nbsp;SQSSmartbusInputWorker process is parsing events and that there is some type of invalid field, or value in the data, in our case _subsecond.&amp;nbsp; When this process hits the invalid value, it appears to drop everything else in the stream (i.e. bytesRemaining).&amp;nbsp; So this is also to say that bytesRemaining contains events that were sent to Splunk Cloud, but not indexed.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When this error occurs,&amp;nbsp; Splunk cloud writes the failed info to an SQS DLQ in S3 which can be observed using:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;index=_internal host=idx* sourcetype=splunkd log_level IN(ERROR,WARN) component=SQSSmartbusInputWorker "Successfully sent a SQS DLQ message to S3 with location"&lt;/LI-CODE&gt;
&lt;P&gt;Curious if anyone else out there is experiencing the same issue.&amp;nbsp;&amp;nbsp;SQSSmartbusInputWorker&amp;nbsp; doesn't appear in any of the indexing documents, but does appear to be very important to the ingest process.&lt;/P&gt;</description>
    <pubDate>Mon, 25 Mar 2024 16:10:01 GMT</pubDate>
    <dc:creator>cyberbilliam</dc:creator>
    <dc:date>2024-03-25T16:10:01Z</dc:date>
    <item>
      <title>Splunk Cloud Dropping Events</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-Dropping-Events/m-p/681872#M2909</link>
      <description>&lt;P&gt;This is more of an advisory than a question.&amp;nbsp; I hope it helps.&lt;/P&gt;
&lt;P&gt;If you are a Splunk Cloud customer I strongly suggest you run this search to ensure that Splunk Cloud is not dropping events.&amp;nbsp; This info is not being presented in the Splunk Cloud monitoring console and is an indicator that indexed events are being dropped.&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;index=_internal host=idx* sourcetype=splunkd log_level IN(ERROR,WARN) component=SQSSmartbusInputWorker "Error parsing events from message content"
| eval bytesRemaining=trim(bytesRemaining,":")
| stats sum(bytesRemaining) as bytesNotIndexed&lt;/LI-CODE&gt;
&lt;P&gt;What these errors are telling us is that some&amp;nbsp;SQSSmartbusInputWorker process is parsing events and that there is some type of invalid field, or value in the data, in our case _subsecond.&amp;nbsp; When this process hits the invalid value, it appears to drop everything else in the stream (i.e. bytesRemaining).&amp;nbsp; So this is also to say that bytesRemaining contains events that were sent to Splunk Cloud, but not indexed.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When this error occurs,&amp;nbsp; Splunk cloud writes the failed info to an SQS DLQ in S3 which can be observed using:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;index=_internal host=idx* sourcetype=splunkd log_level IN(ERROR,WARN) component=SQSSmartbusInputWorker "Successfully sent a SQS DLQ message to S3 with location"&lt;/LI-CODE&gt;
&lt;P&gt;Curious if anyone else out there is experiencing the same issue.&amp;nbsp;&amp;nbsp;SQSSmartbusInputWorker&amp;nbsp; doesn't appear in any of the indexing documents, but does appear to be very important to the ingest process.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Mar 2024 16:10:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-Dropping-Events/m-p/681872#M2909</guid>
      <dc:creator>cyberbilliam</dc:creator>
      <dc:date>2024-03-25T16:10:01Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Cloud Dropping Events</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-Dropping-Events/m-p/710412#M3531</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/236403"&gt;@cyberbilliam&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Is this fixed? Need confirmation before migrating to Splunk Cloud.&lt;/P&gt;</description>
      <pubDate>Sun, 02 Feb 2025 01:31:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-Dropping-Events/m-p/710412#M3531</guid>
      <dc:creator>new_splunker</dc:creator>
      <dc:date>2025-02-02T01:31:40Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Cloud Dropping Events</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-Dropping-Events/m-p/748951#M3880</link>
      <description>&lt;P&gt;In general, it should be.&amp;nbsp; That said, make sure you don't try to send events via HEC to an undefined index in Splunk Cloud.&amp;nbsp; You will likely lose any events after the one destined for the undefined index in a given HEC batch.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jun 2025 13:41:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-Dropping-Events/m-p/748951#M3880</guid>
      <dc:creator>mike_fisher</dc:creator>
      <dc:date>2025-06-30T13:41:25Z</dc:date>
    </item>
  </channel>
</rss>

