dt-rush

@lurch yep

@lurch this one can probably be transfered to docs repo as well

Workaround for now, as @xginn8 devised: > `max(scrape_duration_seconds{job="vpn/cluster"}) < bool 5` will return `1` when a scrape takes less than 5s, and `0` when it takes longer. > > combining...

Dropping the incomplete datapoints query-side is one thing, but dropping them entirely seems to be worth something in my view, unless (this is the only workable "solution", in the case...

If the number of cluster workers is known, and the number of cluster workers timing out is known (presently such metric are not exported), such an averaged "guess" of the...

For the record, this also occurs when a worker has died, not just in the case of timeouts (this is what @xginn8 meant by "timeouts / errors") I see there...

Thanks for pointing that out @zbjornson. I'm working on a PR and tests for this atm. For further justification for this change, I cite the [`robustperception.io` blog post](https://www.robustperception.io/why-predeclare-metrics) on predeclaring...

@zbjornson as mentioned in the discussion in #299, that'll be reverted as it adds to the unnecessary rigidity of using this client.

That is all sorted nicely, however, there is one more issue to bring up: In the [Writing client libaries # Labels](https://prometheus.io/docs/instrumenting/writing_clientlibs/#labels) docs, we read: > Client libraries MUST NOT under...

Branch pushed here: https://github.com/dt-rush/prom-client/tree/relax-label-predeclaration