#Cloud Insights vs Harvest-nabox?

1 messages · Page 1 of 1 (latest)

near ether
#

I know what Cloud Insights can do for us.
But can somebody please elaborate what it can do but Harvest-NAbox cannot do for us or vise versa?
Thank you!

somber cloak
#

In my opinion CI has better alerting and reporting features, you cannot make complex reports just with harvest. Of course, CI isn’t just NetApp but all storage vendors, VMware and kubernetes monitoring. CI engine also is smarter with when to alert and doesn’t just consider threshold as a trigger, but trends from previous behaviors.
Only CI can provide end to end monitoring from vmdk to the LUN for better troubleshooting.

near ether
#

I am interested in more on NetApp products and VMware.
So, anything like what Harvest-NAbox can do better than CI?

somber cloak
#

Harvest goes much deeper in performance metrics delivered out of the box, and is targeted towards more tech-savvy storage admins or partners.
It is also more customisable so it's possible to add things that are not in the stock configuration, as long as you have a way to retrieve it from the clusters.
Finally, Grafana is pretty much unchallenged in the open source space when it comes to build detailed custom dashboards, that's an area where CI will be limited if you stick to the dashboard area (reports are much more powerful, but they are not real-time).

lusty cedar
#

The one thing I read in here that I could use a bit of clarification on is:

Only CI can provide end to end monitoring from vmdk to the LUN for better troubleshooting.

I am a bit new to NetApp, my storage experience is typically in object storage and my observability experience is mostly Elasticsearch/Kibana, Sysdig, Nagios/Sysdig.

Can you not monitor from vmdk to the LUN using harvest?

lusty cedar
#

Also, could we control how long data is stored with using harvest b/c we presumably own the storage or TSDB we're using?

tranquil brook
#

yes, you can control the data retention

somber cloak
#

No you can't

#

😄

#

My "no you can't" is for monitoring the whole stack vmdk to LUN, that's typically where CI (DII now) shines, it can show you the full data path and do incident analysis based on that, as well as change monitoring

tranquil brook
#

FWIW there is nothing that prevents Harvest from adding a vmware collector. No one has asked for that so it hasn't been prioritized. If you're interested in Harvest including that feature please create a feature request with the details https://github.com/NetApp/harvest/issues

somber cloak
#

That's true, and there is also vmware collectors already available that you can stitch together, but you still get better integration with DII, wouldn't you agree ?