<?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: Transform to replace index does not work for two hosts in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Transform-to-replace-index-does-not-work-for-two-hosts/m-p/338474#M62462</link>
    <description>&lt;P&gt;do you have those setting pushed to your search head and cm as well?  I believe that parsing will happen at the first full Splunk Enterprise instance along the way, which would be the servers themselves.&lt;/P&gt;</description>
    <pubDate>Thu, 14 Sep 2017 15:28:15 GMT</pubDate>
    <dc:creator>maciep</dc:creator>
    <dc:date>2017-09-14T15:28:15Z</dc:date>
    <item>
      <title>Transform to replace index does not work for two hosts</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Transform-to-replace-index-does-not-work-for-two-hosts/m-p/338473#M62461</link>
      <description>&lt;P&gt;Due to certain reasons, we have a number of destination indexes that need to be rewritten before indexing. Basically a partner of ours is using the name fubar_company, while we use another. We have a number of rules in &lt;CODE&gt;transforms.conf&lt;/CODE&gt; to rewrite. The failing example is below. The others are very similar.&lt;/P&gt;

&lt;P&gt;This works for the entire infrastructure, except two Splunk servers, one search head and one cluster master. Both of them forward to the indexer cluster, with &lt;CODE&gt;indexAndForward = false&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;For a while, we received alerts for events being forwarded to a non-existing index. So I created the index and can see the events in &lt;CODE&gt;index=os&lt;/CODE&gt; from both hosts. The &lt;CODE&gt;splunk_server&lt;/CODE&gt; field reveals that the events end up in the correct indexers, but not index.&lt;/P&gt;

&lt;P&gt;We're using Splunk 6.2.1. The files are distributed to the indexers through the cluster master.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;props.conf:
[default]
TRANSFORMS-changeindex=redirIdxLinux # There are more transforms here, but this is the failing one

transforms.conf:
[redirIdxLinux]
REGEX = linux_company
SOURCE_KEY = _MetaData:Index
DEST_KEY = _MetaData:Index
FORMAT = os
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 14 Sep 2017 10:00:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Transform-to-replace-index-does-not-work-for-two-hosts/m-p/338473#M62461</guid>
      <dc:creator>echalex</dc:creator>
      <dc:date>2017-09-14T10:00:01Z</dc:date>
    </item>
    <item>
      <title>Re: Transform to replace index does not work for two hosts</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Transform-to-replace-index-does-not-work-for-two-hosts/m-p/338474#M62462</link>
      <description>&lt;P&gt;do you have those setting pushed to your search head and cm as well?  I believe that parsing will happen at the first full Splunk Enterprise instance along the way, which would be the servers themselves.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Sep 2017 15:28:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Transform-to-replace-index-does-not-work-for-two-hosts/m-p/338474#M62462</guid>
      <dc:creator>maciep</dc:creator>
      <dc:date>2017-09-14T15:28:15Z</dc:date>
    </item>
    <item>
      <title>Re: Transform to replace index does not work for two hosts</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Transform-to-replace-index-does-not-work-for-two-hosts/m-p/338475#M62463</link>
      <description>&lt;P&gt;Yep, you're quite right. Actually, the thought occurred to me, so I copied the files to the relevant servers and did an &lt;CODE&gt;|extract reload=T&lt;/CODE&gt; as per the documentation. However, it seems this doesn't take effect without a full restart. It works as expected after a restart.&lt;BR /&gt;
Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 18 Sep 2017 12:02:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Transform-to-replace-index-does-not-work-for-two-hosts/m-p/338475#M62463</guid>
      <dc:creator>echalex</dc:creator>
      <dc:date>2017-09-18T12:02:22Z</dc:date>
    </item>
    <item>
      <title>Re: Transform to replace index does not work for two hosts</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Transform-to-replace-index-does-not-work-for-two-hosts/m-p/338476#M62464</link>
      <description>&lt;P&gt;I believe the "|extract reload=T" was deprecated. Do you have admin capabilities on your splunk servers? You can go to :/debug/refresh to reload the transforms and props without a full restart.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Sep 2017 14:44:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Transform-to-replace-index-does-not-work-for-two-hosts/m-p/338476#M62464</guid>
      <dc:creator>jluo_splunk</dc:creator>
      <dc:date>2017-09-18T14:44:34Z</dc:date>
    </item>
  </channel>
</rss>

