<?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: Adding Index-time field on intermediate forwarder in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Adding-Index-time-field-on-intermediate-forwarder/m-p/124083#M33531</link>
    <description>&lt;P&gt;that did it, with no noticeable impact on CPU on the IF (was expecting some). Thanks again&lt;/P&gt;</description>
    <pubDate>Thu, 16 Jul 2015 08:15:23 GMT</pubDate>
    <dc:creator>greich</dc:creator>
    <dc:date>2015-07-16T08:15:23Z</dc:date>
    <item>
      <title>Adding Index-time field on intermediate forwarder</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Adding-Index-time-field-on-intermediate-forwarder/m-p/124079#M33527</link>
      <description>&lt;P&gt;I need to trace the data from the originating forwarder through intermediate forwarders or directly onto indexers. I am trying to add a field when the data goes through the intermediate forwarder.&lt;/P&gt;

&lt;P&gt;Configuration&lt;/P&gt;

&lt;P&gt;Data collection by Heavy Forwarders&lt;/P&gt;

&lt;P&gt;inputs.conf&lt;BR /&gt;
[default]&lt;BR /&gt;
host = shorthostname (of the HF)&lt;/P&gt;

&lt;P&gt;sending all to Intermediate Forwarders&lt;/P&gt;

&lt;P&gt;inputs.conf&lt;BR /&gt;
[default]&lt;BR /&gt;
host = shorthostname (IF)&lt;BR /&gt;
router = shorthostname (IF)&lt;/P&gt;

&lt;P&gt;props.conf&lt;BR /&gt;
[default]&lt;BR /&gt;
TRANSFORMS-router = addrouter&lt;/P&gt;

&lt;P&gt;transforms.conf&lt;BR /&gt;
[addrouter]&lt;BR /&gt;
SOURCE_KEY = router&lt;BR /&gt;
REGEX = (.*)&lt;BR /&gt;
FORMAT = router::$1&lt;BR /&gt;
WRITE_META = true&lt;/P&gt;

&lt;P&gt;[accepted_keys]&lt;BR /&gt;
DCIF_NAME = router&lt;/P&gt;

&lt;P&gt;And finally on the search head&lt;BR /&gt;
fields.conf&lt;BR /&gt;
[router]&lt;BR /&gt;
INDEXED = true&lt;/P&gt;

&lt;P&gt;It seems that:&lt;BR /&gt;
1- everything that is sourced directly on the IF (syslog and splunk logs) has the field "router"&lt;BR /&gt;
2- everything incoming on TCP from HF does not have the field "router"&lt;/P&gt;

&lt;P&gt;What I am missing to mark incoming cooked data?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 06:41:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Adding-Index-time-field-on-intermediate-forwarder/m-p/124079#M33527</guid>
      <dc:creator>greich</dc:creator>
      <dc:date>2020-09-29T06:41:55Z</dc:date>
    </item>
    <item>
      <title>Re: Adding Index-time field on intermediate forwarder</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Adding-Index-time-field-on-intermediate-forwarder/m-p/124080#M33528</link>
      <description>&lt;P&gt;I must mention that a start message:&lt;BR /&gt;
Checking conf files for problems...&lt;BR /&gt;
                Invalid key in stanza [default] in /opt/splunk/etc/system/local/inputs.conf, line 3: router  (value:  blahhost)&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jul 2015 14:55:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Adding-Index-time-field-on-intermediate-forwarder/m-p/124080#M33528</guid>
      <dc:creator>greich</dc:creator>
      <dc:date>2015-07-15T14:55:17Z</dc:date>
    </item>
    <item>
      <title>Re: Adding Index-time field on intermediate forwarder</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Adding-Index-time-field-on-intermediate-forwarder/m-p/124081#M33529</link>
      <description>&lt;P&gt;This is expected behavior. You are going to have to re-parse your cooked data:&lt;/P&gt;

&lt;P&gt;See here:&lt;BR /&gt;
&lt;A href="http://answers.splunk.com/answers/97918/reparsing-cooked-data-coming-from-a-heavy-forwarder-possible.html" target="_blank"&gt;http://answers.splunk.com/answers/97918/reparsing-cooked-data-coming-from-a-heavy-forwarder-possible.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;On your IF (which probably needs to be a HWF), do this in inputs.conf:&lt;/P&gt;

&lt;P&gt;[splunktcp]&lt;BR /&gt;
    route=has_key:_utf8:parsingQueue;has_key:_linebreaker:parsingQueue;absent_key:_utf8:parsingQueue;absent_key:_linebreaker:parsingQueue&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 06:41:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Adding-Index-time-field-on-intermediate-forwarder/m-p/124081#M33529</guid>
      <dc:creator>jacobwilkins</dc:creator>
      <dc:date>2020-09-29T06:41:41Z</dc:date>
    </item>
    <item>
      <title>Re: Adding Index-time field on intermediate forwarder</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Adding-Index-time-field-on-intermediate-forwarder/m-p/124082#M33530</link>
      <description>&lt;P&gt;Yes IF are HF. On the first instance, your solution seems to work perfectly. Will let soak, and confirm later. Thank you.&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jul 2015 15:53:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Adding-Index-time-field-on-intermediate-forwarder/m-p/124082#M33530</guid>
      <dc:creator>greich</dc:creator>
      <dc:date>2015-07-15T15:53:52Z</dc:date>
    </item>
    <item>
      <title>Re: Adding Index-time field on intermediate forwarder</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Adding-Index-time-field-on-intermediate-forwarder/m-p/124083#M33531</link>
      <description>&lt;P&gt;that did it, with no noticeable impact on CPU on the IF (was expecting some). Thanks again&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jul 2015 08:15:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Adding-Index-time-field-on-intermediate-forwarder/m-p/124083#M33531</guid>
      <dc:creator>greich</dc:creator>
      <dc:date>2015-07-16T08:15:23Z</dc:date>
    </item>
    <item>
      <title>Re: Adding Index-time field on intermediate forwarder</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Adding-Index-time-field-on-intermediate-forwarder/m-p/124084#M33532</link>
      <description>&lt;P&gt;adding the key to the .conf.spec should resolve this&lt;/P&gt;</description>
      <pubDate>Wed, 17 Feb 2016 09:55:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Adding-Index-time-field-on-intermediate-forwarder/m-p/124084#M33532</guid>
      <dc:creator>greich</dc:creator>
      <dc:date>2016-02-17T09:55:24Z</dc:date>
    </item>
  </channel>
</rss>

