<?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 Recommended settings for HEC batch? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Recommended-settings-for-HEC-batch/m-p/630542#M108074</link>
    <description>&lt;P&gt;When sending batch data to HEC server, with multiple events per request, is it better to send large (10k-100k), medium (1k-10k) or small (&amp;gt;1k) batch data to the HEC server? Is there anything that can be done to ensure data is ingested faster and smoother?&lt;/P&gt;</description>
    <pubDate>Mon, 13 Feb 2023 17:05:34 GMT</pubDate>
    <dc:creator>spammenot66</dc:creator>
    <dc:date>2023-02-13T17:05:34Z</dc:date>
    <item>
      <title>Recommended settings for HEC batch?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Recommended-settings-for-HEC-batch/m-p/630542#M108074</link>
      <description>&lt;P&gt;When sending batch data to HEC server, with multiple events per request, is it better to send large (10k-100k), medium (1k-10k) or small (&amp;gt;1k) batch data to the HEC server? Is there anything that can be done to ensure data is ingested faster and smoother?&lt;/P&gt;</description>
      <pubDate>Mon, 13 Feb 2023 17:05:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Recommended-settings-for-HEC-batch/m-p/630542#M108074</guid>
      <dc:creator>spammenot66</dc:creator>
      <dc:date>2023-02-13T17:05:34Z</dc:date>
    </item>
  </channel>
</rss>

