Bartlomiej Plotka

No, it's ready to use. You can see example [here](https://github.com/grpc-ecosystem/go-grpc-middleware/blob/main/examples/server/main.go#L140). Where would you expect the examples/documentation? I think it's fair to add migration guide to README, let's do that 👍🏽...

Hi, have you eventually see 1 value in that gauge? Prometheus scrapes with certain interval so there will be delay. That's why Alerts have "FOR" field that ensures alarming state...

So I think we talked about it here: https://github.com/improbable-eng/thanos/pull/899 I would say for this specifc use case, let's start with option `B` and essentially limit, by saying `--store` are explicitly...

Yea, I would say no specifc config just literally special labels we document properly in our docs

It looks like there are mix of things in this feature requests. So is it about host header or per store TLS config?

How you worked around it? If you will quickly describe this it would be awesome for users (: I guess some forward proxy?

It became stale as no one said anything for long time (: I marked this thread as `pinned` as it's not solved and it's fair feature request. We recently added...

Yes. It Is running on production in various places for quite a long time (: Works well, even by using naive polling. > grpc-go now supports SRV records out of...

Seems so, but ideally we have test reproducing this from the author of this issue. Thanks!

https://github.com/prometheus/client_golang/pull/1066#pullrequestreview-1140407380 was merged, implementing the same. Closing this PR, thanks! Feel free to object, we can reopen.