<?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: SPL to identify UFs needed to increase pipeline sets in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/SPL-to-identify-UFs-needed-to-increase-pipeline-sets/m-p/569405#M198453</link>
    <description>&lt;P&gt;When a queue is blocked it's usually because something downstream is unable to keep up with things.&amp;nbsp; Often that's either the network or the indexers.&amp;nbsp; In those cases, adding another pipeline to the UF will just make things worse.&lt;/P&gt;&lt;P&gt;Use the Monitoring Console to check the health of the indexers.&amp;nbsp; Treat what you find.&lt;/P&gt;&lt;P&gt;Increasing the maxKBps setting in the UF's limits.conf file may get things moving.&lt;/P&gt;&lt;P&gt;To see numbers, this query may help:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=_internal component=Metrics group=queue&lt;/LI-CODE&gt;</description>
    <pubDate>Fri, 01 Oct 2021 21:18:56 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2021-10-01T21:18:56Z</dc:date>
    <item>
      <title>SPL to identify UFs needed to increase pipeline sets</title>
      <link>https://community.splunk.com/t5/Splunk-Search/SPL-to-identify-UFs-needed-to-increase-pipeline-sets/m-p/569275#M198412</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;We are planning to configure some of our universal forwarders to use multiple pipeline sets. Do you have some sort of SPL that we can use to identify which forwarders have blocking queues and needs to increase the number of pipeline set.&lt;/P&gt;</description>
      <pubDate>Fri, 01 Oct 2021 07:07:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/SPL-to-identify-UFs-needed-to-increase-pipeline-sets/m-p/569275#M198412</guid>
      <dc:creator>jaracan</dc:creator>
      <dc:date>2021-10-01T07:07:36Z</dc:date>
    </item>
    <item>
      <title>Re: SPL to identify UFs needed to increase pipeline sets</title>
      <link>https://community.splunk.com/t5/Splunk-Search/SPL-to-identify-UFs-needed-to-increase-pipeline-sets/m-p/569405#M198453</link>
      <description>&lt;P&gt;When a queue is blocked it's usually because something downstream is unable to keep up with things.&amp;nbsp; Often that's either the network or the indexers.&amp;nbsp; In those cases, adding another pipeline to the UF will just make things worse.&lt;/P&gt;&lt;P&gt;Use the Monitoring Console to check the health of the indexers.&amp;nbsp; Treat what you find.&lt;/P&gt;&lt;P&gt;Increasing the maxKBps setting in the UF's limits.conf file may get things moving.&lt;/P&gt;&lt;P&gt;To see numbers, this query may help:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=_internal component=Metrics group=queue&lt;/LI-CODE&gt;</description>
      <pubDate>Fri, 01 Oct 2021 21:18:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/SPL-to-identify-UFs-needed-to-increase-pipeline-sets/m-p/569405#M198453</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-10-01T21:18:56Z</dc:date>
    </item>
  </channel>
</rss>

