nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Isilon Data Collector - Cloud Insight

Sujata

Hello !!!

In CI, when data collector is NetApp array, I collect performance data by querying on "Internal Volumes" for NAS.

For SAN Volumes I use category - "Volume".

In case of Isilon I do get list of shares when I query Shares but when I query "Internal volumes" I don't get Volume names on which those shares reside, I just get one line entry (that is probably isilon namespace).

Any insights/suggestions, please let me know. I think in case of Isilon may be I have to capture Volume names using different query category?

Thx

Sujata

Find more posts tagged with

Accepted answers

Sujata

Correct. I meant to ask how then CI gathers performance data for Isilon (Share was a wrong term I used).

Should I query then with other category? May be Filesystem level type of query ??

Because at Internal Volume category, it did collect as OneFS. Just one line item.

Thank you

All comments

ostiguy

Isilon "OneFS" - the entire array is just one file system.

All of the shares on an Isilon are on that one file system

Sujata

Thx but then how CI collects performance data for each share.

Because when you query a category Share, you don't see IOPS/Latency and Throughput numbers.

ostiguy

CI doesn't collect share performance for any platform. A folder can be shared, but CI does not inventory individual folders - the share object will have a relationship to an Internal Volume, or possibly a Qtree, but there are no statistics on the folder itself

Sujata

Correct. I meant to ask how then CI gathers performance data for Isilon (Share was a wrong term I used).

Should I query then with other category? May be Filesystem level type of query ??

Because at Internal Volume category, it did collect as OneFS. Just one line item.

Thank you