<?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 Intermittent log data ingestion with Packetbeat JSON file in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Intermittent-log-data-ingestion-with-Packetbeat-JSON-file/m-p/706930#M239161</link>
    <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I am experiencing intermittent log ingestion issues on some servers and have observed potential queue saturation in the process. Below are the details of the issue and the related observations:&lt;/SPAN&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;SPAN&gt;Setup Overview:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I am using Packetbeat to capture DNS queries across multiple servers.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Packetbeat generates JSON log files, rotating logs into 10 files, each with a maximum size of 50 MB. Packetbeat generates 3-4 JSON files every minute&lt;BR /&gt;Setup -&amp;gt; Splunk Cloud 9.2.2 , On-Prem Heavy Forwarder 9.1.2 , and Universal Forwarder 9.1.2&lt;BR /&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Example list of Packetbeat log files (rotated by Packetbeat):&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;packetbeat.json&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;packetbeat.1.json&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;packetbeat.2.json&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;packetbeat.3.json&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;...&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;packetbeat.9.json&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Issue Observed:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;On some servers, the logs are ingested and monitored consistently by the Splunk agent, functioning as expected.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;However, on other servers:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Logs are ingested for a few minutes, followed by a 5–6-minute gap.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;This cycle repeats,&amp;nbsp; resulting in missing data in between, while other data collected from the same server ingesting correctly.&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Intermittent_data_ingestion.png" style="width: 999px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/33866iA63215CD0AA974CA/image-size/large?v=v2&amp;amp;px=999" role="button" title="Intermittent_data_ingestion.png" alt="Intermittent_data_ingestion.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Additional Observations:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;While investigating the issue, I observed the following log entry in the Splunk Universal Forwarder _internal index:&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;11-15-2024 17:27:35.615 -0600 INFO HealthChangeReporter - feature="Real-time Reader-0" indicator="data_out_rate" previous_color=yellow color=red due_to_threshold_value=2 measured_value=2 reason="The monitor input cannot produce data because splunkd's processing queues are full. This will be caused by inadequate indexing or forwarding rate, or a sudden burst of incoming data."
host = EAA-DC
index = _internal
source = C:\Program Files\SplunkUniversalForwarder\var\log\splunk\health.log
sourcetype = splunkd​&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The following conf applied to all DNS servers:&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;limits.conf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[thruput]
maxKBps = 0&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;server.conf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[queue]
maxSize = 512MB&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;inputs.conf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[monitor://C:\packetbeat.json]
disabled = false
index = dns
sourcetype = packetbeat&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any direction to resolve this is appreciated! Thank you!&lt;/P&gt;</description>
    <pubDate>Tue, 17 Dec 2024 18:00:55 GMT</pubDate>
    <dc:creator>s_s</dc:creator>
    <dc:date>2024-12-17T18:00:55Z</dc:date>
    <item>
      <title>Intermittent log data ingestion with Packetbeat JSON file</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Intermittent-log-data-ingestion-with-Packetbeat-JSON-file/m-p/706930#M239161</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I am experiencing intermittent log ingestion issues on some servers and have observed potential queue saturation in the process. Below are the details of the issue and the related observations:&lt;/SPAN&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;SPAN&gt;Setup Overview:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I am using Packetbeat to capture DNS queries across multiple servers.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Packetbeat generates JSON log files, rotating logs into 10 files, each with a maximum size of 50 MB. Packetbeat generates 3-4 JSON files every minute&lt;BR /&gt;Setup -&amp;gt; Splunk Cloud 9.2.2 , On-Prem Heavy Forwarder 9.1.2 , and Universal Forwarder 9.1.2&lt;BR /&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Example list of Packetbeat log files (rotated by Packetbeat):&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;packetbeat.json&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;packetbeat.1.json&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;packetbeat.2.json&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;packetbeat.3.json&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;...&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;packetbeat.9.json&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Issue Observed:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;On some servers, the logs are ingested and monitored consistently by the Splunk agent, functioning as expected.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;However, on other servers:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Logs are ingested for a few minutes, followed by a 5–6-minute gap.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;This cycle repeats,&amp;nbsp; resulting in missing data in between, while other data collected from the same server ingesting correctly.&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Intermittent_data_ingestion.png" style="width: 999px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/33866iA63215CD0AA974CA/image-size/large?v=v2&amp;amp;px=999" role="button" title="Intermittent_data_ingestion.png" alt="Intermittent_data_ingestion.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Additional Observations:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;While investigating the issue, I observed the following log entry in the Splunk Universal Forwarder _internal index:&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;11-15-2024 17:27:35.615 -0600 INFO HealthChangeReporter - feature="Real-time Reader-0" indicator="data_out_rate" previous_color=yellow color=red due_to_threshold_value=2 measured_value=2 reason="The monitor input cannot produce data because splunkd's processing queues are full. This will be caused by inadequate indexing or forwarding rate, or a sudden burst of incoming data."
host = EAA-DC
index = _internal
source = C:\Program Files\SplunkUniversalForwarder\var\log\splunk\health.log
sourcetype = splunkd​&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The following conf applied to all DNS servers:&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;limits.conf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[thruput]
maxKBps = 0&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;server.conf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[queue]
maxSize = 512MB&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;inputs.conf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[monitor://C:\packetbeat.json]
disabled = false
index = dns
sourcetype = packetbeat&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any direction to resolve this is appreciated! Thank you!&lt;/P&gt;</description>
      <pubDate>Tue, 17 Dec 2024 18:00:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Intermittent-log-data-ingestion-with-Packetbeat-JSON-file/m-p/706930#M239161</guid>
      <dc:creator>s_s</dc:creator>
      <dc:date>2024-12-17T18:00:55Z</dc:date>
    </item>
    <item>
      <title>Re: Intermittent log data ingestion with Packetbeat JSON file</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Intermittent-log-data-ingestion-with-Packetbeat-JSON-file/m-p/707093#M239207</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/267573"&gt;@s_s&lt;/a&gt;&amp;nbsp;Hello, checkout the queues on the hwf pipleine, and also see if you can apply&amp;nbsp; async forwarding.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://www.linkedin.com/pulse/splunk-asynchronous-forwarding-lightning-fast-data-ingestor-rawat" target="_blank"&gt;https://www.linkedin.com/pulse/splunk-asynchronous-forwarding-lightning-fast-data-ingestor-rawat&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;If this Helps, Please Upvote.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2024 02:16:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Intermittent-log-data-ingestion-with-Packetbeat-JSON-file/m-p/707093#M239207</guid>
      <dc:creator>sainag_splunk</dc:creator>
      <dc:date>2024-12-18T02:16:38Z</dc:date>
    </item>
  </channel>
</rss>

