<?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: Send only few events in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Send-only-few-events/m-p/384271#M21081</link>
    <description>&lt;P&gt;Yes, that would be possible if you use a Heavy Forwarder for that. The feature you are looking for is called "Event Routing"&lt;/P&gt;

&lt;P&gt;You need to configure both servers in the outputs.conf of your forwarder, one as tcpout (for the Splunk Server), and one as syslog output (for the non-splunk server)&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tcpout:splunkindexer]
disabled = false
server = ip.of.ind.exr

[syslog:syslogout]
server = ip.of.sys.log:514
type = udp
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Then you need to adjust the props.conf of the respective source or sourcetype&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[yoursourcetype]
TRANSFORMS-routing = routeAll, routeSubset
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Finally, create a transforms.conf that does the filtering and routing&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[routeAll]
REGEX=(.)
DEST_KEY=_TCP_ROUTING
FORMAT=splunkindexer

[routeSubset]
REGEX=(your_regex_to_filter)
DEST_KEY=_TCP_ROUTING
FORMAT=splunkindexer,syslogout
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Please refer to the splunk docs for details: &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Forwarding/Routeandfilterdatad#Replicate_a_subset_of_data_to_a_third-party_system"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Forwarding/Routeandfilterdatad#Replicate_a_subset_of_data_to_a_third-party_system&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 15 Feb 2019 13:42:34 GMT</pubDate>
    <dc:creator>DMohn</dc:creator>
    <dc:date>2019-02-15T13:42:34Z</dc:date>
    <item>
      <title>Send only few events</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Send-only-few-events/m-p/384270#M21080</link>
      <description>&lt;P&gt;Hello Splunk Support,&lt;/P&gt;

&lt;P&gt;we have the following problem:&lt;BR /&gt;
- We must send a log file to different receiver: &lt;BR /&gt;
-- a Splunk server and the splunk server need ALL events&lt;BR /&gt;
-- a non-splunk server, but only few events, so a whitelisting solution&lt;/P&gt;

&lt;P&gt;I found the following documentation&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/9076/how-to-configure-a-forwarder-to-filter-and-send-only-the-events-i-want.html"&gt;https://answers.splunk.com/answers/9076/how-to-configure-a-forwarder-to-filter-and-send-only-the-events-i-want.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Now my questions:&lt;BR /&gt;
- Could I combine both solution – all events to one server and few events to another server??&lt;/P&gt;</description>
      <pubDate>Fri, 15 Feb 2019 08:20:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Send-only-few-events/m-p/384270#M21080</guid>
      <dc:creator>andreas_linden</dc:creator>
      <dc:date>2019-02-15T08:20:38Z</dc:date>
    </item>
    <item>
      <title>Re: Send only few events</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Send-only-few-events/m-p/384271#M21081</link>
      <description>&lt;P&gt;Yes, that would be possible if you use a Heavy Forwarder for that. The feature you are looking for is called "Event Routing"&lt;/P&gt;

&lt;P&gt;You need to configure both servers in the outputs.conf of your forwarder, one as tcpout (for the Splunk Server), and one as syslog output (for the non-splunk server)&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tcpout:splunkindexer]
disabled = false
server = ip.of.ind.exr

[syslog:syslogout]
server = ip.of.sys.log:514
type = udp
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Then you need to adjust the props.conf of the respective source or sourcetype&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[yoursourcetype]
TRANSFORMS-routing = routeAll, routeSubset
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Finally, create a transforms.conf that does the filtering and routing&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[routeAll]
REGEX=(.)
DEST_KEY=_TCP_ROUTING
FORMAT=splunkindexer

[routeSubset]
REGEX=(your_regex_to_filter)
DEST_KEY=_TCP_ROUTING
FORMAT=splunkindexer,syslogout
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Please refer to the splunk docs for details: &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Forwarding/Routeandfilterdatad#Replicate_a_subset_of_data_to_a_third-party_system"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Forwarding/Routeandfilterdatad#Replicate_a_subset_of_data_to_a_third-party_system&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Feb 2019 13:42:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Send-only-few-events/m-p/384271#M21081</guid>
      <dc:creator>DMohn</dc:creator>
      <dc:date>2019-02-15T13:42:34Z</dc:date>
    </item>
  </channel>
</rss>

