<?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: Why is my SEDCMD props.conf file not working? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178284#M35750</link>
    <description>&lt;P&gt;I have added SEDCMD  on heavy forwarder and it does not work. I have tested the settings individually using UI and it works.  &lt;/P&gt;</description>
    <pubDate>Fri, 05 Apr 2019 01:35:26 GMT</pubDate>
    <dc:creator>nawazns5038</dc:creator>
    <dc:date>2019-04-05T01:35:26Z</dc:date>
    <item>
      <title>Why is my SEDCMD props.conf file not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178266#M35732</link>
      <description>&lt;P&gt;I have created a props.conf file under &lt;CODE&gt;etc/system/local/props.conf&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;The content is&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[default]
SEDCMD-ipi2 = y/e/g/g
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I would expect that any letter &lt;CODE&gt;e&lt;/CODE&gt; would be replaced with a &lt;CODE&gt;g&lt;/CODE&gt; but it's not working.&lt;/P&gt;

&lt;P&gt;Should I activate in any way this file or something like that?&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2014 14:30:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178266#M35732</guid>
      <dc:creator>cbou</dc:creator>
      <dc:date>2014-10-31T14:30:11Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my SEDCMD props.conf file not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178267#M35733</link>
      <description>&lt;P&gt;If you just dropped the file there then you need to restart Splunk since that's an index-time setting.&lt;/P&gt;

&lt;P&gt;Once you've done that you can use this call to confirm Splunk reading that file:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;./bin/splunk cmd btool --debug props list
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 31 Oct 2014 14:55:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178267#M35733</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-10-31T14:55:28Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my SEDCMD props.conf file not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178268#M35734</link>
      <description>&lt;P&gt;I always restarted before. With your debug option I even can read &lt;CODE&gt;/opt/splunkforwarder/etc/system/local/props.conf                          SEDCMD-ipi2 = y/e/g/g&lt;/CODE&gt;. It seams that it does not appear as much as the other lines. But the letter &lt;CODE&gt;e&lt;/CODE&gt; still appears on the splunk server.&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2014 15:28:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178268#M35734</guid>
      <dc:creator>cbou</dc:creator>
      <dc:date>2014-10-31T15:28:28Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my SEDCMD props.conf file not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178269#M35735</link>
      <description>&lt;P&gt;Use this&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[default]
SEDCMD-ipi2 = s/e/g/g
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;option "y" is for strings and does't do global replacement.&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2014 16:53:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178269#M35735</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2014-10-31T16:53:26Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my SEDCMD props.conf file not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178270#M35736</link>
      <description>&lt;P&gt;The way I understand it, &lt;CODE&gt;y/e/g/&lt;/CODE&gt; shouldn't need the g flag because character substitution only makes sense globally... do try leaving off the global flag.&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2014 17:11:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178270#M35736</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-10-31T17:11:56Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my SEDCMD props.conf file not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178271#M35737</link>
      <description>&lt;P&gt;Even this does not work.&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2014 19:03:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178271#M35737</guid>
      <dc:creator>cbou</dc:creator>
      <dc:date>2014-10-31T19:03:17Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my SEDCMD props.conf file not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178272#M35738</link>
      <description>&lt;P&gt;Even with &lt;CODE&gt;y/e/g&lt;/CODE&gt; the props.conf does not work...&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2014 19:03:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178272#M35738</guid>
      <dc:creator>cbou</dc:creator>
      <dc:date>2014-10-31T19:03:37Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my SEDCMD props.conf file not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178273#M35739</link>
      <description>&lt;P&gt;You are looking at stuff indexed after setting this, right?&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2014 19:43:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178273#M35739</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-10-31T19:43:10Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my SEDCMD props.conf file not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178274#M35740</link>
      <description>&lt;P&gt;Yes, i'm refreshing the page, which produce a log with the date, so I'm sure.&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2014 20:51:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178274#M35740</guid>
      <dc:creator>cbou</dc:creator>
      <dc:date>2014-10-31T20:51:51Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my SEDCMD props.conf file not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178275#M35741</link>
      <description>&lt;P&gt;Well, something's fishy in your Splunk environment... I've just created a props.conf in system/local like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[default]
SEDCMD-ipi2 = y/e/g/
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and now get events like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;127.0.0.1 - admin [31/Oct/2014:22:02:08.023 +0100] "GET /sgrvicgsNS/admin/sgarch/sgarch/typgahgad?prgfix=indgx%3D_intgrnal&amp;amp;count=50&amp;amp;max_timg=1&amp;amp;output_modg=json HTTP/1.0" 200 73 - - - 2ms
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Looks fing to mg.&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2014 21:03:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178275#M35741</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-10-31T21:03:07Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my SEDCMD props.conf file not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178276#M35742</link>
      <description>&lt;P&gt;I even try with another server, it does not work... Our forwarder has the version 5.0.4.&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2014 21:12:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178276#M35742</guid>
      <dc:creator>cbou</dc:creator>
      <dc:date>2014-10-31T21:12:10Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my SEDCMD props.conf file not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178277#M35743</link>
      <description>&lt;P&gt;I found it! I was configuring the forwarder and not the server! &lt;CODE&gt;Note with 6.1 props.conf might have to go on the UFs. From dev: With 6.1, the structured data props.conf are happening at monitoring time therefore the props.conf has also to be on the forwarders.&lt;/CODE&gt; makes me on the right way. Thanks for the help &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2014 21:41:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178277#M35743</guid>
      <dc:creator>cbou</dc:creator>
      <dc:date>2014-10-31T21:41:33Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my SEDCMD props.conf file not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178278#M35744</link>
      <description>&lt;P&gt;Yeah, this does belong on the indexer if you're sending it from a universal forwarder. Some newer settings also require some props.conf keys to be present on the forwarder, but stuff like SEDCMD doesn't - regardless of the version.&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2014 22:08:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178278#M35744</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-10-31T22:08:30Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my SEDCMD props.conf file not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178279#M35745</link>
      <description>&lt;P&gt;From my point of view it makes more sense to anonymize data from the Forwarder and not on the server. That's why I always tried to configure the forwarder.&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2014 22:11:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178279#M35745</guid>
      <dc:creator>cbou</dc:creator>
      <dc:date>2014-10-31T22:11:14Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my SEDCMD props.conf file not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178280#M35746</link>
      <description>&lt;P&gt;You can do that, just not on a universal forwarder. Replace it with a heavy forwarder that does all the parsing, timestamping, regexreplacement, yada yada on the source machine and you're there. Then you will need this props.conf setting on the heavy forwarder.&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2014 22:14:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178280#M35746</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-10-31T22:14:39Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my SEDCMD props.conf file not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178281#M35747</link>
      <description>&lt;P&gt;Ok now I understand what universal forwarder client means. Thanks &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2014 22:24:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178281#M35747</guid>
      <dc:creator>cbou</dc:creator>
      <dc:date>2014-10-31T22:24:34Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my SEDCMD props.conf file not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178282#M35748</link>
      <description>&lt;P&gt;For reference here's a quick comparison: &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.0/Forwarding/Typesofforwarders#Forwarder_comparison"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.0/Forwarding/Typesofforwarders#Forwarder_comparison&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;"Per-Event filtering" is what you're doing here, basically.&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2014 22:33:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178282#M35748</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-10-31T22:33:02Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my SEDCMD props.conf file not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178283#M35749</link>
      <description>&lt;P&gt;Are you saying that props settings for structured data on the forwarder were interfering with props.conf settings on the indexer because the "monitoring time" for the inputs needs structured settings, but structured settings end the data parsing phase so that it cannot happen on the indexers?&lt;/P&gt;</description>
      <pubDate>Wed, 05 Aug 2015 22:26:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178283#M35749</guid>
      <dc:creator>landen99</dc:creator>
      <dc:date>2015-08-05T22:26:12Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my SEDCMD props.conf file not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178284#M35750</link>
      <description>&lt;P&gt;I have added SEDCMD  on heavy forwarder and it does not work. I have tested the settings individually using UI and it works.  &lt;/P&gt;</description>
      <pubDate>Fri, 05 Apr 2019 01:35:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-SEDCMD-props-conf-file-not-working/m-p/178284#M35750</guid>
      <dc:creator>nawazns5038</dc:creator>
      <dc:date>2019-04-05T01:35:26Z</dc:date>
    </item>
  </channel>
</rss>

