Data ONTAP 7-Mode Qtree Tracking Quotas - Does it Work on the Volume's Root?

Data ONTAP 7-Mode is still out there, still being used in the enterprise, and still a valid topic for a blog post.

I needed to find out if 7-mode qtree tracking quotas also track consumption in the '-' qtree (root of the volume) and discovered the answer is 'no'. Still, things that don't work make as good a blog post as things that work (we need things that don't work to appreciate things that do work,) so here we go:

I set up my lab 7-mode system as so.

1) Check DNS is configured:

fas01> rdfile /etc/resolv.conf

2) Run CIFS Setup:

fas01> cifs setup

3) Create a couple of volumes:

fas01> vol create vol1 -l en -s none aggr1 10g
fas01> vol create vol2 -l en -s none aggr1 20g

4) Create a couple of qtrees on vol2:

fas01> qtree create /vol/vol2/aqtree
fas01> qtree create /vol/vol2/bqtree

5) Create 4 CIFS shares:

fas01> cifs shares -add vol1 /vol/vol1
fas01> cifs shares -add vol2 /vol/vol2
fas01> cifs shares -add aqtree /vol/vol2/aqtree
fas01> cifs shares -add bqtree /vol/vol2/bqtree

6) See the quotas file is empty:

fas01> rdfile /etc/quotas

7) Populate (see image below):

• /vol/vol1 with 3 * 45MBfile
• /vol/vol2/aqtree with 1 * 45MBfile
• /vol/vol2/bqtree with 2 * 45MBfile

8) Configure volume tracking quotas and enable:

fas01> wrfile -a /etc/quotas * tree@/vol/vol1 - - - - -
fas01> wrfile -a /etc/quotas * tree@/vol/vol2 - - - - -
fas01> quota on /vol/vol1
fas01> quota on /vol/vol2
fas01> quota status

9) Run quota report.

And when I run the quota report we don't have any knowledge of what's in the root of the volume.

fas01> quota report
                          K-Bytes   
Type  ID   Volume   Tree  Used      Quota Specifier
---- ---- ------- ------- --------- ---------------
tree    *    vol1       -         0 *
tree    *    vol2       -         0 *
tree    1    vol2  aqtree     45720 /vol/vol2/aqtree
tree    2    vol2  bqtree     91440 /vol/vol2/bqtree

VVOLs, Oracle Database, Performance, and ONTAP – Some Research Links

Below are some research links and notes I jotted down regards the topic of, VVOLs, Oracle Database, Performance, and ONTAP. I should strongly point out that I am not an Oracle expert, I am also not particularly expert on many other things too! This is just my way of getting some thoughts and ideas together.

1) [VVOLs & Oracle] A Cracking VMware Whitepaper:

Virtualizing Oracle Workloads with VMware vSphere Virtual Volumes on VMware Hybrid Cloud | REFERENCE ARCHITECTURE
https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/whitepaper/solutions/oracle/vmware-oracle-on-virtual-volumes.pdf

From a performance perspective I didn't get much from this whitepaper, but it is great that it exists, since it validates an Oracle on VVOLs approach.

2) [Oracle & Performance & ONTAP] Words of Steiner:

Jeffrey Steiner is the Oracle on ONTAP king. I couldn't find anything relating to VVOLs on his blog but there is this:

NetApp NVMe for your database
https://words.ofsteiner.com/2018/08/24/netapp-nvme-for-your-database/

Down the bottom of the post he presents some statistics from an actual AWR report, and you see what NVMe-oF can do.

Alas, VVOLs are not currently supported on NVMe-oF as per:
Requirements and Limitations of VMware NVMe Storage

3) [Oracle & Performance] Oracle AWR:

I know little about Oracle AWR, but this PDF slide-deck looks very interesting:

Oracle: Using Automatic Workload Repository for Database Tuning: Tips for Expert DBAs
https://www.oracle.com/technetwork/database/manageability/diag-pack-ow09-133950.pdf

4) [VVOLs & Performance & ONTAP] NetApp Verified Architecture:

NetApp Verified Architectures are always worth a look. No Oracle is this NVA, but a little about VVOLs, a little about performance, and of course a big bit about ONTAP.

Modern SAN Cloud-Connected Flash Solution: NetApp, VMware, and Broadcom Verified Architecture Design Edition: With MS Windows Server 2019 and MS SQL Server 2017 Workloads
https://www.netapp.com/pdf.html?item=/media/9222-nva-1145-design.pdf

The '4.5 Workload Design' section talks about:
“We used the 3SB tool to create an 800GB SQL Server database. We spread the database across five 200GB VMDK files, and one additional 200GB VMDK to handle the database log activity. For the FCP environment, we deployed six 250GB LUNs on each of the 14 SQL Server hosts. We created one LUN per volume and one VMDK per LUN. For the NVMe/FC environment, we created three 1.46TB namespaces per SQL Server host, but used two VMDKs per namespace.”

The '5.1 Test Methodology' section talks about:
“As ONTAP systems are designed for multiple workloads and tenants, best performance is obtained when at least four FlexVol volumes are used per node.”

5) [Performance & ONTAP] Justin Parisi:

There are a few important things to understand about ONTAP & Performance, this is covered well by Justin Parisi in these links:

Volume Affinities: How ONTAP and CPU Utilization Has Evolved
https://blog.netapp.com/volume-affinities-how-ontap-and-cpu-utilization-has-evolved/

NetApp ONTAP FlexGroup Volumes: Top Best Practices: TR-4571-a
https://www.netapp.com/pdf.html?item=/media/17251-tr4571a.pdf

NetApp ONTAP FlexGroup Volumes: Best Practices and Implementation Guide: TR-4571
https://www.netapp.com/pdf.html?item=/media/12385-tr4571pdf.pdf

A couple of extracts:

“In ONTAP 9.4 and later (high-end platforms):
- Each volume has one affinity.
- Each aggregate has eight affinities
- Nodes have a maximum of 16 affinities.
One member volume per available affinity is created. In ONTAP 9.4 and later, up to 16 member volumes per node are created in a FlexGroup volume.”

“To support concurrent processing, ONTAP assesses its available hardware at startup and divides its aggregates and volumes into separate classes called affinities. In general terms, volumes that belong to one affinity can be serviced in parallel with volumes that are in other affinities. In contrast, two volumes that are in the same affinity often must take turns waiting for scheduling time (serial processing) on the node’s CPU.”

6) [VVOLs & ONTAP] Rebalancing VVOLs Datastores:

This link has good info in:

Rebalancing vVols datastores
https://docs.netapp.com/vapp-98/index.jsp?topic=%2Fcom.netapp.doc.vsc-iag%2FGUID-C9FEA419-BDDF-4B9B-837C-0D64CC136FA3.html

“All vVols associated with a virtual machine are moved to the same FlexVol volumes”

7) [VVOLs & ONTAP] Flexpod Design Guides:

Flexpod desing guides are always useful because of the high amount of technical detail. Not particularly useful for my research but there is a bit of VVOLs on ONTAP in here:

FlexPod Datacenter with VMware vSphere 7.0 and NetApp ONTAP 9.7
https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/UCS_CVDs/fp_vmware_vsphere_7_0_ontap_9_7.html

SUMMARY / CONCLUSION

From this little bit of research, sonething becomes apparent. If you're after the most extreme Oracle performance you can get, then VVOLs are not going to be the best option:

1) VVOLs are not supported by VMware on NVMe-oF, so you can't benefit from NVMe-oF.
2) All VVOLs associated with a virtual machine are in the same FlexVol, so you can't benefit from using multiple volume affinities.

So you need to ask yourself, is the performance you get from your Oracle on VVOLs testing sufficient for your needs?
If it is then excellent, if not then don't use VVOLs and instead benefit from NVMe-oF and spreading your workload over multiple volume and aggregate affinities.

PS: "Vdbench is a command line utility specifically created to help engineers and customers generate disk I/O workloads to be used for validating storage performance and storage data integrity. Vdbench execution parameters may also specified via an input text file.":
https://www.oracle.com/downloads/server-storage/vdbench-downloads.html

PPS: Something also to bear in mind from this NetApp Documentation:
Unified Manager 9.7 Documentation Center (netapp.com)
"When there is minimal user activity in the resource, the available IOPS value is calculated assuming a generic workload based on approximately 4,500 IOPS per CPU core."

Being Realistic about IT Automation Benefits

I'm a massive fan of IT Automation and I really enjoy doing it (especially the coding part), but at the same time I am realistic about the benefit of it.

I think there was a quote “if you do anything more than twice (in IT) automate it”. This is a fine thing to say, and yes, in an ideal world where you have the time to invest to automate all your tasks, it makes 100% sense, but in the real world it does not necessarily make sense.

My point is best illustrated with an example.

Example:

Say I have a manual task, this manual task takes up 10 minutes of my time, and I have to do it every week. So that's 520 minutes a year.

Now, say my manager says “you must automate it”. Okay fine. But how much time do I need to invest in automating this process.

Say it takes me 40 hours to automate this process (2400 minutes). That means that to start saving time, it's got to have run for over 4.5 years (2400/520). And that's not considering the fact that the automation might need updating in that time, constant monitoring that it runs, troubleshooting when it doesn't...

My point is this:

When considering automating something, also consider the investment in time in creating that automation, and when you will start to see time savings from that automation. Unfortunately this seems to get forgotten in the drive to “automate everything”.

Q: How much time is being spent creating the automation?
Q: When will you actually start saving time from the automation?

Some automations will never save time. Still, a benefit in going through the process of automating something that will never save time, is that potentially you develop tools and methods that can be used to automate something of more value in the future, and that thing will have clear time saving benefits.

Don't get me wrong though, there are massive benefits to be had in IT automation. Some task that regularly needs to happen is a perfect candidate for automation. Or a particularly complex task that won't happen often, but when it does happen you don't want it go wrong (like a Disaster Recovery workflow), is also a good candidate for automation. And many other cases...

DevOps Doesn't Work With Everything

I also think some people are getting too caught up with the word “DevOps”. DevOps is great for software that needs/benefits from constant evolution. But for a write once and forget application, there's really little point in shoe-horning it into a DevOps process, it just complicates things and wastes time.

End of ramble.

Using the OCI DWH to Calculate Storage Efficiency Figures

The following post details an SQL query that you can use to get Storage Efficiency figures per aggregate (storage pool) for your NetApp ONTAP systems (both Clustered ONTAP and 7-Mode), from the NetApp OnCommand Insight Data Warehouse.

These figures should be pretty close to what you see in ActiveIQ - they won't be perfect but close. You need to remember:

1. We have compaction figure at an aggregate level - potentially could be different compaction ratio for different internal volumes.
2. We have deduplication and compression ratio for the whole internal volume and not just the dataUsed bit (data used not including snapshot) - potentially could have different ratios for the dataUsed bit and the snapshot bit.

Image: NetApp Active IQ > Capacity and Efficiency > Storage Efficiency > Node > Savings without Snapshot Backups

The SQL Query

SELECT

*,

`Logical Used MB`/`Physical Used MB` AS 'Storage Efficiency'

FROM(

 SELECT

 CASE

  WHEN s.`microcodeVersion` like '%7-Mode' THEN '7-Mode'

  WHEN s.`microcodeVersion` like '%ONTAP' THEN 'ONTAP'

  ELSE 'UNKNOWN'

 END AS 'Mode',

 spd.storageName AS 'Storage',

 spd.name AS 'Aggregate',

 COUNT(*) AS 'Vol Count',

 SUM(i.dataUsedCapacityMB) AS 'DataUsed Minus Snapshots MB',

 FLOOR(SUM(i.dataUsedCapacityMB) * COALESCE(spcf.compactionRatio,1)) AS 'Physical Used MB',

 FLOOR(SUM(

  CASE

   WHEN i.`dedupeRatio` IS NOT NULL AND i.`compressionRatio` IS NOT NULL

    THEN

     CASE

      WHEN s.`microcodeVersion` like '%7-Mode'

       THEN (i.`dataUsedCapacityMB` * 1/(i.`dedupeRatio` * i.`compressionRatio`))

      ELSE (i.`dataUsedCapacityMB` * 1/(i.`dedupeRatio` + i.`compressionRatio` -1))

     END

   WHEN i.`dedupeRatio` IS NOT NULL THEN (i.`dataUsedCapacityMB` * 1/(i.`dedupeRatio`))

   WHEN i.`compressionRatio` IS NOT NULL THEN (i.`dataUsedCapacityMB` * 1/(i.`compressionRatio`))

   ELSE i.`dataUsedCapacityMB`

  END)) AS 'Logical Used MB'

 FROM dwh_capacity.internal_volume_capacity_fact AS i

 JOIN dwh_capacity.date_dimension AS dd ON dd.tk = i.dateTk

 JOIN dwh_capacity.storage_pool_dimension AS spd ON spd.tk = i.storagePoolTk

 JOIN dwh_capacity.storage_and_storage_pool_capacity_fact AS spcf ON i.storagePoolTk = spcf.storagePoolTK AND i.dateTk = spcf.dateTk

 JOIN dwh_capacity.storage_dimension AS s ON s.tk = spcf.storageTk

 WHERE dd.latest = 1

 AND s.manufacturer = 'NetApp'

 GROUP BY i.storagePoolTk

) AS t0

-- TRY TO REMOVE ROOT AGGRS --

WHERE `Vol Count` > 1

AND `Aggregate` NOT LIKE '%_ROOT'

What does the Unified VSC WebCLI 'container rebalance' do?

Update: This post was written before I got my hands on ONTAP Tools for VMware vSphere 9.8.

Rebalancing vVols datastores

The 9.8 release of ONTAP tools supports a command to rebalance FlexVol volumes in your datacenter. The main goal is to enable even space utilization among FlexVol volumes. ONTAP tools redistributes vVols among existing volumes based on space usage, thin provisioning, LUN count, and storage capability profiles.

The rebalancing of vVols datastore is performed by LUN move or file move.

https://docs.netapp.com/vapp-98/topic/com.netapp.doc.vsc-iag/GUID-C9FEA419-BDDF-4B9B-837C-0D64CC136FA3.html

---------------

vVols Virtual Machines on NetApp ONTAP – What LUNs are created?

This post illustrates the LUNs created when using the NetApp Virtual Storage Console for VMware.

Prior to our vVol datastore and vVol VMs setup, we have the following LUNs and igroups which will be ignored for the rest of the post.

cluster1::> lun show
Vserver Path State Mapped Type Size
------- ---------------- ------ ------ ------ ----
svm1 /vol/iscsi/iscsi online mapped vmware 20GB

cluster1::> igroup show
Vserver Igroup Protocol OS Type Initiators
------- --------- -------- ------- ---------------------------
svm1 initgroup iscsi vmware iqn.1998-01.com.vmware:esx1
iqn.1998-01.com.vmware:esx2
svm1 sql iscsi windows -

One notable thing is that we have 2 * ESXi hosts in our lab VMware cluster.

Creating a vVol Datastore

After creating a Storage Capability Profile, we create a vVol datastore consisting of 3 Flexvols using the NetApp VSC for Vmware (vSphere plugin).

Image: New vVol Datastore Creation with 3 Flexvols


And we see the following LUNs and igroup.

cluster1::> lun show
Vserver Path State Mapped Type Size
------- ---- ----- ------ ---- ----
svm1 /vol/iscsi_Vvol_fv1/vvolPE-1615496750216 online mapped vmware 4MB
svm1 /vol/iscsi_Vvol_fv2/vvolPE-1615496750200 online mapped vmware 4MB
svm1 /vol/iscsi_Vvol_fv3/vvolPE-1615496750216 online mapped vmware 4MB

cluster1::> igroup show
Vserver Igroup Protocol OS Initiators
------- ------ -------- -- ----------
svm1 vvol-igroup-1 iscsi vmware iqn.1998-01.com.vmware:esx1,iqn.1998-01.com.vmware:esx2

3 * Protocol Endpoint LUNs (1 per flexvol in our vVol datastore.)
The newly created vvol igroup has our 2 * ESXi hosts in, and this will be the same for the rest of this walkthrough.

Creating our first vVol VM

Now we create our first vVol VM, and see what LUNs we get.

cluster1::> lun show
Vserver Path State Mapped Type Size
------- ---- ----- ------ ---- ----
svm1 /vol/iscsi_Vvol_fv1/naa.600a0980774f6a344d2446434f4f7a7a.vmdk online - vmware 4GB
svm1 /vol/iscsi_Vvol_fv1/naa.600a0980774f6a344d2446434f503030.vmdk online - vmware 1.50GB
svm1 /vol/iscsi_Vvol_fv1/vvolPE-1615496750216 online mapped vmware 4MB
svm1 /vol/iscsi_Vvol_fv2/vvolPE-1615496750200 online mapped vmware 4MB
svm1 /vol/iscsi_Vvol_fv3/vvolPE-1615496750216 online mapped vmware 4MB

At this point the VM is not powered on:

• The 4GB LUN ending f7a7a.vmdk holds the VM's files.
• The 1.5GB LUN ending 03030.vmdk is the actual VM's disk drive.

Resizing Disk Drive to 8GB and Powering it On

If we resize the VM's hard disk from 1.5GB to 8GB and power it on (it has 128MB memory) these are the LUNs we now see:

cluster1::> lun show
Vserver Path State Mapped Type Size
------- ---- ----- ------ ---- ----
svm1 /vol/iscsi_Vvol_fv1/naa.600a0980774f6a344d2446434f4f7a7a.vmdk online - vmware 4GB
svm1 /vol/iscsi_Vvol_fv1/naa.600a0980774f6a344d2446434f503030.vmdk online - vmware 8GB
svm1 /vol/iscsi_Vvol_fv1/vvolPE-1615496750216 online mapped vmware 4MB
svm1 /vol/iscsi_Vvol_fv2/naa.600a0980774f6a344d2446434f503031.vmdk online - vmware 128MB
svm1 /vol/iscsi_Vvol_fv2/vvolPE-1615496750200 online mapped vmware 4MB
svm1 /vol/iscsi_Vvol_fv3/vvolPE-1615496750216 online mapped vmware 4MB

• The 4GB LUN ending f7a7a.vmdk holds the VM's files.
• The 8GB LUN ending 03030.vmdk is the actual VM's disk drive.
• The 128MB LUN ending 03031.vmdk is the memory swap LUN.

Interesting to notice that none of these vVol VM LUNs say mapped!

Image: vVol Virtual Machine Files in the f7a7a.vmdk LUN


Skipping Ahead to 5 * vVol VMs

Now we skip ahead to where we have 5 * vVol Vms, of which 4 are powered on. And one of the VMs has had it's memory upped to 12GB.

Image: 5 * vVol VMs


cluster1::> lun show
Vserver Path State Mapped Type Size
------- ---- ----- ------ ---- ----
svm1 /vol/iscsi_Vvol_fv1/naa.600a0980774f6a344d2446434f4f7a7a.vmdk online - vmware 4GB
svm1 /vol/iscsi_Vvol_fv1/naa.600a0980774f6a344d2446434f50302d.vmdk online - vmware 5GB
svm1 /vol/iscsi_Vvol_fv1/naa.600a0980774f6a344d2446434f503030.vmdk online - vmware 8GB
svm1 /vol/iscsi_Vvol_fv1/naa.600a0980774f6a344d2446434f503036.vmdk online - vmware 128MB
svm1 /vol/iscsi_Vvol_fv1/naa.600a0980774f6a344d2446434f503037.vmdk online - vmware 128MB
svm1 /vol/iscsi_Vvol_fv1/naa.600a0980774f6a344d2446434f503038.vmdk online - vmware 128MB
svm1 /vol/iscsi_Vvol_fv1/naa.600a0980774f6a344d2446434f503039.vmdk online - vmware 4GB
svm1 /vol/iscsi_Vvol_fv1/vvolPE-1615496750216 online mapped vmware 4MB
svm1 /vol/iscsi_Vvol_fv2/naa.600a0980774f6a344d2446434f503032.vmdk online - vmware 4GB
svm1 /vol/iscsi_Vvol_fv2/naa.600a0980774f6a344d2446434f503033.vmdk online - vmware 6GB
svm1 /vol/iscsi_Vvol_fv2/naa.600a0980774f6a344d2446434f503034.vmdk online - vmware 4GB
svm1 /vol/iscsi_Vvol_fv2/naa.600a0980774f6a344d2446434f503041.vmdk online - vmware 12GB
svm1 /vol/iscsi_Vvol_fv2/naa.600a0980774f6a344d2446434f503042.vmdk online - vmware 4GB
svm1 /vol/iscsi_Vvol_fv2/naa.600a0980774f6a344d2446434f503043.vmdk online - vmware 7.50GB
svm1 /vol/iscsi_Vvol_fv2/vvolPE-1615496750200 online mapped vmware 4MB
svm1 /vol/iscsi_Vvol_fv3/naa.600a0980774f6a344d2446434f503035.vmdk online - vmware 7GB
svm1 /vol/iscsi_Vvol_fv3/vvolPE-1615496750216 online mapped vmware 4MB

Highlighted above we have:

• In green the 5 * VM's files vmdk's.
• In cyan the 5 * VM's disk drives (each VM has 1 disk drive, each is a different size here – 5 , 6, 7, 7.5, 8).
• In yellow the 4 * powered on VM's memory swap LUNs (3 have 128MB memory, the fourth has 12GB memory).

OCI REST API vs CI REST API

Snapshot comparison taken on 7th March 2021.

Image: Cloud Insights API Documentation link: WebUI > Admin > API Access > API Documentation


Similarly to the previous post, another comparison of OCI vs CI. This time we compare the REST API documentation from NetApp OnCommand Insight (OCI) 7.3.10 vs REST API documentation from NetApp Cloud Insights (CI).

I'm getting my list of REST APIs from:
OCI: WebUI > ? > REST API Documentation
CI: WebUI > Admin > API Access > API Documentation

Image: NetApp OCI REST API Documentation link: WebUI > ? > REST API Documentation


There are some additions with CI, with the dwh-management and lake branches being of specific interest:

assets/import
assets/risks
assets/storageVirtualMachines
collector/datasourceTypes
collector/datasources
dwh-management/upload/csvs
lake/ingest/influxdb
lake/metadata
lake/query
lake/telegraf

List of NetApp OnCommand Insight 7.3.10 REST APIs

admin/acquisitionUnits
admin/audits
admin/certificates
admin/datasources
admin/health
admin/ldap
admin/licenses
admin/patches
admin/users
assets/annotations
assets/applications
assets/businessEntities
assets/dataStores
assets/devices
assets/disks
assets/fabrics
assets/fileSystems
assets/genericDevices
assets/hosts
assets/iSCSINetworkPortal
assets/iSCSISessions
assets/internalVolumes
assets/paths
assets/ports
assets/qtrees
assets/quotas
assets/shares
assets/storageNodes
assets/storagePools
assets/storages
assets/switches
assets/tapes
assets/virtualMachines
assets/vmdks
assets/volumes
assets/zoneMembers
assets/zones
identifications/fc
identifications/ip
integrations/agents
integrations/input
login
queries
search

List of NetApp Cloud Insights REST APIs

assets/annotations
assets/applications
assets/dataStores
aasets/device
assets/disks
assets/fabrics
assets/fileSystems
assets/genericDevices
assets/hosts
assets/import
assets/internalVolumes
assets/iSCSINetworkPortals
assets/iSCSISessions
assets/paths
assets/ports
assets/qtrees
assets/quotas
assets/risks
assets/shares
assets/storageNodes
assets/storagePools
assets/storageVirtualMachines
assets/storages
assets/switches
assets/tapes
assets/virtualMachines
assets/vmdks
assets/volumes
assets/zoneMembers
assets/zones
collector/datasourceTypes
collector/datasources
dwh-management/upload/csvs
lake/ingest/influxdb
lake/metadata
lake/query
lake/telegraf
queries
search

OCI Data Sources vs CI Data Collectors

Snapshot comparison taken on 3rd March 2021

A comparison of NetApp OnCommand Insight (OCI) Data Sources vs NetApp Cloud Insights (CI) Data Collectors. Here I’m getting my list of:

• OCI Data Sources from an OCI 7.3.10 SP 9 WebUI > Admin > Data sources > + Add 
• CI Data Collectors from the Cl WebUI > Admin > Data Collectors > Add Data Collector 

Image: Cloud Insights Data Collectors (click to enlarge)

OnCommand Insight Data Sources (65)

3Par - InServ

Amazon - AWS Cloud Cost

Amazon - AWS EC2

Amazon - AWS S3

Brocade - Brocade Network Advisor

Brocade - Enterprise Fabric Connectivity Manager

Brocade - FC Switch Firmware 4.2+

Brocade - Sphereon / Intrepid Switch (SNMP)

Ceph - Ceph

Cisco - FC Switch Firmware 2.0+

Dell - Compellent (API)

EMC - Atmos

EMC - Celerra

EMC - Centera Viewer

EMC - Clariion

EMC - Data Domain

EMC - ECC StorageScope

EMC - ECS

EMC - Isilon

EMC - RecoverPoint

EMC - ScaleIO

EMC - Solutions Enabler with Performance

EMC - VNX

EMC - VNXe

EMC - VPLEX

EMC - Xtremio

Fujitsu - Eternus

Generic Device - Generic DB Host Resolver

Generic Device - Generic File System Level Utilization

HDS - HCP

HDS - HNAS

HDS - HiCommand Device Manager

HDS - HiCommand Device Manager Lite

HP - Command View AE

HP - Command View AE Lite

HP - EVA Storage (SSSU)

HPE - Nimble Storage

HUAWEI - OceanStor

IBM - Cleversafe

IBM - DS

IBM - PowerVM

IBM - SVC

IBM - Tivoli Monitoring

IBM - Total Storage DS4000 series

IBM - XIV

Infinidat - InfiniBox

Integration - SNMP

Microsoft - Azure Compute

Microsoft - Azure Government Compute

Microsoft - Azure NetApp Files

Microsoft - Hyper-V

NetApp - Clustered Data ONTAP

NetApp - Data ONTAP 7-Mode

NetApp - E-Series

NetApp - Host and VM File Systems

NetApp - SolidFire

NetApp - StorageGrid

Nutanix - Nutanix Storage

OpenStack - OpenStack

Oracle - ZFS

Pure Storage - FlashArray

Qlogic - FC Switch

Red Hat - RHEV

VMware - vSphere

Violin Memory - Violin 6000 Series

Cloud Insights Data Collectors (85)

Apache

Apache - ActiveMQ

Apache - Zookeeper

AWS - EC2 and EBS

Azure - NetApp Files

Azure - VMs and VHD

Azure Gov - VMs and VHD

Broadcom - Brocade Network Advisor (BNA)

Broadcom - Fibre Channel Switches

Cisco - MDS Fabric Switches

Couchbase

CouchDB

Dell - XC Series

DellEMC - Data Domain

DellEMC - ECS

DellEMC - Isilon

DellEMC - PowerStore

DellEMC - RecoverPoint

DellEMC - ScaleIO

DellEMC - Unity

DellEMC - VMAX/PowerMax Family of Devices

DellEMC - VNX Block Storage

DellEMC - VNX File

DellEMC - VNX Unified

DellEMC - VPLEX

DellEMC - XtremIO

Docker

ElasticSearch

Flink

Fujitsu - Eternus DX

Google Cloud Platform - Compute and Storage

Hadoop

HAProxy

HashiCorp - Consul

Hitachi - Command Suite

Hitachi - Content Platform

Hitachi - NAS Platform

Hitachi - Ops Centera

HPE - 3PAR StoreServ Storage

HPE - Command View

HPE - Nimble Storage

Huawei - OceanStor and Dorado Devices

IBM - Cleversafe

IBM - CS Series

IBM - PowerVM

IBM - SAN Volume Controller (SVC)

IBM - System Storage DS8000 Series

IBM - XIV and A9000 Storages

Infinidat - InfiniBox

Java

Kafka

Kapacitor

Kibana

Kubernetes

Lenovo - HX Series

macOS

Memcached

Microsoft - Hyper-V

MongoDB

MySQL

NetApp - Cloud Volumes ONTAP

NetApp - Cloud Volumes Services for AWS

NetApp - Data ONTAP 7-Mode

NetApp - E-Series

NetApp - HCI Virtual Center

NetApp - ONTAP Data Management Software

NetApp - ONTAP Select

NetApp - SolidFire All-Flash Array

NetApp - StorageGrid

netstat

Nginx

Nutanix - NX Series

OpenStack

OpenZFS

Oracle - ZFS Storage Appliance

PostgreSQL

Puppet

PureStorage - FlashArray

RedHat - Red Hat Virtualization

Redis

RethinkDB

RHEL & CentOS

Ubuntua & Debian

VMware - vSphere

Windows

Think it should be called "Total Cloud Insights" - Public Cloud, Private Cloud, Hybrid Cloud, On Premise - Any Cloud!