<?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: Setting &amp;quot;no_priority_stripping = true&amp;quot; in inputs.conf does not line break my events correctly. How to edit my configurations? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Setting-quot-no-priority-stripping-true-quot-in-inputs-conf-does/m-p/362659#M66115</link>
    <description>&lt;P&gt;According to inputs.conf.spec (&lt;A href="https://docs.splunk.com/Documentation/Splunk/6.6.2/Admin/Inputsconf" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/6.6.2/Admin/Inputsconf&lt;/A&gt;) if no_priority_stripping is set to true it causes instance to NOT strip the  syslog field from received events. However, for breaking events correctly try creating a new sourcetype in your props.conf file as such:&lt;/P&gt;

&lt;P&gt;[new_source_type]&lt;BR /&gt;
MAX_TIMESTAMP_LOOKAHEAD = 20&lt;BR /&gt;
TIME_FORMAT = %b %d %H:%M:%S&lt;BR /&gt;
TIME_PREFIX = &amp;lt;\d+&amp;gt;&lt;BR /&gt;
LINE_BREAKER = ^&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;BR /&gt;
TRUNCATE = 5000&lt;/P&gt;

&lt;P&gt;where:&lt;/P&gt;

&lt;P&gt;MAX_TIMESTAMP_LOOKAHEAD, TIME_PREFIX, TIME_FORMAT and SHOULD_LINEMERGE controls line breaking. Note TRUNCATE is thrown in for best practice purpose only. &lt;/P&gt;

&lt;P&gt;Then inside your inputs.conf add this statement underneath the stanza for your input:&lt;/P&gt;

&lt;P&gt;sourcetype=new_source_type&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 14:55:34 GMT</pubDate>
    <dc:creator>mtolbert_kgi</dc:creator>
    <dc:date>2020-09-29T14:55:34Z</dc:date>
    <item>
      <title>Setting "no_priority_stripping = true" in inputs.conf does not line break my events correctly. How to edit my configurations?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Setting-quot-no-priority-stripping-true-quot-in-inputs-conf-does/m-p/362657#M66113</link>
      <description>&lt;P&gt;Hi. I need to add &lt;STRONG&gt;no_priority_stripping = true&lt;/STRONG&gt; to my UDP syslog input so that I can create a lookup for the facility and priority fields. But when I do this, line breaking doesn't work properly. What I'd like to do is &lt;STRONG&gt;LINE_BREAKER = (&amp;lt;\d+&amp;gt;)&lt;/STRONG&gt;, but of course, this strips out the characters that I need for the lookup. How do I configure this input to break on that regex, but retain those characters in the event?&lt;/P&gt;

&lt;P&gt;Here are some sample events:&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;&amp;lt;85&amp;gt;Mar 21 13:16:22 C220-FCH1922V34X AUDIT[17179]: Login success (user:iseadmin, ip:192.168.10.10, service:sshd)&lt;/CODE&gt;&lt;BR /&gt;
&lt;CODE&gt;&amp;lt;85&amp;gt;Mar 21 13:16:22 C220-FCH1922V34X AUDIT[17179]: Session open (user:iseadmin, ip:192.168.10.10, id:63, type:CLI)&lt;/CODE&gt;&lt;BR /&gt;
&lt;CODE&gt;&amp;lt;85&amp;gt;Mar 21 13:16:53 C220-FCH1922V34X AUDIT[17180]: Session close (user:iseadmin, ip:192.168.10.10, id:63, type:CLI)&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;My goal is to lookup for the value &lt;STRONG&gt;85&lt;/STRONG&gt; and return two new fields. And this will work, if I can get the lines to break as I described above:&lt;BR /&gt;
&lt;STRONG&gt;syslog_facility=authpriv&lt;/STRONG&gt;&lt;BR /&gt;
&lt;STRONG&gt;syslog_severity=notice&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 13:16:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Setting-quot-no-priority-stripping-true-quot-in-inputs-conf-does/m-p/362657#M66113</guid>
      <dc:creator>_smp_</dc:creator>
      <dc:date>2020-09-29T13:16:52Z</dc:date>
    </item>
    <item>
      <title>Re: Setting "no_priority_stripping = true" in inputs.conf does not line break my events correctly. How to edit my configurations?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Setting-quot-no-priority-stripping-true-quot-in-inputs-conf-does/m-p/362658#M66114</link>
      <description>&lt;P&gt;You really need to show sample events.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Mar 2017 14:33:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Setting-quot-no-priority-stripping-true-quot-in-inputs-conf-does/m-p/362658#M66114</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-03-21T14:33:13Z</dc:date>
    </item>
    <item>
      <title>Re: Setting "no_priority_stripping = true" in inputs.conf does not line break my events correctly. How to edit my configurations?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Setting-quot-no-priority-stripping-true-quot-in-inputs-conf-does/m-p/362659#M66115</link>
      <description>&lt;P&gt;According to inputs.conf.spec (&lt;A href="https://docs.splunk.com/Documentation/Splunk/6.6.2/Admin/Inputsconf" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/6.6.2/Admin/Inputsconf&lt;/A&gt;) if no_priority_stripping is set to true it causes instance to NOT strip the  syslog field from received events. However, for breaking events correctly try creating a new sourcetype in your props.conf file as such:&lt;/P&gt;

&lt;P&gt;[new_source_type]&lt;BR /&gt;
MAX_TIMESTAMP_LOOKAHEAD = 20&lt;BR /&gt;
TIME_FORMAT = %b %d %H:%M:%S&lt;BR /&gt;
TIME_PREFIX = &amp;lt;\d+&amp;gt;&lt;BR /&gt;
LINE_BREAKER = ^&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;BR /&gt;
TRUNCATE = 5000&lt;/P&gt;

&lt;P&gt;where:&lt;/P&gt;

&lt;P&gt;MAX_TIMESTAMP_LOOKAHEAD, TIME_PREFIX, TIME_FORMAT and SHOULD_LINEMERGE controls line breaking. Note TRUNCATE is thrown in for best practice purpose only. &lt;/P&gt;

&lt;P&gt;Then inside your inputs.conf add this statement underneath the stanza for your input:&lt;/P&gt;

&lt;P&gt;sourcetype=new_source_type&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 14:55:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Setting-quot-no-priority-stripping-true-quot-in-inputs-conf-does/m-p/362659#M66115</guid>
      <dc:creator>mtolbert_kgi</dc:creator>
      <dc:date>2020-09-29T14:55:34Z</dc:date>
    </item>
  </channel>
</rss>

