Subscribe

OCI REST CDOT NODE PERFORMANCE - STARTTIME ISSUE

Gentlemen,

 

From OCI REST interface I am able to get the performace of nodes, volumes, etc, but found out the default is a week ( avg ). Trying to find out the way to limit the time of the performance response ( to last 3 hours for example ).

 

Links I use to get performance:

https://hoeoci01/rest/v1/assets/storageNodes/[NODE_ID]/performance?expand=history&fromTime=1488454020000&toTime=1493983620000

https://hoeoci01/rest/v1/assets/storageNodes/[NODE_ID]/performance

https://hoeoci01/rest/v1/assets/storageNodes/[NODE_ID]/performance?expand=history&since=THREE_HOURS

 

Does anyone know how to limit the default weekly avg with another timestart without expanding ? ( by expanding you get 15 min datapoints for 1 week !

 

Thanks in advance.

 

 

 

 

Re: OCI REST CDOT NODE PERFORMANCE - STARTTIME ISSUE

 

Trantino -

 

No, and yes...

 

OCI polls C-Mode data sources on 15min intervals

 

Hence you could grab the expanded output and then filter in your code for the 15min samples that you want to use.


I hope this response has been helpful to you.

At your service,

Eugene E. Kashpureff, Sr.
Independent NetApp Consultant http://www.linkedin.com/in/eugenekashpureff
Senior NetApp Instructor, Fast Lane US http://www.fastlaneus.com/
(P.S. I appreciate 'kudos' on any helpful posts.)

Re: OCI REST CDOT NODE PERFORMANCE - STARTTIME ISSUE

I think you can construct a request like:

 

 

https://localhost/rest/v1/assets/storageNodes/27924/performance?fromTime=1465567200000&toTime=1465578000000&expand=default

 

Where you specify the

 

fromtime in Unix *milliseconds* based timestamp, as well as the toTime

 

The expand=default only has performance metrics for the various objects of the thing we are talking about - not the invidual samples the expand=history has.

 

For example, on the demo (sales) database, one of the nodes has

 

latency 
performanceCategory"Latency"
description"Latency"
read 
description"Latency - Read"
unitType"ms"
start1465569000000
end1465578000000
current120
min72
max520
avg297.3866566151527
sum3152

 

You would want to use the "avg" latency for your use case.

 

I hope this helps. This is not my area of expertize, but most of the OCI folks have been travelling to Las Vegas over the last day or two - I am at 36k feet right now myself

 

Matt