<?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: Universal Forwarder Multi-Line Event Line Breaking in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Universal-Forwarder-Multi-Line-Event-Line-Breaking/m-p/506691#M2318</link>
    <description>&lt;P&gt;Rich,&lt;/P&gt;&lt;P&gt;I did have that thought this morning but wanted to get my question in.&amp;nbsp; I will try that and see what happens.&lt;/P&gt;&lt;P&gt;I would rather split the events on the UF before indexing.&amp;nbsp; That way I do not have to restart the production Splunk instance.&lt;/P&gt;&lt;P&gt;I'll try the props.conf on the indexer and will report the outcome.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rcp&lt;/P&gt;</description>
    <pubDate>Tue, 30 Jun 2020 13:52:11 GMT</pubDate>
    <dc:creator>raynold_peterso</dc:creator>
    <dc:date>2020-06-30T13:52:11Z</dc:date>
    <item>
      <title>Universal Forwarder Multi-Line Event Line Breaking</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Universal-Forwarder-Multi-Line-Event-Line-Breaking/m-p/506679#M2315</link>
      <description>&lt;P&gt;Good morning all,&lt;/P&gt;&lt;P&gt;I have been beating my head against this issue for a week or more.&amp;nbsp; Let me give you the details.&lt;/P&gt;&lt;P&gt;We have one indexer and multiple Universal Forwarders in the field.&amp;nbsp; One of these forwarders I am running a scripted input to gather directory data for a file monitoring solution.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;input.conf:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;###### Scripted Input to monitor jpeg files
[script://.\bin\dircontents.bat]
disabled = 0
## Run once per minute
interval = 60
sourcetype = Script:dir_files
index = filewatch&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;dircontents.bat&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;@echo off
D:
cd /seed
dir /b&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The forwarder gathers this data from the script:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;24Aug2017.txt
24Jan2018.txt
28Jul2016.txt
28Jul2016.txt~
29Jan2018.txt
INCHARGE-AM-PM-AL.seedfile
INCHARGE-AM-PM-AZ.seedfile
INCHARGE-AM-PM-GA-FL.seedfile
INCHARGE-AM-PM.seedfile
MitchDRSite.list
rcp.list
TSM-seed.list&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This data is one event with Multiple lines.&amp;nbsp; I want to bread on the line feeds.&amp;nbsp; That sounds simple enough.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;props.conf&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[Script:dir_files]
SHOULD_LINEMERGE = false
LINE_BREAKER = ([\r\n]+)
MAX_EVENTS = 10000
TRUNCATE = 0&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After I deploy the configs to the UF, the data starts coming in as a single event with multiple lines.&amp;nbsp; Very frustrating!!!&lt;/P&gt;&lt;P&gt;I have tried many things, changed my regex around and I just can not find the solution.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any help would be appreciated at this time.&lt;/P&gt;&lt;P&gt;Let me know what you think&lt;/P&gt;&lt;P&gt;Rcp&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jun 2020 13:14:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Universal-Forwarder-Multi-Line-Event-Line-Breaking/m-p/506679#M2315</guid>
      <dc:creator>raynold_peterso</dc:creator>
      <dc:date>2020-06-30T13:14:54Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder Multi-Line Event Line Breaking</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Universal-Forwarder-Multi-Line-Event-Line-Breaking/m-p/506685#M2317</link>
      <description>Have you tried putting that props.conf file on the indexer?</description>
      <pubDate>Tue, 30 Jun 2020 13:34:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Universal-Forwarder-Multi-Line-Event-Line-Breaking/m-p/506685#M2317</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-06-30T13:34:18Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder Multi-Line Event Line Breaking</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Universal-Forwarder-Multi-Line-Event-Line-Breaking/m-p/506691#M2318</link>
      <description>&lt;P&gt;Rich,&lt;/P&gt;&lt;P&gt;I did have that thought this morning but wanted to get my question in.&amp;nbsp; I will try that and see what happens.&lt;/P&gt;&lt;P&gt;I would rather split the events on the UF before indexing.&amp;nbsp; That way I do not have to restart the production Splunk instance.&lt;/P&gt;&lt;P&gt;I'll try the props.conf on the indexer and will report the outcome.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rcp&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jun 2020 13:52:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Universal-Forwarder-Multi-Line-Event-Line-Breaking/m-p/506691#M2318</guid>
      <dc:creator>raynold_peterso</dc:creator>
      <dc:date>2020-06-30T13:52:11Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder Multi-Line Event Line Breaking</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Universal-Forwarder-Multi-Line-Event-Line-Breaking/m-p/506728#M2323</link>
      <description>&lt;P&gt;Well, that worked as expected.&amp;nbsp; The data broke on the line feeds at the indexer level.&lt;/P&gt;&lt;P&gt;I would still like to know if the data can be split up at the UF before sending the data.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rcp&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jun 2020 16:16:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Universal-Forwarder-Multi-Line-Event-Line-Breaking/m-p/506728#M2323</guid>
      <dc:creator>raynold_peterso</dc:creator>
      <dc:date>2020-06-30T16:16:24Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder Multi-Line Event Line Breaking</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Universal-Forwarder-Multi-Line-Event-Line-Breaking/m-p/506736#M2325</link>
      <description>UFs don't do line breaking.</description>
      <pubDate>Tue, 30 Jun 2020 16:36:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Universal-Forwarder-Multi-Line-Event-Line-Breaking/m-p/506736#M2325</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-06-30T16:36:52Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder Multi-Line Event Line Breaking</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Universal-Forwarder-Multi-Line-Event-Line-Breaking/m-p/574989#M10714</link>
      <description>&lt;P&gt;I release this is old but Universal Forwarders do perform EVENT_BREAKER properties.&amp;nbsp;&lt;BR /&gt;It was brought in for&lt;BR /&gt;1. Better load balancing.&lt;BR /&gt;2. Line break tuning would be more efficient, E.G. multiple lines of the same event would not be sent to different indexers.&lt;/P&gt;&lt;P&gt;See the props.conf.spec in the Universal forwarder for "EVENT_BREAKER" for more details.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Nov 2021 06:10:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Universal-Forwarder-Multi-Line-Event-Line-Breaking/m-p/574989#M10714</guid>
      <dc:creator>dexterpokta</dc:creator>
      <dc:date>2021-11-16T06:10:36Z</dc:date>
    </item>
  </channel>
</rss>

