Matt Wringe pointed out an inconsistency in our REST API. We have endpoints for fetching raw data from a single metric. We have endpoints for fetching stats from a single metric. We have endpoints for fetching stats from multiple metrics. We lack endpoints for fetching raw data from multiple metrics.
Given the endpoint changes done for
HWKMETRICS-24, I propose the following new endpoints:
And because the memory concerns that I raised in HWKMETRICS-392, I propose that we return in the response a list of what I will call named data point which would look like:
Each data point object in the list contains an id property which more precisely corresponds to the name portion of a metric id.
I think it makes sense to also include a new endpoint for mixed data.
The response could return a list of what I will call typed data points which would look like:
Each data point includes an additional type field. This format makes it very easy to stream the data back to the client when we are executing multiple queries in parallel.