Open killme2008 opened 1 year ago
@killme2008 this seems still relevant. What is our starting point? Read the PromQL remote read code path and investigate how to add the time series info and whether it helps?
cc @waynexia
We have a plan to support it, and we already have tsid
in the storage format, it can be used to improve the performance.
For prom remote read API, maybe we can also select the tsid column. However, we already have native PromQL support so the priority of this issue should be low.
it can be used to improve the performance.
We can use it to improve performance and that is what I'm going to do, but it is out of this issue's topic.
When we query from a metrics table written by prometheus remote write:
We don't known the timeseries information at all( for example
instance, job
here), so when we want to supports remote read ,we have to find out the timeseries by ourself such as:The timeseries protobuf message:
It's really ugly and not good for performance. I think we should improve it in future.