<?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: Splunk Enterprise Security - TSIDX-dependent Correlation Searches not working after 3.0 upgrade in Splunk Enterprise Security</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-TSIDX-dependent-Correlation-Searches/m-p/134099#M423</link>
    <description>&lt;P&gt;moving the bucket location means that acceleration needs to be rebuilt.&lt;/P&gt;</description>
    <pubDate>Wed, 25 Feb 2015 20:53:04 GMT</pubDate>
    <dc:creator>mcronkrite</dc:creator>
    <dc:date>2015-02-25T20:53:04Z</dc:date>
    <item>
      <title>Splunk Enterprise Security - TSIDX-dependent Correlation Searches not working after 3.0 upgrade</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-TSIDX-dependent-Correlation-Searches/m-p/134095#M419</link>
      <description>&lt;P&gt;We recently upgraded our Enterprise Security instance to v3.0 from v2.4. After the upgrade, I noticed that Correlation Searches relying on TSIDX instances (that is, searches that begin with a command of the form "| tstats count FROM datamodel=X") do not appear to be functioning properly. I can verify that the data models are building properly, and when I try to return the same data with a "| pivot" command, it works just fine. I'd like to know why this is happening, and see if we can remediate it...I know I can convert all my correlation searches to "| pivot" commands, but I'm hoping there's a better way.&lt;/P&gt;

&lt;P&gt;If it makes any difference, we have changed the default home directory of the data model summaries; instead of living in /opt/splunk/var/lib/splunk/index-name, they live in /opt/splunk/var/lib/splunk/index-name/db. I first noticed this problem after the change, so that may have something to do with it...&lt;/P&gt;</description>
      <pubDate>Wed, 16 Apr 2014 19:19:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-TSIDX-dependent-Correlation-Searches/m-p/134095#M419</guid>
      <dc:creator>BenjaminWyatt</dc:creator>
      <dc:date>2014-04-16T19:19:58Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Enterprise Security - TSIDX-dependent Correlation Searches not working after 3.0 upgrade</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-TSIDX-dependent-Correlation-Searches/m-p/134096#M420</link>
      <description>&lt;P&gt;Benjamin,&lt;/P&gt;

&lt;P&gt;Most of our correlations (along w/ report and dashboard searches) at this time use the `summariesonly` macro which defaults to "true" based on our macro definition in the SA-Utils app.  This means that we will only search across accelerated data.  This is really only difference between our tstats searches and pivot that I can think would be attributing to the differences you are seeing.  For testing purposes, you should be able to run searches using "| tstats count from datamodel=$model$" vs. "| tstats summariesonly=true count from datamodel=$model$".  If you are seeing a discrepancy between tstats searches, this is an indication that acceleration is not complete, or is having problems.  You should absolutely not have to convert any correlation searches.&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
David&lt;/P&gt;</description>
      <pubDate>Wed, 16 Apr 2014 21:40:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-TSIDX-dependent-Correlation-Searches/m-p/134096#M420</guid>
      <dc:creator>hazekamp</dc:creator>
      <dc:date>2014-04-16T21:40:51Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Enterprise Security - TSIDX-dependent Correlation Searches not working after 3.0 upgrade</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-TSIDX-dependent-Correlation-Searches/m-p/134097#M421</link>
      <description>&lt;P&gt;So it looks like I can see results now, but the searches are taking far longer than they should with data model acceleration - is there a "quick and easy" way to diagnose and troubleshoot issues with data model acceleration?&lt;/P&gt;</description>
      <pubDate>Thu, 17 Apr 2014 14:59:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-TSIDX-dependent-Correlation-Searches/m-p/134097#M421</guid>
      <dc:creator>BenjaminWyatt</dc:creator>
      <dc:date>2014-04-17T14:59:11Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Enterprise Security - TSIDX-dependent Correlation Searches not working after 3.0 upgrade</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-TSIDX-dependent-Correlation-Searches/m-p/134098#M422</link>
      <description>&lt;P&gt;I would check for the usual errors in splunkd,web_service, etc.  You can also run the following search for which the "info" field will give you status:&lt;/P&gt;

&lt;P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;CODE&gt;search_activity&lt;/CODE&gt; | search search_type="dm_acceleration" OR search_type="summary_directory"&lt;/CODE&gt;&lt;/PRE&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 16:25:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-TSIDX-dependent-Correlation-Searches/m-p/134098#M422</guid>
      <dc:creator>hazekamp</dc:creator>
      <dc:date>2020-09-28T16:25:03Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Enterprise Security - TSIDX-dependent Correlation Searches not working after 3.0 upgrade</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-TSIDX-dependent-Correlation-Searches/m-p/134099#M423</link>
      <description>&lt;P&gt;moving the bucket location means that acceleration needs to be rebuilt.&lt;/P&gt;</description>
      <pubDate>Wed, 25 Feb 2015 20:53:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-TSIDX-dependent-Correlation-Searches/m-p/134099#M423</guid>
      <dc:creator>mcronkrite</dc:creator>
      <dc:date>2015-02-25T20:53:04Z</dc:date>
    </item>
  </channel>
</rss>

