Thats odd. I confirmed remote read is returning future data points to
Prometheus. But I can't see the data points in Prom UI. The series is
truncated to 'now'.
On Monday, May 10, 2021 at 7:44:20 AM UTC-4 Julien Pivotto wrote:
> On 07 May 09:42, Johny wrote:
> > Hi,
> > Could you please look int
On 07 May 09:42, Johny wrote:
> Hi,
> Could you please look into this? I just want to understand PromQL behavior
> with future timestamps.
I do not think we have limitations here. Could you look at the remote
read query Prometheus is sending? Is it cropping the timestamps? not
sending the query?
Hi,
Could you please look into this? I just want to understand PromQL behavior
with future timestamps.
On Monday, May 3, 2021 at 1:47:52 AM UTC-4 Johny wrote:
> Prometheus remote read -
> https://prometheus.io/docs/prometheus/latest/configuration/configuration/#remote_read
> (I thought this wa
Prometheus remote read
-
https://prometheus.io/docs/prometheus/latest/configuration/configuration/#remote_read
(I thought this was part of standard)
read_recent is already set to true. Any data points in future (now+x) are
not returned back. Anything in prometheus causing this?
On Sunday, May
On 02 May 12:57, Johny wrote:
> I am reading time series from a remote backend via Open Telemetry remote
> read API. It works for most cases except future time series (data points in
> future). I can see the data points (+1 or 2 years from now) are being
> returned from remote backend but Promet
I am reading time series from a remote backend via Open Telemetry remote
read API. It works for most cases except future time series (data points in
future). I can see the data points (+1 or 2 years from now) are being
returned from remote backend but Prometheus is not rendering them to users.
6 matches
Mail list logo
