> 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 interval timer is a
ticker (specifically a Go time.Ticker[*]) and it effectively only does a
new tick and thus a new scrape of the target when the old one is done. I
believe that you might be able to get scrapes (of a given target) back
to back, but only one scrape (of a given target) is ever happening at
one time because the thing that does the scrape is driven by the ticks
of the timer.
(If Prometheus or the system it's running on is under load these ticks
and handling them may be delayed, too, but again there's only one scrape
of a given target in progress at once.)
- cks
*: https://pkg.go.dev/time#Ticker
--
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/243248.1712344360%40apps0.cs.toronto.edu.
