<?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: Splunk stream in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-stream/m-p/669963#M17934</link>
    <description>&lt;P&gt;&lt;SPAN&gt;now in props.conf&lt;BR /&gt;[stream:ip]&lt;BR /&gt;TRUNCATE = 100000&lt;BR /&gt;I will change to 0, I will check, I will return with the answer&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 28 Nov 2023 05:53:29 GMT</pubDate>
    <dc:creator>Vadim_Peskov</dc:creator>
    <dc:date>2023-11-28T05:53:29Z</dc:date>
    <item>
      <title>Splunk stream</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-stream/m-p/669866#M17930</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi!&lt;BR /&gt;We use Splunk Stream 7.3.0. When receiving an event in a log longer than 1000000 characters, Splunk cuts it. Event in json format. Tell me what settings should be applied in Splunk Stream so that Splunk parses the data correctly.&lt;BR /&gt;Thanks!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 27 Nov 2023 15:20:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-stream/m-p/669866#M17930</guid>
      <dc:creator>Vadim_Peskov</dc:creator>
      <dc:date>2023-11-27T15:20:11Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk stream</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-stream/m-p/669906#M17931</link>
      <description>&lt;P&gt;IIRC Splunk Stream doesn't have truncation settings and this ends up being caught by the truncation settings for your sourcetype within props.conf.&amp;nbsp; Can you share what your stanza is for your sourcetype?&amp;nbsp; Is TRUNCATE=1000000?&amp;nbsp; You might need to change to TRUNCATE=0 to force Splunk to include all of the event.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Nov 2023 17:45:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-stream/m-p/669906#M17931</guid>
      <dc:creator>_JP</dc:creator>
      <dc:date>2023-11-27T17:45:57Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk stream</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-stream/m-p/669963#M17934</link>
      <description>&lt;P&gt;&lt;SPAN&gt;now in props.conf&lt;BR /&gt;[stream:ip]&lt;BR /&gt;TRUNCATE = 100000&lt;BR /&gt;I will change to 0, I will check, I will return with the answer&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2023 05:53:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-stream/m-p/669963#M17934</guid>
      <dc:creator>Vadim_Peskov</dc:creator>
      <dc:date>2023-11-28T05:53:29Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk stream</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-stream/m-p/670027#M17943</link>
      <description>&lt;LI-CODE lang="markup"&gt;[stream:ip]
TRUNCATE = 0&lt;/LI-CODE&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;did not help.&lt;BR /&gt;Any other suggestions?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2023 15:02:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-stream/m-p/670027#M17943</guid>
      <dc:creator>Vadim_Peskov</dc:creator>
      <dc:date>2023-11-28T15:02:33Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk stream</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-stream/m-p/670234#M17952</link>
      <description>&lt;P&gt;Did you see any change in the data being ingested when you made the TRUNCATE value change?&amp;nbsp; Also, if you change it to something specific to test it, like 10237.&amp;nbsp; Does that limit it to 10237 bytes?&amp;nbsp; This is mainly just to see if this particular TRUNCATE setting is what is limiting your data, and maybe we can help rule it out as the culprit so we know to dig further.&lt;/P&gt;</description>
      <pubDate>Wed, 29 Nov 2023 20:52:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-stream/m-p/670234#M17952</guid>
      <dc:creator>_JP</dc:creator>
      <dc:date>2023-11-29T20:52:29Z</dc:date>
    </item>
  </channel>
</rss>

