<?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 over long-lived TCP connection? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-send-events-over-long-lived-TCP-connection/m-p/104428#M21998</link>
    <description>&lt;P&gt;To answer my own question: &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Wheretofindtheconfigurationfiles"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/Wheretofindtheconfigurationfiles&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 08 Nov 2011 11:54:31 GMT</pubDate>
    <dc:creator>giraffe</dc:creator>
    <dc:date>2011-11-08T11:54:31Z</dc:date>
    <item>
      <title>How to send events over long-lived TCP connection?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-send-events-over-long-lived-TCP-connection/m-p/104424#M21994</link>
      <description>&lt;P&gt;Our application generates many small monitoring events.  We are feeding these to Splunk by TCP.  We would like to keep a single connection open between each of our processes and the Splunk TCP input. However, when we do this the events do not appear when sent over the TCP connection, but only when the TCP stream is closed.  Then they all appear together as a single event.&lt;/P&gt;

&lt;P&gt;How do we configure the TCP input to generate one event per line as they stream in, instead of treating all data received over the connection as a single event?&lt;/P&gt;</description>
      <pubDate>Fri, 04 Nov 2011 16:46:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-send-events-over-long-lived-TCP-connection/m-p/104424#M21994</guid>
      <dc:creator>giraffe</dc:creator>
      <dc:date>2011-11-04T16:46:13Z</dc:date>
    </item>
    <item>
      <title>Re: How to send events over long-lived TCP connection?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-send-events-over-long-lived-TCP-connection/m-p/104425#M21995</link>
      <description>&lt;P&gt;You need to tell Splunk when to break the incoming data into new events. Right now Splunk doesn't find anything to break the events on, so it waits until the end of the input stream. By default Splunk will create a new event when it encounters something it recognizes as a timestamp, or when the maximum defined number of lines in an event has been reached (default 256). These settings are specified in props.conf (docs: &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/admin/propsconf"&gt;http://docs.splunk.com/Documentation/Splunk/latest/admin/propsconf&lt;/A&gt; - the settings you're looking for are &lt;CODE&gt;MAX_EVENTS&lt;/CODE&gt; and &lt;CODE&gt;BREAK_ONLY_BEFORE_DATE&lt;/CODE&gt;).&lt;/P&gt;

&lt;P&gt;Could you paste some sample events? That way we could help with coming up with working settings for breaking your log stream into individual events.&lt;/P&gt;</description>
      <pubDate>Fri, 04 Nov 2011 17:37:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-send-events-over-long-lived-TCP-connection/m-p/104425#M21995</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2011-11-04T17:37:04Z</dc:date>
    </item>
    <item>
      <title>Re: How to send events over long-lived TCP connection?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-send-events-over-long-lived-TCP-connection/m-p/104426#M21996</link>
      <description>&lt;P&gt;You can add timestamp/unix time to the begging of event line. For example:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;1320663001,event1
1320663002,event2
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;In this case splunk will divide events&lt;/P&gt;

&lt;P&gt;unix time is a &lt;CODE&gt;"date +%s"&lt;/CODE&gt; command in linux systems, or &lt;CODE&gt;$sTimeStamp = get-date ((Get-Date).touniversaltime()) -uformat "%s"&lt;/CODE&gt; in PowerShell&lt;/P&gt;</description>
      <pubDate>Mon, 07 Nov 2011 10:58:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-send-events-over-long-lived-TCP-connection/m-p/104426#M21996</guid>
      <dc:creator>Vladimir</dc:creator>
      <dc:date>2011-11-07T10:58:47Z</dc:date>
    </item>
    <item>
      <title>Re: How to send events over long-lived TCP connection?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-send-events-over-long-lived-TCP-connection/m-p/104427#M21997</link>
      <description>&lt;P&gt;I've found a props.conf in etc/system/defaults.  Can I create one in /etc/system/local?  And if so, will the definitions in there be merged with the one in etc/system/defaults or will the defaults be ignored?&lt;/P&gt;</description>
      <pubDate>Tue, 08 Nov 2011 11:30:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-send-events-over-long-lived-TCP-connection/m-p/104427#M21997</guid>
      <dc:creator>giraffe</dc:creator>
      <dc:date>2011-11-08T11:30:37Z</dc:date>
    </item>
    <item>
      <title>Re: How to send events over long-lived TCP connection?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-send-events-over-long-lived-TCP-connection/m-p/104428#M21998</link>
      <description>&lt;P&gt;To answer my own question: &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Wheretofindtheconfigurationfiles"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/Wheretofindtheconfigurationfiles&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Nov 2011 11:54:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-send-events-over-long-lived-TCP-connection/m-p/104428#M21998</guid>
      <dc:creator>giraffe</dc:creator>
      <dc:date>2011-11-08T11:54:31Z</dc:date>
    </item>
  </channel>
</rss>

