couchdb-erlang mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Lehnardt <>
Subject Re: starting on metrics
Date Fri, 16 Nov 2012 12:56:23 GMT
Hey all,

I love this discussion, but note that this is erlang@ where we want to
get people comfortable hacking CouchDB internals, not dev@ where we make
it extra hard to get your patches in (which we don’t but you know what
I mean :)

If this is a training exercise for Dave that may or may not lead to stuff
we can merge into CouchDB proper, or use as a learning-protype or whatever,
we should focus on that instead of trying to figure out what the proper
way to do this if it were on track to land in CouchDB.


On Nov 16, 2012, at 08:13 , Ben Anderson <> wrote:

> On Thu, Nov 15, 2012 at 7:58 PM, Paul Davis <> wrote:
>>> Well, it would be nice to provide a clean internal API for storage,
>>> then use that for the default HTTP plugin, yeah?
>> Not sure what you mean by storage here. I would say the first step is the
>> API for collection which is just the "couch_stats:incr(Key)" type of
>> discussion. The HTTP plugin would then just be a thing that provides an
>> implementation for those functions and has an HTTP handler to report.For
>> more complicated bits like statsd/riemann/collectd the plugin would just do
>> what's necessary to forward on the collected metrics.
> More specifically I mean a split between metrics insertion ("storage")
> and metrics retrieval. That would make it straightforward to enable
> two simultaneous retrieval interfaces (e.g., Collectd and HTTP), since
> they wouldn't include conflicting implementations of an insertion API.
> Probably better just to write this than awkwardly debate the
> semantics. I'm sure you'll like it when it's done, Paul. ;)

View raw message