Re: [prometheus-users] query for time series misses samples (that should be there), but not when offset is used

> Also, what would happen if e.g. there was a first scrape, which get's > delayed > 0.002 s ... and before that first scrape arrives, there's yet > another (later) scrape which has no jitter and is on time? > Are they going to be properly ordered? As far as I know, this can't happen. The scrape

Re: [prometheus-users] query for time series misses samples (that should be there), but not when offset is used

Hey. On Friday, April 5, 2024 at 7:10:29 AM UTC+2 Ben Kochie wrote: If the jitter is > 0.002, the real value is stored. Interesting... though I guess bad for my solution in the other thread, where I make the assumption that it's guaranteed that samples are always exactly on point with the

Re: [prometheus-users] query for time series misses samples (that should be there), but not when offset is used

On Thu, Apr 4, 2024 at 7:03 PM Christoph Anton Mitterer wrote: > Hey Chris, Brian. > > Thanks for your replies/confirmations. > > > On Sunday, March 24, 2024 at 8:16:14 AM UTC+1 Ben Kochie wrote: > > Yup, this is correct. Prometheus sets the timestamp of the sample at the > start of the scrape. B

Re: [prometheus-users] query for time series misses samples (that should be there), but not when offset is used

Hey Chris, Brian. Thanks for your replies/confirmations. On Sunday, March 24, 2024 at 8:16:14 AM UTC+1 Ben Kochie wrote: Yup, this is correct. Prometheus sets the timestamp of the sample at the start of the scrape. But since it's an ACID compliant database, the data is not queryable until aft

Re: [prometheus-users] query for time series misses samples (that should be there), but not when offset is used

Yup, this is correct. Prometheus sets the timestamp of the sample at the start of the scrape. But since it's an ACID compliant database, the data is not queryable until after it's been fully ingested. This is intentional, because the idea is that whatever atomicity is desired by the target is hand

Re: [prometheus-users] query for time series misses samples (that should be there), but not when offset is used

> I noticed a somewhat unexpected behaviour, perhaps someone can explain why > this happens. > > - on a Prometheus instance, with a scrape interval of 10s > - doing the following queries via curl from the same node where Prometheus > runs (so there cannot be any different system times or so > > L

[prometheus-users] query for time series misses samples (that should be there), but not when offset is used

Hey. I noticed a somewhat unexpected behaviour, perhaps someone can explain why this happens. - on a Prometheus instance, with a scrape interval of 10s - doing the following queries via curl from the same node where Prometheus runs (so there cannot be any different system times or so Looking a