Hello,

RAW data is available for Target. Null values could be observed if you are running this API call against targets which aren't being utilized (Ex. you have deployed FC only and not specifying "entity-index" or "entity-name" and therefore receiving back iSCSI targets as well; you have not zoned an in initiator to all targets). But if you are driving IO to these targets, you should not see null.

Regarding the second, I am observing the same with real_time. I am checking back with some eng resources and will get back to you.

-Marco

Hi Marco,

I can confirm that all performance values when calling RAW were null, as you say this is expected for the iSCSI targets as we are full FC however FC stats also return null values. This was coming from a cluster running 40,000 IOPS and about 900mb/s so I would  have certainly expected to see some non null data coming back.

Thanks.

Could you send me the exact REST API call you are placing and also the version of your XtremIO array(s)?

Our clusters are running 4.0.2 Build 80

I think this may be a bug. After further testing I can get RAW data points if I drop the filters.

Example REST Call That Return Nulls On Target Object

/api/json/v2/types/performance?cluster-name=CLUSTERNAME&entity=Target&prop=avg__bw&prop=avg__avg_latency&time-frame=last_hour&granularity=raw&limit=20

If you remove the &prop= filters from this call then raw data points are returned. I can not cut and paste into this window or I would share the JSON output.

Do you have any examples on how to use the  time-frame custom_time call?

Thanks.

When you use a limit prop you should avoid getting null, example: api/json/v2/types/performance?entity=Cluster&granularity=raw&limit=1

I have confirmed there is an issue with real_time option, and will get back to you on custom time.