You are evaluating the PromQL query
"scrape_duration_seconds{job="prometheus"}@1637919561" at time
1638787945.238
That seems perfectly consistent to me.
A simple instant vector query, like "up", evaluates the expression at some
specific instant in time T (by default, the current time). The value of
each time series at time T is the most recent value it had *at or before*
time T. But the timestamp of the result is T. That's because you asked
for a vector of time series at time T, and the result is the value of these
timeseries as they were at time T.
Similarly, if you ask for "up@T1" at time T2, then the instant vector
result will be timestamped T2, because you asked for the value of this
expression *as it was at time T2*. The fact that the expression internally
makes use of the timeseries at or before time T1 doesn't change this.
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/prometheus-users/4885fd04-72f1-4d11-888a-90ec77b4fa36n%40googlegroups.com.
