Unsolved
46 Posts
0
3237
EMC Xtremio Performance
Hello
We are using the EMC Xtremio Performance queries to gather statistics. Currently we are using below REST API to get the statistics.
However this gives us huge amount of data causing. So to filter this further, I am trying to put time limit instead of getting data for an hour. However below REST API is coming back with "Response code 400, msg : Bad Request"
https://xio01/api/json/v2/types/performance?cluster-name=xio176&entity=Volume&granularity=raw&from-time=2018-05-11 13:26:19&to-time=2018-05-11 13:41:19
https://xio01/api/json/v2/types/performance?cluster-name=xio176&entity=Initiator&granularity=raw&from-time=2018-05-11 13:26:19&to-time=2018-05-11 13:41:19
https://xio01/api/json/v2/types/performance?cluster-name=xio176&entity=Target&granularity=raw&from-time=2018-05-11 13:26:19&to-time=2018-05-11 13:41:19
Also same command with object list does not return any data either for initiator or volume. It works for Target.
E.g below works
https://xio01/api/json/v2/types/performance?cluster-name=xio176&entity=Target&granularity=raw&from-time=2018-05-11 13:26:19&to-time=2018-05-11 13:41:19&obj-list=X1-SC1-target1&obj-list=X1-SC1-target2&obj-list=X1-SC1-target3&obj-list=X1-SC1-target4
But below does not
https://xio01/api/json/v2/types/performance?cluster-name=xio176&entity=Initiator&granularity=raw&from-time=2018-05-11 13:26:19&to-time=2018-05-11 13:41:19&obj-list=mdm1dbq1_0&obj-list=mdm1dbq1_0s&obj-list=mdm2dbq1_1&obj-list=mdm1dbq1_1s
Also the commands seem to be very slow too, e.g below command is taking 2 hrs and comes back with "Response code 400, msg : Bad Request"
https://xio03/api/json/v2/types/performance?cluster-name=xio066&entity=Initiator&granularity=raw&from-time=2018-05-11 15:30:14&to-time=2018-05-11 15:45:14&obj-list=vplex3_e2_b1_fc03&obj-list=vplex3_e3_a1_fc01&obj-list=vplex3_e3_a1_fc03&obj-list=vplex3_e3_b1_fc01
Please can you help why time limit is not working in certain cases? And how can I limit the data.
scotthoward
64 Posts
1
May 20th, 2018 07:00
Given the object names you've listed above, I presume you're attempting to run this against an XtremIO X2 array? Which means you're using at least XMS version 6.0?
I just tried each of the commands you've got above, and they worked as expected (I had to change the dates as they are more than a week old so there was no "raw" data available, but otherwise they were an exact cut-n-paste)
What are you using to make the requests? The date format includes a space, which needs to be "escaped" in the request. Most software will look after this for you, but you can always try replacing the space with %20 (the URL-encoded value for a space) and see if that makes any difference.
As for your question around limiting the data, do you really need the "raw" (5 second) data? If not, you can change the granularity to "one_minute" which will give you around 1/12th as much data. Otherwise, what you're doing using a time is the correct way to do it.
Is the GUI itself functioning correctly? It uses the same REST API to gather it's performance data, so if it's working so should your calls...
artRanade
46 Posts
0
May 30th, 2018 14:00
In addition to my above question, will you be able to tell me if granularity of one_minute would work with &time-frame=last_hour option?
artRanade
46 Posts
0
May 30th, 2018 14:00
Thanks. I will try with %20 with date format. I am wondering why the query with time in it worked for Target. Even that has spaces. Anyways I will give all of them a shot again.
I can change to "one_minute" granularity, but would it give me the performance counters which are cumulative/average or are they point in time?
Is the only difference between granularity = raw and one_minute that samples are taken every 5 seconds vs samples are every min?