<?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: Adding a custom &amp;quot;handler&amp;quot; to TCP/UDP input in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Adding-a-custom-quot-handler-quot-to-TCP-UDP-input/m-p/23781#M96592</link>
    <description>&lt;P&gt;Hi Damien, don't forget to "accept" an answer by clicking the outlined check-mark to the left of it.&lt;/P&gt;</description>
    <pubDate>Thu, 09 Jun 2011 16:15:35 GMT</pubDate>
    <dc:creator>dwaddle</dc:creator>
    <dc:date>2011-06-09T16:15:35Z</dc:date>
    <item>
      <title>Adding a custom "handler" to TCP/UDP input</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Adding-a-custom-quot-handler-quot-to-TCP-UDP-input/m-p/23777#M96588</link>
      <description>&lt;P&gt;Does such a facility exist within SPLUNK by which you can add a custom "handler" to a TCP or UDP socket input ?&lt;/P&gt;

&lt;P&gt;Such a scenario might be where you want to send data to SPLUNK via TCP, and this data might be a proprietary layer 4 network protocol that requires a custom handler to first decode the raw protocol bytes into a textual format before passing on to SPLUNK indexing.&lt;/P&gt;

&lt;P&gt;I could quite easily write a "scripted input" that listens on a socket and outputs decoded bytes to STDOUT, but it would be nice if I could just write a custom "handler" that chains onto a standard TCP input.&lt;/P&gt;

&lt;P&gt;Regards,&lt;/P&gt;

&lt;P&gt;Damien D.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2011 03:39:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Adding-a-custom-quot-handler-quot-to-TCP-UDP-input/m-p/23777#M96588</guid>
      <dc:creator>Damien_Dallimor</dc:creator>
      <dc:date>2011-06-07T03:39:42Z</dc:date>
    </item>
    <item>
      <title>Re: Adding a custom "handler" to TCP/UDP input</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Adding-a-custom-quot-handler-quot-to-TCP-UDP-input/m-p/23778#M96589</link>
      <description>&lt;P&gt;Such a facility does not exist at this time.  At least, not that is accessible to us customers.  Splunk may have such a technique they use internally - but I don't think they expose any kind of API for us to get at it.&lt;/P&gt;

&lt;P&gt;If this is something you want Splunk to consider you should submit an ER for it.&lt;BR /&gt;&lt;BR /&gt;
&lt;A href="http://splunk-base.splunk.com/answers/4844/how-can-i-submit-an-enhancement-request"&gt;http://splunk-base.splunk.com/answers/4844/how-can-i-submit-an-enhancement-request&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2011 14:41:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Adding-a-custom-quot-handler-quot-to-TCP-UDP-input/m-p/23778#M96589</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2011-06-07T14:41:06Z</dc:date>
    </item>
    <item>
      <title>Re: Adding a custom "handler" to TCP/UDP input</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Adding-a-custom-quot-handler-quot-to-TCP-UDP-input/m-p/23779#M96590</link>
      <description>&lt;P&gt;Just write a scripted input, especially if you are confident that you can do it.  What is the difference between that and a custom handler?  &lt;/P&gt;

&lt;P&gt;In general, your handler will provide the bottleneck, so the underlying TCP and UDP sockets don't really buy you anything.  &lt;/P&gt;

&lt;P&gt;If you just &lt;STRONG&gt;must&lt;/STRONG&gt; use Splunk's sockets, have your scripted input listen on one port, do your decoding, and send the plain-text stream to a Splunk socket listening on another port.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2011 17:19:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Adding-a-custom-quot-handler-quot-to-TCP-UDP-input/m-p/23779#M96590</guid>
      <dc:creator>araitz</dc:creator>
      <dc:date>2011-06-07T17:19:35Z</dc:date>
    </item>
    <item>
      <title>Re: Adding a custom "handler" to TCP/UDP input</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Adding-a-custom-quot-handler-quot-to-TCP-UDP-input/m-p/23780#M96591</link>
      <description>&lt;P&gt;Thanks guys..I think I'll go with the scripted input proxying on to a Splunk socket input.&lt;/P&gt;

&lt;P&gt;Damien D. &lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2011 21:38:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Adding-a-custom-quot-handler-quot-to-TCP-UDP-input/m-p/23780#M96591</guid>
      <dc:creator>Damien_Dallimor</dc:creator>
      <dc:date>2011-06-07T21:38:53Z</dc:date>
    </item>
    <item>
      <title>Re: Adding a custom "handler" to TCP/UDP input</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Adding-a-custom-quot-handler-quot-to-TCP-UDP-input/m-p/23781#M96592</link>
      <description>&lt;P&gt;Hi Damien, don't forget to "accept" an answer by clicking the outlined check-mark to the left of it.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Jun 2011 16:15:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Adding-a-custom-quot-handler-quot-to-TCP-UDP-input/m-p/23781#M96592</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2011-06-09T16:15:35Z</dc:date>
    </item>
  </channel>
</rss>

