<?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 Can I route some data as syslog output to multiple destinations? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Can-I-route-some-data-as-syslog-output-to-multiple-destinations/m-p/16246#M1925</link>
    <description>&lt;P&gt;I am indexing data feeds A and B and want to forward just data from B as syslog to servers X and Y (cloning the data stream). How can I do this?&lt;/P&gt;</description>
    <pubDate>Sat, 26 Jun 2010 03:55:02 GMT</pubDate>
    <dc:creator>Dan</dc:creator>
    <dc:date>2010-06-26T03:55:02Z</dc:date>
    <item>
      <title>Can I route some data as syslog output to multiple destinations?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Can-I-route-some-data-as-syslog-output-to-multiple-destinations/m-p/16246#M1925</link>
      <description>&lt;P&gt;I am indexing data feeds A and B and want to forward just data from B as syslog to servers X and Y (cloning the data stream). How can I do this?&lt;/P&gt;</description>
      <pubDate>Sat, 26 Jun 2010 03:55:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Can-I-route-some-data-as-syslog-output-to-multiple-destinations/m-p/16246#M1925</guid>
      <dc:creator>Dan</dc:creator>
      <dc:date>2010-06-26T03:55:02Z</dc:date>
    </item>
    <item>
      <title>Re: Can I route some data as syslog output to multiple destinations?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Can-I-route-some-data-as-syslog-output-to-multiple-destinations/m-p/16247#M1926</link>
      <description>&lt;P&gt;Here is an example config that accomplishes this. I would recommend reading: &lt;A href="http://www.splunk.com/base/Documentation/latest/Admin/Configureforwarderswithoutputs.conf" rel="nofollow"&gt;http://www.splunk.com/base/Documentation/latest/Admin/Configureforwarderswithoutputs.conf&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;outputs.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[syslog]
defaultGroup=nothing
indexAndForward=true

[syslog:serverX]
server = beefysup01:514

[syslog:serverY]
server = 10.1.12.10:514
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;EM&gt;Note: By default, all events will get sent to all configured target groups. To avoid this, you need to set defaultGroup=nothing ("nothing" can be any name that is not defined as a target group). Then you manually route data to the targets using props and transforms.&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;props.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::B]
TRANSFORMS-routing=syslogRouting
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;EM&gt;Note: This is an example of why you should receive different types of network inputs on different ports. If data feeds A and B were different kinds of syslog (say router data and proxy data), and if both were received on default syslog port 514, then you would have a hard time separating A from B.&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;transforms.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[syslogRouting]
REGEX=.
DEST_KEY=_SYSLOG_ROUTING
FORMAT=serverX,serverY
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;EM&gt;Note: FORMAT is a comma separated list of target groups, which results in cloning of the data.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 26 Jun 2010 05:01:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Can-I-route-some-data-as-syslog-output-to-multiple-destinations/m-p/16247#M1926</guid>
      <dc:creator>Dan</dc:creator>
      <dc:date>2010-06-26T05:01:14Z</dc:date>
    </item>
    <item>
      <title>Re: Can I route some data as syslog output to multiple destinations?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Can-I-route-some-data-as-syslog-output-to-multiple-destinations/m-p/16248#M1927</link>
      <description>&lt;P&gt;I believe that this could be more efficiently accomplished this way, assuming feed A comes in in port 1500, and B comes in on port 1600:&lt;/P&gt;

&lt;P&gt;inputs.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[udp:1500]
_SYSLOG_ROUTING = nothing

[udp:1600]
_SYSLOG_ROUTING = serverX,serverY
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;outputs.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[syslog]
defaultGroup = none

[serverX]
server = x:1234
[serverY]
server = y:1234
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sat, 26 Jun 2010 05:33:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Can-I-route-some-data-as-syslog-output-to-multiple-destinations/m-p/16248#M1927</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2010-06-26T05:33:14Z</dc:date>
    </item>
    <item>
      <title>Re: Can I route some data as syslog output to multiple destinations?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Can-I-route-some-data-as-syslog-output-to-multiple-destinations/m-p/16249#M1928</link>
      <description>&lt;P&gt;I think you can only set _TCPOUT_ROUTING in inputs.conf&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 09:14:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Can-I-route-some-data-as-syslog-output-to-multiple-destinations/m-p/16249#M1928</guid>
      <dc:creator>Dan</dc:creator>
      <dc:date>2020-09-28T09:14:05Z</dc:date>
    </item>
  </channel>
</rss>

