<?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: netapp-harvest capacity metrics for cDOT 8.3.x in Active IQ Unified Manager Discussions</title>
    <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/netapp-harvest-capacity-metrics-for-cDOT-8-3-x/m-p/119433#M21341</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.netapp.com/t5/user/viewprofilepage/user-id/7599"&gt;@madden﻿&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks for your detailed reply. The original reason behind my question was to be sure I need to set up OCUM to get the storage capacity metrics, so you clearly replied yes &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; What you wrote is sensible, especially about avoiding the extra collection load on the cluster. Given that OCUM adds value to monitoring and to the infrastructure in general, I will go on and set it up. Thank you!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Federico&lt;/P&gt;</description>
    <pubDate>Thu, 19 May 2016 13:01:21 GMT</pubDate>
    <dc:creator>fede_melaccio</dc:creator>
    <dc:date>2016-05-19T13:01:21Z</dc:date>
    <item>
      <title>netapp-harvest capacity metrics for cDOT 8.3.x</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/netapp-harvest-capacity-metrics-for-cDOT-8-3-x/m-p/119377#M21320</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am interested in enabling storage capacity metrics on harvest for clustered DOT 8.3.x systems. Is this possible by polling the OnCommand Unified Manager only? Is there any other option? Thanks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best&lt;/P&gt;&lt;P&gt;Federico&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 20:54:36 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/netapp-harvest-capacity-metrics-for-cDOT-8-3-x/m-p/119377#M21320</guid>
      <dc:creator>fede_melaccio</dc:creator>
      <dc:date>2025-06-04T20:54:36Z</dc:date>
    </item>
    <item>
      <title>Re: netapp-harvest capacity metrics for cDOT 8.3.x</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/netapp-harvest-capacity-metrics-for-cDOT-8-3-x/m-p/119416#M21334</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.netapp.com/t5/user/viewprofilepage/user-id/49576"&gt;@fede_melaccio﻿&lt;/a&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Harvest supports capacity monitoring exclusively via&amp;nbsp;OCUM. &amp;nbsp;I made this choice because:&lt;/P&gt;&lt;P&gt;1) Everyone should use&amp;nbsp;OCUM. &amp;nbsp;It provides monitoring, trending, alerting, and more, at&amp;nbsp;no additional cost.&lt;/P&gt;&lt;P&gt;2) Reduce collection load on the cluster. &amp;nbsp;Since OCUM is already collecting&amp;nbsp;and storing the data&amp;nbsp;we can avoid any additional collection load on the cluster.&lt;/P&gt;&lt;P&gt;3) Time; I only have so much to implement things &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am working on another feature (mapping vols under&amp;nbsp;aggrs, in addition to vols under svms as today) but this&amp;nbsp;will also require OCUM. &amp;nbsp;So if you can let me know why you don't want to use OCUM that would be helpful for me to understand.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers,&lt;BR /&gt;Chris Madden&lt;/P&gt;&lt;P&gt;Storage Architect, NetApp EMEA (and author of Harvest)&lt;/P&gt;&lt;P&gt;Blog:&amp;nbsp;&lt;A href="http://blog.pkiwi.com/" target="_blank"&gt;It all begins with data&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;If this post resolved your issue, please help others by selecting&amp;nbsp;&lt;STRONG&gt;ACCEPT AS SOLUTION&lt;/STRONG&gt;&amp;nbsp;or adding a&amp;nbsp;&lt;STRONG&gt;KUDO &lt;/STRONG&gt;or both!&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2016 18:19:25 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/netapp-harvest-capacity-metrics-for-cDOT-8-3-x/m-p/119416#M21334</guid>
      <dc:creator>madden</dc:creator>
      <dc:date>2016-05-18T18:19:25Z</dc:date>
    </item>
    <item>
      <title>Re: netapp-harvest capacity metrics for cDOT 8.3.x</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/netapp-harvest-capacity-metrics-for-cDOT-8-3-x/m-p/119433#M21341</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.netapp.com/t5/user/viewprofilepage/user-id/7599"&gt;@madden﻿&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks for your detailed reply. The original reason behind my question was to be sure I need to set up OCUM to get the storage capacity metrics, so you clearly replied yes &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; What you wrote is sensible, especially about avoiding the extra collection load on the cluster. Given that OCUM adds value to monitoring and to the infrastructure in general, I will go on and set it up. Thank you!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Federico&lt;/P&gt;</description>
      <pubDate>Thu, 19 May 2016 13:01:21 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/netapp-harvest-capacity-metrics-for-cDOT-8-3-x/m-p/119433#M21341</guid>
      <dc:creator>fede_melaccio</dc:creator>
      <dc:date>2016-05-19T13:01:21Z</dc:date>
    </item>
  </channel>
</rss>

