<?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 Why are props not working consistently? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-props-not-working-consistently/m-p/646508#M109962</link>
    <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;I have created a props for line breaking. I have tested it using a process of Add Data and Set sourcetype and Advance option. The below props is working fine.&lt;/P&gt;
&lt;P&gt;While placing the same in HF, its working in consistently. Kindly assist on fixing the same.&lt;/P&gt;
&lt;P&gt;My props is:&lt;/P&gt;
&lt;P&gt;[ __auto__learned__ ]&lt;/P&gt;
&lt;P&gt;SHOULD_LINEMERGE=false&lt;/P&gt;
&lt;P&gt;NO_BINARY_CHECK=true&lt;/P&gt;
&lt;P&gt;TIME_FORMAT=%Y-%m-%d %H:%M:%S,%3Q&lt;/P&gt;
&lt;P&gt;MAX_TIMESTAMP_LOOKAHEAD=23&lt;/P&gt;
&lt;P&gt;LINE_BREAKER&amp;nbsp; =([\r\n]+)&lt;/P&gt;
&lt;P&gt;TRUNCATE=20000&lt;/P&gt;
&lt;P&gt;TIME_PREFIX=^\"&lt;/P&gt;</description>
    <pubDate>Mon, 12 Jun 2023 14:07:35 GMT</pubDate>
    <dc:creator>sagar_shubham23</dc:creator>
    <dc:date>2023-06-12T14:07:35Z</dc:date>
    <item>
      <title>Why are props not working consistently?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-props-not-working-consistently/m-p/646508#M109962</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;I have created a props for line breaking. I have tested it using a process of Add Data and Set sourcetype and Advance option. The below props is working fine.&lt;/P&gt;
&lt;P&gt;While placing the same in HF, its working in consistently. Kindly assist on fixing the same.&lt;/P&gt;
&lt;P&gt;My props is:&lt;/P&gt;
&lt;P&gt;[ __auto__learned__ ]&lt;/P&gt;
&lt;P&gt;SHOULD_LINEMERGE=false&lt;/P&gt;
&lt;P&gt;NO_BINARY_CHECK=true&lt;/P&gt;
&lt;P&gt;TIME_FORMAT=%Y-%m-%d %H:%M:%S,%3Q&lt;/P&gt;
&lt;P&gt;MAX_TIMESTAMP_LOOKAHEAD=23&lt;/P&gt;
&lt;P&gt;LINE_BREAKER&amp;nbsp; =([\r\n]+)&lt;/P&gt;
&lt;P&gt;TRUNCATE=20000&lt;/P&gt;
&lt;P&gt;TIME_PREFIX=^\"&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jun 2023 14:07:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-props-not-working-consistently/m-p/646508#M109962</guid>
      <dc:creator>sagar_shubham23</dc:creator>
      <dc:date>2023-06-12T14:07:35Z</dc:date>
    </item>
    <item>
      <title>Re: Props is not working consistently.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-props-not-working-consistently/m-p/646509#M109963</link>
      <description>&lt;P&gt;You're not giving us too much information &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Firstly, what do you mean by "working inconsistently"?&lt;/P&gt;&lt;P&gt;Secondly, we don't know what your events look like - please provide us with a (anonymized if needed) sample. (Put it in a code box - &amp;lt;/&amp;gt; sign on top of the edit window).&lt;/P&gt;&lt;P&gt;Thirdly, I would advise keeping a descriptive and predictable naming for your sourcetypes - __auto_learned__ can be easily overwritten since it's telling nothing about the source.&lt;/P&gt;</description>
      <pubDate>Sat, 10 Jun 2023 18:40:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-props-not-working-consistently/m-p/646509#M109963</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2023-06-10T18:40:38Z</dc:date>
    </item>
  </channel>
</rss>

