<?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: Tag data on universal forwarder in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Tag-data-on-universal-forwarder/m-p/111444#M1131</link>
    <description>&lt;P&gt;On your forwarder&lt;/P&gt;

&lt;P&gt;inputs.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor://your stuff to monitor]
sourcetype = blah
index = bleh
+ other inputs settings
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Just make sure that the index &lt;CODE&gt;bleh&lt;/CODE&gt; exists in your indexer before you start sending events.&lt;/P&gt;

&lt;P&gt;/K&lt;/P&gt;</description>
    <pubDate>Wed, 02 Apr 2014 13:12:50 GMT</pubDate>
    <dc:creator>kristian_kolb</dc:creator>
    <dc:date>2014-04-02T13:12:50Z</dc:date>
    <item>
      <title>Tag data on universal forwarder</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Tag-data-on-universal-forwarder/m-p/111439#M1126</link>
      <description>&lt;P&gt;Hi! &lt;/P&gt;

&lt;P&gt;We are migrating from storm to self hosted splunk. &lt;/P&gt;

&lt;P&gt;In storm there are projects which are a nice addition to splunk capabilities in Enterprise all te forwarded data goes to the same bag. &lt;/P&gt;

&lt;P&gt;If we forward for example "access.log"s from different machines which serve different projects we cuold limite search and report by hosts but this is inneficient.&lt;/P&gt;

&lt;P&gt;Is there a way to setup forwarders to add a field which tell which project that lines come from ?&lt;/P&gt;

&lt;P&gt;EDIT:&lt;/P&gt;

&lt;P&gt;After some click'n'learn i managed to create several indexes, an several receivers. But i cannot fin the way to setup a different index per receiver por. Any data sent by the universal forwarder to any receiver goes to the main index in the splunk server&lt;/P&gt;</description>
      <pubDate>Fri, 28 Mar 2014 14:03:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Tag-data-on-universal-forwarder/m-p/111439#M1126</guid>
      <dc:creator>splunkprimeriti</dc:creator>
      <dc:date>2014-03-28T14:03:28Z</dc:date>
    </item>
    <item>
      <title>Re: Tag data on universal forwarder</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Tag-data-on-universal-forwarder/m-p/111440#M1127</link>
      <description>&lt;P&gt;Are you possibly looking for separate indexes per "project"? Those come with role-based permissions out of the box.&lt;/P&gt;</description>
      <pubDate>Fri, 28 Mar 2014 17:38:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Tag-data-on-universal-forwarder/m-p/111440#M1127</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-03-28T17:38:28Z</dc:date>
    </item>
    <item>
      <title>Re: Tag data on universal forwarder</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Tag-data-on-universal-forwarder/m-p/111441#M1128</link>
      <description>&lt;P&gt;@martin_muller perhaps. I'm  n00b with the enterprisei flavor of splunk. We have one license for three related projects and want to do searches only on one of 'em at a time. I was loking for a way to do "* project=foobar" But if is there another way to achieve it will suffice&lt;/P&gt;</description>
      <pubDate>Mon, 31 Mar 2014 13:57:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Tag-data-on-universal-forwarder/m-p/111441#M1128</guid>
      <dc:creator>splunkprimeriti</dc:creator>
      <dc:date>2014-03-31T13:57:16Z</dc:date>
    </item>
    <item>
      <title>Re: Tag data on universal forwarder</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Tag-data-on-universal-forwarder/m-p/111442#M1129</link>
      <description>&lt;P&gt;hi @martin_mueller seems that you are right I need separate indexes per project, but I can not achieve it.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2014 09:48:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Tag-data-on-universal-forwarder/m-p/111442#M1129</guid>
      <dc:creator>splunkprimeriti</dc:creator>
      <dc:date>2014-04-02T09:48:14Z</dc:date>
    </item>
    <item>
      <title>Re: Tag data on universal forwarder</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Tag-data-on-universal-forwarder/m-p/111443#M1130</link>
      <description>&lt;P&gt;How so?&lt;/P&gt;

&lt;P&gt;You can define new indexes in indexes.conf (or through the UI) on your indexer(s), and define the &lt;CODE&gt;index&lt;/CODE&gt; key in inputs.conf on your forwarders.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2014 09:52:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Tag-data-on-universal-forwarder/m-p/111443#M1130</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-04-02T09:52:01Z</dc:date>
    </item>
    <item>
      <title>Re: Tag data on universal forwarder</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Tag-data-on-universal-forwarder/m-p/111444#M1131</link>
      <description>&lt;P&gt;On your forwarder&lt;/P&gt;

&lt;P&gt;inputs.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor://your stuff to monitor]
sourcetype = blah
index = bleh
+ other inputs settings
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Just make sure that the index &lt;CODE&gt;bleh&lt;/CODE&gt; exists in your indexer before you start sending events.&lt;/P&gt;

&lt;P&gt;/K&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2014 13:12:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Tag-data-on-universal-forwarder/m-p/111444#M1131</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2014-04-02T13:12:50Z</dc:date>
    </item>
  </channel>
</rss>

