There is a utility that comes with Harvest 1.x which you can use to retrieve information about the counters. It's a little bit work, but most of the time you'll get all the details (in Harvest 2.0 we are working on a GUI that will simplify this, but it will take some time to be ready).
First, find out the "object" the counter belongs to (I'll explain that in a minute). Then, run the utility:
Replace HOST, USER and PASSWORD with the IP address, username and password of your cluster (this is used to retrieve the API info), and replace OBJECT with object (e.g. "volume", "system:node", "processor"... ). You should get a list of counters with detailed description.
How to find out the object? Most of the time, you can lookup a counter in Harvests' template. (e.g. "template/default/cdot-9.6.0.conf") and see under which object they are listed. Unfortunately, some counters are cooked by the plugins, so you have to either guess their origin or lookup in the plugin sourcecode. This is the case with the counter "qos_read_io_type" that I see in your screenshot: it is cooked from the counter "read_io_type" from -- I think -- the object "workload_volume". So I would run:
The utility used the parameter "-o" for the "display object list" and got the ext_cache description below. ext_cache: This object lists global WAFL External Cache state information applicable to the entire software subsystem, not specific to a given type of cache. Does the "External Cache" mean Flash Cache (PAM card or NVRAM)?
Is this tool the same as the "statistics catalog object show" command?
I have found a web-site explanation of these counters, the reference as below.
Yes the statistics catalog command will explain the CMA object:instance:counter descriptions. Some counters are not used for customer consumption, and we generally don't have customers poking around in there.
Thanks vachagan_gratian and paul_stejskal for the prompt reply.
We understand that these data are the same as the output by the statistics catalog command, we also learned Harvest-Utility could use to get the metrics list and more information.
We are looking for some counter and index making dashboard to quickly check 1. Hardware health (ex: Interconnect-Switch-Power; Network Port Status; CRC error count ...etc.) 2. Effective performance of health (Is only need to look at volume latency? or any suggested?)
3. Space and performance indicators confirm expansion requirements