Björn Rabenstein

> A) Bring ObserveWithExemplar to Observer, why not? Because it changes the `Observer` interface. It breaks everyone who has implemented the `Observer` interface outside of our control (most commonly, I...

The other approaches are all valid options, I think. I would just generally suggest to put helpers into a separate package. My experience from the past is that users get...

Also, check what flavors of multi-error other parts of the Prometheus ecosystem are using.

To keep things in scope of this issue: We can only change the MultiError in client_golang when we bump the major version. That won't happen tomorrow, so I'd say just...

I mostly assigned this to myself as a “default” because I used to be the maintainer of this repo. Therefore, I'm un-assigning this from myself no. New maintainers @bwplotka &...

This has to be sync'd with other client libraries, obviously. Perhaps a topic for the roadmap meeting at PromCon.

The implementation details will be fairly easy to figure out once we have settled on the HTTP API (which should be the same across client libraries). Since the choice there...

I have been pondering the idea of automatic "description by collection" for quite some time (since December 2013 or so). Sometimes, it will work great, but sometimes it would defeat...

> I think we should do this by passing in time series names/regexes. I think labels would be a bit much in practice. Yes, that's what I would go for....

> Only for the 1st class of exporters I listed above. That doesn't help the mysql exporter as-is. "Describe by collect" might simplify things (but not if metrics show up...