That makes sense to me, and would be nice to build of an existing protocol, and agree it sounds like a large effort. I’m pretty new to xDS as well, though we have many people on the Kuma team who are quite knowledgeable — I’d be happy to set up a call/ bring them in to help size the work if you’d be open to that.
And understand + agree on the configuration approach for the extra layer. The main difficulty for users is configuring the file_sd + sidecar, relabel_configs should be fairly straightforward and accessible. Austin On Wed, Oct 21, 2020 at 6:37 PM Julien Pivotto <[email protected]> wrote: > On 21 Oct 15:12, Austin Cawley-Edwards wrote: > > Hey all, > > > > I've gathered up some research about our efforts with the DNS SD option, > > please let me know if I've overlooked something. > > I have been looking on my side too - I think that what the option that's > more likely on the table would not to have a "generic" implementation, > but a xDS protocol service discovery. In that case, it would not be an > issue to have that in Prometheus (even the gRPC version). > > However, the extra layer that kuma is offering in the SD should be done > at the Prometheus configuration level - e.g. by the user, in the > relabel_configs. > > I think I'd like to better understand xDS but it seems that it could be > good option for a service discovery in Prometheus, at least at first > sight. > > We are looking at a huge amount of work here I think. > > -- > Julien Pivotto > @roidelapluie > -- You received this message because you are subscribed to the Google Groups "Prometheus Developers" 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-developers/CALGL%2BUC0xqbt-9pwmSzzbshiisxNu5RoOh6DSxNrwOzpK%2BdveQ%40mail.gmail.com.
