<?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: Dataset used for getting search performance numbers in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Dataset-used-for-getting-search-performance-numbers/m-p/388959#M3336</link>
    <description>&lt;P&gt;Hi, @swatishs &lt;/P&gt;

&lt;P&gt;You can simply generate a dataset on your own with the Eventgen tool available in Splunk Base &lt;A href="https://splunkbase.splunk.com/app/1924/#/details"&gt;https://splunkbase.splunk.com/app/1924/#/details&lt;/A&gt;. It ships with event samples which you can modify to your environment. Additionally, to create a known distribution of your matching rates, you can create artificial fields that simply contain keywords like "every10", "every1M", etc., so you can use them in your searches to test, for example:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;dense search:
'search index={index_name} every10  | stats count'

sparse search:
'search index={index_name} every1K  | stats count'

rare search:
'search index={index_name} every10M | stats count'
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Wed, 03 Apr 2019 17:50:53 GMT</pubDate>
    <dc:creator>jessec_splunk</dc:creator>
    <dc:date>2019-04-03T17:50:53Z</dc:date>
    <item>
      <title>Dataset used for getting search performance numbers</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Dataset-used-for-getting-search-performance-numbers/m-p/388958#M3335</link>
      <description>&lt;P&gt;I want to evaluate the search performance of my Splunk setup similar to what Splunk has published here:&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.2.3/Capacity/HowsearchtypesaffectSplunkEnterpriseperformance"&gt;https://docs.splunk.com/Documentation/Splunk/7.2.3/Capacity/HowsearchtypesaffectSplunkEnterpriseperformance&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Does anyone know:&lt;BR /&gt;
1. The dataset they used?&lt;BR /&gt;
2. The search queries they performed for various types of searches (dense, sparse etc.)?&lt;/P&gt;

&lt;P&gt;If it is not published, can anyone point me to such a dataset suited for measuring search performance?&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2019 06:40:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Dataset-used-for-getting-search-performance-numbers/m-p/388958#M3335</guid>
      <dc:creator>swatishs</dc:creator>
      <dc:date>2019-04-03T06:40:49Z</dc:date>
    </item>
    <item>
      <title>Re: Dataset used for getting search performance numbers</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Dataset-used-for-getting-search-performance-numbers/m-p/388959#M3336</link>
      <description>&lt;P&gt;Hi, @swatishs &lt;/P&gt;

&lt;P&gt;You can simply generate a dataset on your own with the Eventgen tool available in Splunk Base &lt;A href="https://splunkbase.splunk.com/app/1924/#/details"&gt;https://splunkbase.splunk.com/app/1924/#/details&lt;/A&gt;. It ships with event samples which you can modify to your environment. Additionally, to create a known distribution of your matching rates, you can create artificial fields that simply contain keywords like "every10", "every1M", etc., so you can use them in your searches to test, for example:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;dense search:
'search index={index_name} every10  | stats count'

sparse search:
'search index={index_name} every1K  | stats count'

rare search:
'search index={index_name} every10M | stats count'
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 03 Apr 2019 17:50:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Dataset-used-for-getting-search-performance-numbers/m-p/388959#M3336</guid>
      <dc:creator>jessec_splunk</dc:creator>
      <dc:date>2019-04-03T17:50:53Z</dc:date>
    </item>
  </channel>
</rss>

