Hi @fede_melaccio
Harvest supports capacity monitoring exclusively via OCUM. I made this choice because:
1) Everyone should use OCUM. It provides monitoring, trending, alerting, and more, at no additional cost.
2) Reduce collection load on the cluster. Since OCUM is already collecting and storing the data we can avoid any additional collection load on the cluster.
3) Time; I only have so much to implement things 🙂
I am working on another feature (mapping vols under aggrs, in addition to vols under svms as today) but this will also require OCUM. So if you can let me know why you don't want to use OCUM that would be helpful for me to understand.
Cheers,
Chris Madden
Storage Architect, NetApp EMEA (and author of Harvest)
Blog: It all begins with data
If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO or both!