Toby Lawrence

What would this look like in practice? Right now, we _do_ have docs for the macros under `metrics/src/lib.rs` where we re-export them.

No sweat! Can you take another look on `main`? I pushed an update that removes `proc-macro-hack`, which I think should lead to the re-export stuff not getting garbled and letting...

Very delayed reply, but combing through older issues on the repo... It _seems_ like this is related to how we re-export the macros, since looking at the `test` proc macro...

It turns out that achieving this is not super easy. The best I've been able to manage to do is to get `rust-analyzer` to display a simple doc comment on...

Is there anyway you can give me a high-level overview of exemplars and how a typical application, with one of the official Prometheus client SDKs, is using them? I'm finding...

Just a note: this is still on my backlog to review, things have just been a bit hectic for me lately. 😅

So, my main question after reading your explanation (thank you for that!): do the exemplars have to be logically related? Which is to say... if I have two concurrent tasks/threads/whatever...

> They can be different, there is no connection between exemplars over different metrics. Alright, that's good news. 👍🏻 Depending on the behavior necessary, it seems like it could be...

Right, so my thought is that the render logic would essentially be responsible for figuring out if it was time to sample a new exemplar for each unique histogram. So...

Are the labels for exemplars only meant for exemplars period? Like would you not typically include, say, a trade ID label _unless_ you wanted it to be an exemplar?