<?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 Splunk REST Storage Endpoints - Clarification in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-REST-Storage-Endpoints-Clarification/m-p/471740#M81054</link>
    <description>&lt;P&gt;Hey Answers,&lt;/P&gt;
&lt;P&gt;I have an endpoint question if anyone has the knowledge to enlighten me.&lt;/P&gt;
&lt;P&gt;I have a client that was designing searches for an admin dashboard and crafted two based on existing monitoring console one to determine amount of space used in their storage:&lt;/P&gt;
&lt;P&gt;One is trying to determine free disk space on a partition and is referencing /services/server/status/partitions-space.&lt;BR /&gt;The result is that they’re using 7.5 TB of their 8 TB’s in the drive.&lt;/P&gt;
&lt;P&gt;The other is trying to determine free index space and is referencing /services/data/index-volumes.&lt;BR /&gt;The result of that one is that they’re using 5.2 TB of their 8 TB’s in the drive.&lt;/P&gt;
&lt;P&gt;When I log on to the server and do a “df -h”, that drive says it’s using 5.3TB of 8TB allocated, so it seems like the “index-volumes” one is correct, but he’s wondering what the “partitions-space” one is looking at then and where that extra data is coming from.&lt;/P&gt;
&lt;P&gt;I’m stumped as I thought that it would be “partitions-space” being hardware level storage and “index-volumes” being the Splunk related storage. Any insight into what the partitions-space one might be doing differently?&lt;/P&gt;
&lt;P&gt;Thanks so much,&lt;BR /&gt;Austin&lt;/P&gt;</description>
    <pubDate>Sat, 06 Jun 2020 23:23:40 GMT</pubDate>
    <dc:creator>AustinAlbrecht</dc:creator>
    <dc:date>2020-06-06T23:23:40Z</dc:date>
    <item>
      <title>Splunk REST Storage Endpoints - Clarification</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-REST-Storage-Endpoints-Clarification/m-p/471740#M81054</link>
      <description>&lt;P&gt;Hey Answers,&lt;/P&gt;
&lt;P&gt;I have an endpoint question if anyone has the knowledge to enlighten me.&lt;/P&gt;
&lt;P&gt;I have a client that was designing searches for an admin dashboard and crafted two based on existing monitoring console one to determine amount of space used in their storage:&lt;/P&gt;
&lt;P&gt;One is trying to determine free disk space on a partition and is referencing /services/server/status/partitions-space.&lt;BR /&gt;The result is that they’re using 7.5 TB of their 8 TB’s in the drive.&lt;/P&gt;
&lt;P&gt;The other is trying to determine free index space and is referencing /services/data/index-volumes.&lt;BR /&gt;The result of that one is that they’re using 5.2 TB of their 8 TB’s in the drive.&lt;/P&gt;
&lt;P&gt;When I log on to the server and do a “df -h”, that drive says it’s using 5.3TB of 8TB allocated, so it seems like the “index-volumes” one is correct, but he’s wondering what the “partitions-space” one is looking at then and where that extra data is coming from.&lt;/P&gt;
&lt;P&gt;I’m stumped as I thought that it would be “partitions-space” being hardware level storage and “index-volumes” being the Splunk related storage. Any insight into what the partitions-space one might be doing differently?&lt;/P&gt;
&lt;P&gt;Thanks so much,&lt;BR /&gt;Austin&lt;/P&gt;</description>
      <pubDate>Sat, 06 Jun 2020 23:23:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-REST-Storage-Endpoints-Clarification/m-p/471740#M81054</guid>
      <dc:creator>AustinAlbrecht</dc:creator>
      <dc:date>2020-06-06T23:23:40Z</dc:date>
    </item>
  </channel>
</rss>

