<?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: header problem in splunk reading the wrong header in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/header-problem-in-splunk-reading-the-wrong-header/m-p/200780#M187556</link>
    <description>&lt;P&gt;hi guys,&lt;/P&gt;

&lt;P&gt;i found the solution that in props.conf if i use CHECK_FOR_HEADER=TRUE  the events are extracting in the correct manner.&lt;/P&gt;

&lt;P&gt;thanx.&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 10:29:34 GMT</pubDate>
    <dc:creator>lavanyaanne</dc:creator>
    <dc:date>2020-09-29T10:29:34Z</dc:date>
    <item>
      <title>header problem in splunk reading the wrong header</title>
      <link>https://community.splunk.com/t5/Splunk-Search/header-problem-in-splunk-reading-the-wrong-header/m-p/200779#M187555</link>
      <description>&lt;P&gt;i am using perl script to pull the data from DB. The data is indexed perfectly and it's using the header that i was mentioned in the script. But after some time it's taking the one of the event as the header and it's indexing the data.  what might be the problem.&lt;BR /&gt;
here attaching the inputs and props .please help me &lt;/P&gt;

&lt;P&gt;inputs.conf &lt;BR /&gt;
[script:///opt/li/splunk/etc/apps/input/bin/actions.pl]&lt;BR /&gt;
interval = 0 */1 * * *&lt;BR /&gt;
index = _internal&lt;BR /&gt;
sourcetype = actions&lt;BR /&gt;
source = actions.pl&lt;BR /&gt;
disabled = false&lt;/P&gt;

&lt;P&gt;[batch:///opt/li/splunk/etc/apps/input/bin/actions_data.psv*]&lt;BR /&gt;
index = sample&lt;BR /&gt;
sourcetype = actions&lt;BR /&gt;
move_policy = sinkhole&lt;BR /&gt;
disabled = false&lt;BR /&gt;
crcSalt= &lt;/P&gt;

&lt;P&gt;props.conf&lt;/P&gt;

&lt;P&gt;[actions]&lt;BR /&gt;
SHOULD_LINEMERGE=false&lt;BR /&gt;
INDEXED_EXTRACTIONS=PSV&lt;BR /&gt;
NO_BINARY_CHECK=true&lt;BR /&gt;
DATETIME_CONFIG=NONE&lt;BR /&gt;
CHARSET=auto&lt;BR /&gt;
disabled=false&lt;BR /&gt;
category=sample&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 10:26:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/header-problem-in-splunk-reading-the-wrong-header/m-p/200779#M187555</guid>
      <dc:creator>lavanyaanne</dc:creator>
      <dc:date>2020-09-29T10:26:44Z</dc:date>
    </item>
    <item>
      <title>Re: header problem in splunk reading the wrong header</title>
      <link>https://community.splunk.com/t5/Splunk-Search/header-problem-in-splunk-reading-the-wrong-header/m-p/200780#M187556</link>
      <description>&lt;P&gt;hi guys,&lt;/P&gt;

&lt;P&gt;i found the solution that in props.conf if i use CHECK_FOR_HEADER=TRUE  the events are extracting in the correct manner.&lt;/P&gt;

&lt;P&gt;thanx.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 10:29:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/header-problem-in-splunk-reading-the-wrong-header/m-p/200780#M187556</guid>
      <dc:creator>lavanyaanne</dc:creator>
      <dc:date>2020-09-29T10:29:34Z</dc:date>
    </item>
    <item>
      <title>Re: header problem in splunk reading the wrong header</title>
      <link>https://community.splunk.com/t5/Splunk-Search/header-problem-in-splunk-reading-the-wrong-header/m-p/200781#M187557</link>
      <description>&lt;P&gt;Change from &lt;CODE&gt;batch&lt;/CODE&gt; to &lt;CODE&gt;monitor&lt;/CODE&gt; so that the original source file is preserved (this step is not necessary if you have access to the original file through some other means) and then check the &lt;CODE&gt;source&lt;/CODE&gt; field for the event that contains the header.  Once you know the name of the offending file, go back to it and examine it.  I believe you will find &lt;EM&gt;something&lt;/EM&gt; in that file that is different from all the other files.  There might be a blank line as the first line or some other unexpected  characters or formatting.  Eliminate the source of this and that will fix your problem.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Aug 2016 13:56:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/header-problem-in-splunk-reading-the-wrong-header/m-p/200781#M187557</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2016-08-01T13:56:23Z</dc:date>
    </item>
  </channel>
</rss>

