<?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: How to send events from same path to different indexes depending on host using a single deployment? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-send-events-from-same-path-to-different-indexes-depending/m-p/143621#M29318</link>
    <description>&lt;P&gt;You could put the 95% into a common serverclass and only keep the 5% in separate serverclasses. That should severely reduce maintenance overhead.&lt;/P&gt;</description>
    <pubDate>Tue, 15 Jul 2014 19:34:55 GMT</pubDate>
    <dc:creator>martin_mueller</dc:creator>
    <dc:date>2014-07-15T19:34:55Z</dc:date>
    <item>
      <title>How to send events from same path to different indexes depending on host using a single deployment?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-send-events-from-same-path-to-different-indexes-depending/m-p/143618#M29315</link>
      <description>&lt;P&gt;Hello.   Here's my situation.   I am using the deployment server to push deployments to universal forwarders and would like to create a single deployment for multiple Apache servers.  For reasons I won't get into, I have a need to send events from the same path to different indexes depending on the host that they come from.&lt;/P&gt;

&lt;P&gt;So the logic of a hypothetical inputs.conf I create would be&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor:///var/weblogs/*/*.log]
 if host::host1 OR host::host2 OR host::host3, index = special_index

[monitor:///var/weblogs/*/*.log]
 if host::host4 OR host::host5 OR host::host6, index = main
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Obviously inputs.conf doesn't support this kind of syntax, but it's unclear to me how I might be able to accomplish this same thing, if at all, using just one deployment.  I already have a lot of different individual deployments with minor tweaks between them like this directing to different indexes stuff, but it's hard to maintain all those different but similar configurations.&lt;/P&gt;

&lt;P&gt;Is there a way I might change the index value via configuration for events from this path depending on the host value?&lt;/P&gt;

&lt;P&gt;Thanks very much.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2014 17:41:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-send-events-from-same-path-to-different-indexes-depending/m-p/143618#M29315</guid>
      <dc:creator>mfrost8</dc:creator>
      <dc:date>2014-07-15T17:41:52Z</dc:date>
    </item>
    <item>
      <title>Re: How to send events from same path to different indexes depending on host using a single deployment?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-send-events-from-same-path-to-different-indexes-depending/m-p/143619#M29316</link>
      <description>&lt;P&gt;You have two options.&lt;/P&gt;

&lt;P&gt;First, create two serverclasses - one for events going to main and one for events going to special_index. That's the easiest to do and most efficient to process for your machines.&lt;/P&gt;

&lt;P&gt;Second, you could set up transforms.conf rules on your indexers that decide based on an event's host whether to send an event to main or to special_index. That works, but is a bit harder to configure and adds unnecessary load to your indexers compared to just setting things in inputs.conf right away..&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2014 18:02:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-send-events-from-same-path-to-different-indexes-depending/m-p/143619#M29316</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-07-15T18:02:21Z</dc:date>
    </item>
    <item>
      <title>Re: How to send events from same path to different indexes depending on host using a single deployment?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-send-events-from-same-path-to-different-indexes-depending/m-p/143620#M29317</link>
      <description>&lt;P&gt;Thanks, Martin.&lt;/P&gt;

&lt;P&gt;That's what I was afraid of. I already have separate deployments for these different hosts which is a pain to maintain because 95% of the deployments are identical so if I make a change I have to make sure I put it in multiple places the same way.&lt;/P&gt;

&lt;P&gt;As I was writing the original message, I thought about the indexer-side transforms.conf stuff, but that's not super-clear either.  Doesn't seem like there's a great solution for this other than finding a justification for collapsing it all into the same index starting now.&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2014 18:20:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-send-events-from-same-path-to-different-indexes-depending/m-p/143620#M29317</guid>
      <dc:creator>mfrost8</dc:creator>
      <dc:date>2014-07-15T18:20:26Z</dc:date>
    </item>
    <item>
      <title>Re: How to send events from same path to different indexes depending on host using a single deployment?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-send-events-from-same-path-to-different-indexes-depending/m-p/143621#M29318</link>
      <description>&lt;P&gt;You could put the 95% into a common serverclass and only keep the 5% in separate serverclasses. That should severely reduce maintenance overhead.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2014 19:34:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-send-events-from-same-path-to-different-indexes-depending/m-p/143621#M29318</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-07-15T19:34:55Z</dc:date>
    </item>
  </channel>
</rss>

