<?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: Indexing queues greater than 100 lines in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Indexing-queues-greater-than-100-lines/m-p/57352#M13995</link>
    <description>&lt;P&gt;Oh, Sorry.&lt;BR /&gt;
I could not find something about it to bring to my own question.&lt;BR /&gt;
I'm sorry.&lt;/P&gt;</description>
    <pubDate>Mon, 16 Sep 2013 05:23:54 GMT</pubDate>
    <dc:creator>jrodriguezap</dc:creator>
    <dc:date>2013-09-16T05:23:54Z</dc:date>
    <item>
      <title>Indexing queues greater than 100 lines</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Indexing-queues-greater-than-100-lines/m-p/57349#M13992</link>
      <description>&lt;P&gt;Hi all, I would like to set the transforms.conf started indexing log files when they exceed the 100 lines per second as a condition in the Regex, I believe that it is possible to Splunk, any ideas, suggestions or reference to a link to achieve?&lt;/P&gt;

&lt;P&gt;Thanks in advance for your attention.&lt;BR /&gt;
regards&lt;/P&gt;</description>
      <pubDate>Sun, 08 Sep 2013 00:42:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Indexing-queues-greater-than-100-lines/m-p/57349#M13992</guid>
      <dc:creator>jrodriguezap</dc:creator>
      <dc:date>2013-09-08T00:42:57Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing queues greater than 100 lines</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Indexing-queues-greater-than-100-lines/m-p/57350#M13993</link>
      <description>&lt;P&gt;Señor Rodríguez:&lt;/P&gt;

&lt;P&gt;I have deleted our struggles from last night and I am sending you an email. I will connect you with my colleague who covers Latin America. &lt;/P&gt;

&lt;P&gt;I believe do understand what you need now, and I have a suggestion - but still am unclear about some of your environment and feel it is the translator that is not helping us.&lt;/P&gt;

&lt;P&gt;When you have the solution, please post it here as the answer and I will up-vote so that others may benefit.&lt;/P&gt;</description>
      <pubDate>Sun, 08 Sep 2013 14:09:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Indexing-queues-greater-than-100-lines/m-p/57350#M13993</guid>
      <dc:creator>rsennett_splunk</dc:creator>
      <dc:date>2013-09-08T14:09:59Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing queues greater than 100 lines</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Indexing-queues-greater-than-100-lines/m-p/57351#M13994</link>
      <description>&lt;P&gt;There is no such method to wait for number of lines before indexing ,Splunk will start indexing the file as soon as they are available.&lt;/P&gt;

&lt;P&gt;What is the problem with your files, are the events cut in multiple events :&lt;/P&gt;

&lt;P&gt;A  - are your events longer than 250 lines per events.&lt;BR /&gt;
Splunk has a default limit for the multiline events, you can configure your sourcetype in props,conf (at the indexer/heavy forwarder level) with MAX_EVENTS=&lt;INTEGER&gt;&lt;/INTEGER&gt;&lt;/P&gt;

&lt;P&gt;B - Is your application using a write buffer and writing slowly in chunk (cutting events in the middle of the line ? )&lt;BR /&gt;
you can use the setting time_before_close in inputs.conf on the forwarders for this monitor, to force Splunk to wait longer before detecting the EOF.&lt;/P&gt;

&lt;P&gt;see &lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.4/admin/Inputsconf" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.4/admin/Inputsconf&lt;/A&gt;&lt;BR /&gt;
time_before_close = &lt;INTEGER&gt;&lt;BR /&gt;
* Modtime delta required before Splunk can close a file on EOF.&lt;BR /&gt;
* Tells the system not to close files that have been updated in past &lt;INTEGER&gt; seconds.&lt;BR /&gt;
* Defaults to 3.&lt;/INTEGER&gt;&lt;/INTEGER&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 14:43:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Indexing-queues-greater-than-100-lines/m-p/57351#M13994</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2020-09-28T14:43:57Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing queues greater than 100 lines</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Indexing-queues-greater-than-100-lines/m-p/57352#M13995</link>
      <description>&lt;P&gt;Oh, Sorry.&lt;BR /&gt;
I could not find something about it to bring to my own question.&lt;BR /&gt;
I'm sorry.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Sep 2013 05:23:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Indexing-queues-greater-than-100-lines/m-p/57352#M13995</guid>
      <dc:creator>jrodriguezap</dc:creator>
      <dc:date>2013-09-16T05:23:54Z</dc:date>
    </item>
  </channel>
</rss>

