As far as I know, the /query_range endpoint only accepts an *instant*
query. The instant query is swept between the given start and end times at
the given step. In other words, it repeats the instant query at multiple
points in time, as if you'd hit the /query endpoint multiple times.
However,
Thank you Julius.
-So range vector selector (like "foo[5m]") is run on range_query url(
*/api/v1/query_range*) and not on instant query(*/api/v1/query*) url right?
If it needs to be given on */api/v1/query_range*), the documentation refers
to only this where *start*, *end* and *step* parameters ar
Hi,
I just saw this question. Check out
https://promlabs.com/blog/2020/07/02/selecting-data-in-promql and
https://promlabs.com/blog/2020/06/18/the-anatomy-of-a-promql-query, which
should answer most of your questions in more detail.
In addition to answers Matthias provided:
2. + 3. All three ran
1. Now
2. Uh, not sure, probably better to specify one 😬
3. Probably not, end might default to "now" implicitly?
4. They are different – there are two different types involved here.
`http_request_total` returns an instant vector: a 1-dimensional list of the
value at that instance for each label com
Hello all,
I am new to PromQL and would like to understand as I could not find things
(unless I am missing it) here:
https://prometheus.io/docs/prometheus/latest/querying/api/
1. For an instant query, if I dont give timestamp, then what is the
logic/default timestamp.
2. For range query, what is
5 matches
Mail list logo
