Just found some useful article might explain this behavior and share it
with you. Really appreciate Stuart's explanation on this case!
- https://prometheus.io/docs/prometheus/latest/querying/basics/#staleness
- https://www.robustperception.io/staleness-and-promql
-
Hi Stuart,
Thank yo so much for your quick response! I would like to go more details for
it.
(1) Is there any official documentation has mentioned about this mechanism?
(2) The default look back interval is 5 minutes. Is it configurable for
Prometheus and promtool during the unit testing for
On 2020-07-15 19:17, Jhih Cheng Luo wrote:
I am also curious about this behavior. Can anyone explain this case in
more detail? I appreciate it!
Since the time series data 'x' only has the values between 0m to 2m,
why the alert is still fired between 3m to 7m? Thank!
Tashfia Rahman於 2020年6月9日星期二
I am also curious about this behavior. Can anyone explain this case in more
detail? I appreciate it!
Since the time series data 'x' only has the values between 0m to 2m, why
the alert is still fired between 3m to 7m? Thank!
Tashfia Rahman於 2020年6月9日星期二 UTC+8下午9時57分19秒寫道：
>
> Hi all,
>
> I'm
I am also curious about this behavior. Can anyone explain this case in more
detail? I appreciate it!
Since the time series data 'x' only has the values between 0m to 2m. Why
the alert is still fired between 3m to 7m? Thank!
Tashfia Rahman於 2020年6月9日星期二 UTC+8下午9時57分19秒寫道：
>
> Hi all,
>
> I'm
I am also curious about this behavior. Can anyone explain this case in more
detail? I appreciate it!
Since the time series data 'x' only has the values between 0m to 2m. Why
the alert still is fired between 3m to 7m? Thank!
--
You received this message because you are subscribed to the Google
The scrape time.
--
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 prometheus-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
Thanks for the response! To clarify, does time T refer to the eval_time or
the interval time?
On Tuesday, June 9, 2020 at 4:33:38 PM UTC-4, Brian Candler wrote:
>
> The value at time T is defined as the most recent value received *prior*
> to time T, but prometheus only looks back 5 minutes.
>
The value at time T is defined as the most recent value received *prior* to
time T, but prometheus only looks back 5 minutes.
--
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,
Additionally, if you have multiple input series values, how is it reflected
on the expression? Is the '5 5 5' applied to every minute, or does it mean
that each minute 0 through 2 has a value of 5?
On Tuesday, June 9, 2020 at 9:57:19 AM UTC-4, Tashfia Rahman wrote:
>
> Hi all,
>
> I'm using
10 matches
Mail list logo
