<?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 Heavy forwarder connections to Splunk indexers by checking internal logs for any type of issues. in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-connections-to-Splunk-indexers-by-checking/m-p/695049#M115458</link>
    <description>&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;i have to create an alert to monitor any issue happens for HF to Indexers, by checking internal logs. I am using this spl. Need suggestions or correct SPL.&lt;BR /&gt;&lt;BR /&gt;index=_internal source=*metrics.log group=tcpin_connections hostname="*hf*"&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 02 Aug 2024 07:48:08 GMT</pubDate>
    <dc:creator>phanikumarcs</dc:creator>
    <dc:date>2024-08-02T07:48:08Z</dc:date>
    <item>
      <title>Heavy forwarder connections to Splunk indexers by checking internal logs for any type of issues.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-connections-to-Splunk-indexers-by-checking/m-p/695049#M115458</link>
      <description>&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;i have to create an alert to monitor any issue happens for HF to Indexers, by checking internal logs. I am using this spl. Need suggestions or correct SPL.&lt;BR /&gt;&lt;BR /&gt;index=_internal source=*metrics.log group=tcpin_connections hostname="*hf*"&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2024 07:48:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-connections-to-Splunk-indexers-by-checking/m-p/695049#M115458</guid>
      <dc:creator>phanikumarcs</dc:creator>
      <dc:date>2024-08-02T07:48:08Z</dc:date>
    </item>
    <item>
      <title>Re: Heavy forwarder connections to Splunk indexers by checking internal logs for any type of issues.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-connections-to-Splunk-indexers-by-checking/m-p/695051#M115459</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/254654"&gt;@phanikumarcs&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;I'd simplify your search to search eventual erros:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=_internal hostname="*hf*"&lt;/LI-CODE&gt;&lt;P&gt;whot do you want to monitor?&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2024 08:04:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-connections-to-Splunk-indexers-by-checking/m-p/695051#M115459</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2024-08-02T08:04:19Z</dc:date>
    </item>
    <item>
      <title>Re: Heavy forwarder connections to Splunk indexers by checking internal logs for any type of issues.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-connections-to-Splunk-indexers-by-checking/m-p/695052#M115460</link>
      <description>&lt;P&gt;Yes, but we have to setup a alert for example if any issues will get based on warns or errors it will trigger&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2024 08:07:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-connections-to-Splunk-indexers-by-checking/m-p/695052#M115460</guid>
      <dc:creator>phanikumarcs</dc:creator>
      <dc:date>2024-08-02T08:07:08Z</dc:date>
    </item>
    <item>
      <title>Re: Heavy forwarder connections to Splunk indexers by checking internal logs for any type of issues.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-connections-to-Splunk-indexers-by-checking/m-p/695053#M115461</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/254654"&gt;@phanikumarcs&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;as I said, define your Use Cases, then you could create your searches.&lt;/P&gt;&lt;P&gt;e.g. you could create an alert for the queues:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=_internal  source=*metrics.log sourcetype=splunkd group=queue 
| eval name=case(name=="aggqueue","2 - Aggregation Queue",
 name=="indexqueue", "4 - Indexing Queue",
 name=="parsingqueue", "1 - Parsing Queue",
 name=="typingqueue", "3 - Typing Queue",
 name=="splunktcpin", "0 - TCP In Queue",
 name=="tcpin_cooked_pqueue", "0 - TCP In Queue") 
| eval max=if(isnotnull(max_size_kb),max_size_kb,max_size) 
| eval curr=if(isnotnull(current_size_kb),current_size_kb,current_size) 
| eval fill_perc=round((curr/max)*100,2) 
| bin _time span=1m
| stats Median(fill_perc) AS "fill_percentage" perc90(fill_perc) AS "90_perc" max(max) AS max max(curr) AS curr by host, _time, name 
| where (fill_percentage&amp;gt;70 AND name!="4 - Indexing Queue") OR (fill_percentage&amp;gt;70 AND name="4 - Indexing Queue")
| sort -_time&lt;/LI-CODE&gt;&lt;P&gt;then you could check the disk space,&lt;/P&gt;&lt;P&gt;or whtelse you like.&lt;/P&gt;&lt;P&gt;Anyway: define your Use Cases&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2024 08:16:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-connections-to-Splunk-indexers-by-checking/m-p/695053#M115461</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2024-08-02T08:16:18Z</dc:date>
    </item>
  </channel>
</rss>

