On 27 May 08:05, Brian Brazil wrote: > On Wed, 27 May 2020 at 07:52, Stuart Clark <[email protected]> wrote: > > > On 27/05/2020 07:50, Brian Brazil wrote: > > > > On Wed, 27 May 2020 at 07:05, Ben Kochie <[email protected]> wrote: > > > >> I was thinking about building an "exporter kit" repo that would include > >> some helpful functions to reduce the amount of boilerplate needed to write > >> exporters. > >> > > > > I've thought such a thing would be useful for a long time, though my > > presumption was always that it would end up in client_golang as it's not > > too far from instrumentation. > > > > In general I'm not a big fan of widespread proliferation of repos, > > particularly if it's lots of tiny repos. Even in the previous cases where > > we managed to get the layering largely right, it still was quite a pain in > > terms of overhead and release management if the repos were being actively > > developed. A single toolkit-y repo I could live with, I'd be concerned if > > we were talking repos beyond that. > > > > > > How does the release management/overhead differ between several single > > purpose repos and a single repo containing independent things in different > > directories? > > > I don't think we've really had that particular situation come up yet, but I > imagine there'd be similar challenges either way - likely with the > multiple-repo case being a bit trickier to debug through.
We would need to adapt our Makefiles; and stop vendoring if we go for multi repo in one. The benefits for the users is to be able to only pull the https/package. But now that I think about it, of we make a toolkit repo, it will probably ALSO include the http server logic, so the exporters would NOT need to use http directly. At the end, I then think we then can do a single toolkit repo. Next to the toolkit repo (in prometheus org) we could also create a template repo [1] github.com/prometheus-community/exemple_exporter which reuses that and that people can just "fork" [2]. [1] https://help.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-template-repository [2] https://help.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template > > -- > Brian Brazil > www.robustperception.io > > -- > 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/CAHJKeLrCUHOYnd3u%2B%2B8KNexFr0qdrT_0e69eeC8ZMz--r4WymQ%40mail.gmail.com. -- 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/20200527072640.GA334861%40oxygen.
