<?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: tsidx topologycruncy in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/tsidx-topologycruncy/m-p/236855#M99072</link>
    <description>&lt;P&gt;Done. Thanks!&lt;/P&gt;</description>
    <pubDate>Thu, 10 Mar 2016 18:57:12 GMT</pubDate>
    <dc:creator>baoctac</dc:creator>
    <dc:date>2016-03-10T18:57:12Z</dc:date>
    <item>
      <title>tsidx topologycruncy</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/tsidx-topologycruncy/m-p/236849#M99066</link>
      <description>&lt;P&gt;Sifting through the discussions about tsidx files, I still find myself confused on how these populate. Currently on my search head, there are 25GB in the tsidx/topologyCrunch directory. The only apps I have installed are Splunk App for AWS and Nessus. From the Settings &amp;gt; Report Acceleration Summary, no accelerations are configured.&lt;/P&gt;

&lt;P&gt;My questions are: 1) how can i determine where these files are coming from, and 2) how do i go about removing them.&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 07 Mar 2016 16:18:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/tsidx-topologycruncy/m-p/236849#M99066</guid>
      <dc:creator>baoctac</dc:creator>
      <dc:date>2016-03-07T16:18:55Z</dc:date>
    </item>
    <item>
      <title>Re: tsidx topologycruncy</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/tsidx-topologycruncy/m-p/236850#M99067</link>
      <description>&lt;P&gt;Can you give the full path to the folder in question please?&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2016 14:32:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/tsidx-topologycruncy/m-p/236850#M99067</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2016-03-08T14:32:01Z</dc:date>
    </item>
    <item>
      <title>Re: tsidx topologycruncy</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/tsidx-topologycruncy/m-p/236851#M99068</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;
The full path is /opt/splunk/var/lib/splunk/tsidxstats/topologyCronSearch&lt;/P&gt;

&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2016 14:34:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/tsidx-topologycruncy/m-p/236851#M99068</guid>
      <dc:creator>baoctac</dc:creator>
      <dc:date>2016-03-08T14:34:22Z</dc:date>
    </item>
    <item>
      <title>Re: tsidx topologycruncy</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/tsidx-topologycruncy/m-p/236852#M99069</link>
      <description>&lt;P&gt;These are coming from a tscollect command in one of your saved searches.&lt;/P&gt;

&lt;P&gt;The saved search is probably called "topologyCronSearch".&lt;/P&gt;

&lt;P&gt;To remove them, delete the saved search and restart OR disable the saved search and manually delete them from the file system.  You should make sure you're not using anything related to the search first though.   Most likely, Somewhere there is another search that's looking at these files.  Removing the files will cause tstats commands that rely on them to begin failing.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2016 18:38:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/tsidx-topologycruncy/m-p/236852#M99069</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2016-03-08T18:38:13Z</dc:date>
    </item>
    <item>
      <title>Re: tsidx topologycruncy</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/tsidx-topologycruncy/m-p/236853#M99070</link>
      <description>&lt;P&gt;Awesome! Thanks jkat54. I found a reference under a saved search with the reference  to 'namespace=topologyCronSearch'. looks like this search (called Config: Topology Data Generator) was set up alongside the Splunk App for AWS App. &lt;/P&gt;</description>
      <pubDate>Thu, 10 Mar 2016 17:25:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/tsidx-topologycruncy/m-p/236853#M99070</guid>
      <dc:creator>baoctac</dc:creator>
      <dc:date>2016-03-10T17:25:49Z</dc:date>
    </item>
    <item>
      <title>Re: tsidx topologycruncy</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/tsidx-topologycruncy/m-p/236854#M99071</link>
      <description>&lt;P&gt;if this answered your question, please 'accept' it &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Mar 2016 18:50:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/tsidx-topologycruncy/m-p/236854#M99071</guid>
      <dc:creator>piebob</dc:creator>
      <dc:date>2016-03-10T18:50:30Z</dc:date>
    </item>
    <item>
      <title>Re: tsidx topologycruncy</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/tsidx-topologycruncy/m-p/236855#M99072</link>
      <description>&lt;P&gt;Done. Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 10 Mar 2016 18:57:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/tsidx-topologycruncy/m-p/236855#M99072</guid>
      <dc:creator>baoctac</dc:creator>
      <dc:date>2016-03-10T18:57:12Z</dc:date>
    </item>
  </channel>
</rss>

