rcrowley/go-metrics

Contact client implementation authors about splitting off into new libraries

mihasya opened this issue · 15 comments

Other libraries to document:

From the gist of it, it sounds like a good idea, maybe you could share some details you have in mind?

Howdy! Basically, just spinning the individual reporters that require an external dependency (like a service) into their own little repos that import go-metrics and are referenced in go-metrics README and docs, but are otherwise independent. So many of the issues and PRs are for things like Stathat InfluxDB, which none of the maintainers of go-metrics use, so they just languish. I think it's a more maintainable path forward.

@mihasya Any preferences on the naming of theses "spin-off" ?

@cyberdelia hmm.. not entirely sure, but I also don't think it's worth agonizing over. They'll theoretically only be imported once, in main.go, correct?

@cyberdelia probably something like metrics-graphite or similar will work just fine.

@cyberdelia you can see my stab at the Librato client's move here #122

@cyberdelia nice and easy. Thanks!

I don't use the stathat lib at all, if someone else wants to take ownership - I'm happy to relinquish any "control"

@bketelsen thanks for letting us know. We'll find it a home, even if it's just under my account with a "MAINTAINER WANTED" in the README.

It looks like the github account for Michael Crosby is @crosbymichael. Michael, would you be interested in becoming the maintainer for a split-out version of the influx reporter?

@mihasya ya, i can take the influx part

@crosbymichael Beauty! Please check out the repos myself and @cyberdelia have created for librato and graphite

http://prometheus.io/ looks like a candidate for the creation of a client

Is there something inherently incompatible with statsd and this library, that there isn't an exporter for it?