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" |
| start | 1465569000000 |
| end | 1465578000000 |
| current | 120 |
| min | 72 |
| max | 520 |
| avg | 297.3866566151527 |
| sum | 3152 |
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