Hello Vachagan and thank you for your reply. I have seen this answer already on this forum and it is too general. I'll give you an example. First of all... I use nabox and it contains graphite. I can browse the graphite and I assume that the structure there is the same as I can get from the cli utility, right? So for example
..../node/node01/aggr/data_aggr1/vol_summary/total_ops. I would say that this is IOPS on the backend/aggregate level.
But then we have
..../node/node01/vol_summary/total_ops -here I'm not sure. Is it frontend? Is it the same counter as for the aggr? The graphs put together are almost the same but there are differences. So it looks like to different sets of data.
What iops are combined in total_ops? I can see a lot of ops around - other, read, write, cifs, nfs, cifs_read, cifs_write, nfs3, nvf3_read, ........ endless list of ops scattered around all possible sub categories. Without detailed documentation it is just a mess.
And another confusion
there is a panel in nabox called Node Protocol Backend Drilldown and there is NFS IOPs graph that takes data from
..../node/*/system/nfs_ops .... so the system branch gathers the data from backend??
What I really miss is a document that would describe
..../node/node01/vol_summary/total_ops is the counter for ?total iops on the frontend bla bla? and the command used by harvest to collect the data from netapp storage is <command>
Is there something like that? Because I think there must be something from the guys that wrote/write the harvest.
Thank you in advance for any help that can shed some light to this.