<?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: Best Practice for Automatic Lookups in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Best-Practice-for-Automatic-Lookups/m-p/669013#M17885</link>
    <description>&lt;P&gt;I'm not sure there are best practices around automatic lookups.&amp;nbsp; There are some for lookups in general, however.&amp;nbsp; Monitor lookup size (in bytes) to make sure they don't cause the knowledge bundle to become too large (2GB).&amp;nbsp; Large lookups should be blocked from the bundle or converted to KVStore.&lt;/P&gt;</description>
    <pubDate>Fri, 17 Nov 2023 13:40:54 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2023-11-17T13:40:54Z</dc:date>
    <item>
      <title>Best Practice for Automatic Lookups</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Best-Practice-for-Automatic-Lookups/m-p/668734#M17876</link>
      <description>&lt;P&gt;Is there a suggested size of lookup that would be the maximum size of a lookup that should be used for an automatic lookup?&lt;/P&gt;&lt;P&gt;Such as if your lookup exceeds more than x rows it would best not to use with an automatic lookup?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Nov 2023 12:11:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Best-Practice-for-Automatic-Lookups/m-p/668734#M17876</guid>
      <dc:creator>jaburke1</dc:creator>
      <dc:date>2023-11-15T12:11:19Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practice for Automatic Lookups</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Best-Practice-for-Automatic-Lookups/m-p/669013#M17885</link>
      <description>&lt;P&gt;I'm not sure there are best practices around automatic lookups.&amp;nbsp; There are some for lookups in general, however.&amp;nbsp; Monitor lookup size (in bytes) to make sure they don't cause the knowledge bundle to become too large (2GB).&amp;nbsp; Large lookups should be blocked from the bundle or converted to KVStore.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Nov 2023 13:40:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Best-Practice-for-Automatic-Lookups/m-p/669013#M17885</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-11-17T13:40:54Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practice for Automatic Lookups</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Best-Practice-for-Automatic-Lookups/m-p/669016#M17886</link>
      <description>&lt;P&gt;Thanks Rich! Is it a bad practice to use a KVStore for automatic lookups since they can get very large?&lt;/P&gt;</description>
      <pubDate>Fri, 17 Nov 2023 13:52:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Best-Practice-for-Automatic-Lookups/m-p/669016#M17886</guid>
      <dc:creator>jaburke1</dc:creator>
      <dc:date>2023-11-17T13:52:40Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practice for Automatic Lookups</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Best-Practice-for-Automatic-Lookups/m-p/669027#M17887</link>
      <description>&lt;P&gt;I wouldn't say that at all.&amp;nbsp; One of the features of KVStore is to replace large lookup files.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Nov 2023 15:33:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Best-Practice-for-Automatic-Lookups/m-p/669027#M17887</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-11-17T15:33:12Z</dc:date>
    </item>
  </channel>
</rss>

