<?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 splunk tcp output format... in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/splunk-tcp-output-format/m-p/75775#M15464</link>
    <description>&lt;P&gt;if I wanted to write a receiver for splunk data (i.e. have my index server(s) forward data via tcpout in the outputs.conf), is the format for splunk2splunk traffic published anywhere?&lt;/P&gt;

&lt;P&gt;I know it seems like an obscure need, but nonetheless, I've got it. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Thanks
Steve&lt;/P&gt;</description>
    <pubDate>Sat, 23 Oct 2010 00:41:23 GMT</pubDate>
    <dc:creator>Steve_Litras</dc:creator>
    <dc:date>2010-10-23T00:41:23Z</dc:date>
    <item>
      <title>splunk tcp output format...</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/splunk-tcp-output-format/m-p/75775#M15464</link>
      <description>&lt;P&gt;if I wanted to write a receiver for splunk data (i.e. have my index server(s) forward data via tcpout in the outputs.conf), is the format for splunk2splunk traffic published anywhere?&lt;/P&gt;

&lt;P&gt;I know it seems like an obscure need, but nonetheless, I've got it. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Thanks
Steve&lt;/P&gt;</description>
      <pubDate>Sat, 23 Oct 2010 00:41:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/splunk-tcp-output-format/m-p/75775#M15464</guid>
      <dc:creator>Steve_Litras</dc:creator>
      <dc:date>2010-10-23T00:41:23Z</dc:date>
    </item>
    <item>
      <title>Re: splunk tcp output format...</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/splunk-tcp-output-format/m-p/75776#M15465</link>
      <description>&lt;P&gt;Why not just sending out syslog? Consuming this should be quite easy.&lt;/P&gt;</description>
      <pubDate>Sat, 23 Oct 2010 00:58:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/splunk-tcp-output-format/m-p/75776#M15465</guid>
      <dc:creator>ziegfried</dc:creator>
      <dc:date>2010-10-23T00:58:07Z</dc:date>
    </item>
    <item>
      <title>Re: splunk tcp output format...</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/splunk-tcp-output-format/m-p/75777#M15466</link>
      <description>&lt;P&gt;The problem with the syslog output is that it just dumps the raw event, no metadata. I need some of the metadata from the cooked event stream.&lt;/P&gt;</description>
      <pubDate>Sat, 23 Oct 2010 01:37:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/splunk-tcp-output-format/m-p/75777#M15466</guid>
      <dc:creator>Steve_Litras</dc:creator>
      <dc:date>2010-10-23T01:37:30Z</dc:date>
    </item>
    <item>
      <title>Re: splunk tcp output format...</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/splunk-tcp-output-format/m-p/75778#M15467</link>
      <description>&lt;P&gt;Maybe it would be easier to use a script that performs a constant realtime search on the events your're interested in and sends them to the target system.&lt;/P&gt;</description>
      <pubDate>Sat, 23 Oct 2010 01:44:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/splunk-tcp-output-format/m-p/75778#M15467</guid>
      <dc:creator>ziegfried</dc:creator>
      <dc:date>2010-10-23T01:44:30Z</dc:date>
    </item>
    <item>
      <title>Re: splunk tcp output format...</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/splunk-tcp-output-format/m-p/75779#M15468</link>
      <description>&lt;P&gt;It's not documented, and probably never will be.  If you need event metadata you're probably best off with the realtime search suggestion above -- that way you have control about exactly what fields you get.&lt;/P&gt;</description>
      <pubDate>Sat, 23 Oct 2010 07:33:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/splunk-tcp-output-format/m-p/75779#M15468</guid>
      <dc:creator>mitch_1</dc:creator>
      <dc:date>2010-10-23T07:33:16Z</dc:date>
    </item>
    <item>
      <title>Re: splunk tcp output format...</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/splunk-tcp-output-format/m-p/75780#M15469</link>
      <description>&lt;P&gt;It doesn't look like a tremendously complex protocol. You can always fire up a netcat listener, dump everything to a file, and take a peek.&lt;/P&gt;

&lt;P&gt;Of course, there's no guarantee that it won't get changed in the next release of Splunk. Looks like the format is already on version 2.&lt;/P&gt;</description>
      <pubDate>Sat, 23 Oct 2010 08:28:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/splunk-tcp-output-format/m-p/75780#M15469</guid>
      <dc:creator>southeringtonp</dc:creator>
      <dc:date>2010-10-23T08:28:37Z</dc:date>
    </item>
  </channel>
</rss>

