<?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: where to add my props.conf for new sourcetype - created using preview in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/where-to-add-my-props-conf-for-new-sourcetype-created-using/m-p/366692#M92943</link>
    <description>&lt;P&gt;Hello @Skins,&lt;BR /&gt;
There are couple questions here, I will try to address one by one&lt;BR /&gt;
You will probably want to push inputs.conf to monitor a file and not props.conf,&lt;BR /&gt;
this is a great wiki page that explains where conf files go:&lt;BR /&gt;
&lt;A href="https://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings%3F"&gt;https://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings%3F&lt;/A&gt;&lt;BR /&gt;
to automate this process across forwarder (and other splunk instances) you can use one of your splunk instances as a Deployment Server. According to your architecture description, your Search Head is the best candidate.&lt;BR /&gt;
here is docs on how to configure deployment server and deployment clients (pay attention that Indexers can be clients too!):&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.6.0/Updating/Configuredeploymentclients"&gt;http://docs.splunk.com/Documentation/Splunk/6.6.0/Updating/Configuredeploymentclients&lt;/A&gt;&lt;BR /&gt;
now you can build small apps that will carry configurations such as inputs, outputs, props and more!&lt;BR /&gt;
create serverclasses and assign clients and apps to groups, now you can control your Indexers configuration and forwarders configurations from one single machine.&lt;/P&gt;

&lt;P&gt;Let us know if it worked well.&lt;/P&gt;

&lt;P&gt;hope it helps&lt;/P&gt;</description>
    <pubDate>Tue, 09 May 2017 01:09:42 GMT</pubDate>
    <dc:creator>adonio</dc:creator>
    <dc:date>2017-05-09T01:09:42Z</dc:date>
    <item>
      <title>where to add my props.conf for new sourcetype - created using preview</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/where-to-add-my-props-conf-for-new-sourcetype-created-using/m-p/366691#M92942</link>
      <description>&lt;P&gt;I want to push out a props .conf file to monitor a file which resides on two machines with forwarders deployed.&lt;/P&gt;

&lt;P&gt;my env consists of 1  x sh  , 2 x indexer (not clustered) 2 x ufs&lt;/P&gt;

&lt;P&gt;So far i have used the manual file upload method to create a new sourcetype and used the preview window to separate and timestamp my events how i want.&lt;/P&gt;

&lt;P&gt;Now i'm unclear best practice to deploy these to the indexers and where they should reside ? should they also be added to my deployment apps directory and deployed to the forwarders ?&lt;/P&gt;

&lt;P&gt;gratzi&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2017 04:03:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/where-to-add-my-props-conf-for-new-sourcetype-created-using/m-p/366691#M92942</guid>
      <dc:creator>Skins</dc:creator>
      <dc:date>2017-05-08T04:03:16Z</dc:date>
    </item>
    <item>
      <title>Re: where to add my props.conf for new sourcetype - created using preview</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/where-to-add-my-props-conf-for-new-sourcetype-created-using/m-p/366692#M92943</link>
      <description>&lt;P&gt;Hello @Skins,&lt;BR /&gt;
There are couple questions here, I will try to address one by one&lt;BR /&gt;
You will probably want to push inputs.conf to monitor a file and not props.conf,&lt;BR /&gt;
this is a great wiki page that explains where conf files go:&lt;BR /&gt;
&lt;A href="https://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings%3F"&gt;https://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings%3F&lt;/A&gt;&lt;BR /&gt;
to automate this process across forwarder (and other splunk instances) you can use one of your splunk instances as a Deployment Server. According to your architecture description, your Search Head is the best candidate.&lt;BR /&gt;
here is docs on how to configure deployment server and deployment clients (pay attention that Indexers can be clients too!):&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.6.0/Updating/Configuredeploymentclients"&gt;http://docs.splunk.com/Documentation/Splunk/6.6.0/Updating/Configuredeploymentclients&lt;/A&gt;&lt;BR /&gt;
now you can build small apps that will carry configurations such as inputs, outputs, props and more!&lt;BR /&gt;
create serverclasses and assign clients and apps to groups, now you can control your Indexers configuration and forwarders configurations from one single machine.&lt;/P&gt;

&lt;P&gt;Let us know if it worked well.&lt;/P&gt;

&lt;P&gt;hope it helps&lt;/P&gt;</description>
      <pubDate>Tue, 09 May 2017 01:09:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/where-to-add-my-props-conf-for-new-sourcetype-created-using/m-p/366692#M92943</guid>
      <dc:creator>adonio</dc:creator>
      <dc:date>2017-05-09T01:09:42Z</dc:date>
    </item>
    <item>
      <title>Re: where to add my props.conf for new sourcetype - created using preview</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/where-to-add-my-props-conf-for-new-sourcetype-created-using/m-p/366693#M92944</link>
      <description>&lt;P&gt;That was an error in my original post - i meant the inputs.conf for the file monitoring.&lt;/P&gt;

&lt;P&gt;I didnt however think of using the DS to deploy to the indexers as well as the UF's &lt;/P&gt;

&lt;P&gt;gratzi&lt;/P&gt;</description>
      <pubDate>Tue, 09 May 2017 04:07:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/where-to-add-my-props-conf-for-new-sourcetype-created-using/m-p/366693#M92944</guid>
      <dc:creator>Skins</dc:creator>
      <dc:date>2017-05-09T04:07:19Z</dc:date>
    </item>
  </channel>
</rss>

