Unsolved
This post is more than 5 years old
522 Posts
0
1013
REST API Date/Time question
Hi, I was curious if someone might be able to point me in the right direction in case I am doing something wrong with some collection through REST. I have the following command:
/api/json/v2/types/performance?cluster-index=1&entity=Volume&prop=wr_latency&prop=rd_latency&prop=wr_iops&prop=rd_iops&granularity=raw&from-time=2016-11-30+23%3A25%3A30&to-time=2016-11-30+23%3A30%3A30
(I removed the https://IP from the command since the ECN page destroys the link)
but while the output shows some readable output for the categories, there is nothing populate for the values:
{
"counters": [],
"members": [
"timestamp",
"guid",
"name",
"index",
"wr_latency",
"rd_latency",
"wr_iops",
"rd_iops"
],
So I was curious if anyone more savvy with REST might spot something I am doing wrong with the command - admittedly I am not very confident in the date/time being provided.
thanks!
huj1
15 Posts
0
November 30th, 2016 16:00
Hi, may I know your XMS version?
echolaughmk
522 Posts
0
December 1st, 2016 08:00
Sure - I am trying with 2 different versions: 4.2 and 4.0.2.80
I think I have played with it enough to narrow down the question that seems to be breaking - Is "raw" a supported granularity for the properties above?
I can get the command to work after figuring out the from-time and to-time when I use a granularity of "one_hour", but when I use "raw" it just crashes and never responds, so maybe that isn't supported?
granularity=one_hour&from-time= 2016-11-30 15:20:00&to-time= 2016-11-30 18:20:00 - this works
granularity=raw&from-time= 2016-11-30 15:20:00&to-time= 2016-11-30 18:20:00 - this always crashes or returns garbage/errors
thanks!
huj1
15 Posts
0
December 1st, 2016 15:00
Hi, it do support raw but I assume there is another issue impacted this function.
May I know if there any way to get a dossier log?
echolaughmk
522 Posts
0
December 2nd, 2016 05:00
Hi,
Thanks for the help. I have opened a case since I played with it much more and it looks like the command works on all versions except for the latest 4.2.1 version. I was incorrect in my assumption of 4.2 above, so this seems like the command works (I had to run a few attempts but got it to work), however it works only on versions prior to 4.2.1 (.15) code so I'll respond to this thread with the outcome for everyone to be aware of.
thanks!
-Keith