Open
Description
It'd be lovely to see Statsd grow support material to use it as a library, rather than as a standalone daemon. Rather than app->(statsd->statsd-backend)->storage, it'd be great to have (app->statsd-backend as a single process)->storage, for operational ease (the Dropwizard "the app is the app and requires little else" philosophy) and for footprint.
Activity
mrtazz commentedon Feb 20, 2015
Can you elaborate a little bit on how do you want to use it? But in general the nodejs runtime is already somewhat limited when it comes to computation heavy things. So I'd probably advice against running StatsD fully inline in your app (if that's what you're getting at).
rektide commentedon Feb 20, 2015
I'd like deployable applications that use the statsd backends to output metrics. I'm unsure how much front end could or should be made use of to do that, and looking for some guidance as to what might make good starting places to begin using statsd / statsd-backends inline.
coykitten commentedon Jul 17, 2015
@rektide We're a ways off from being able to
require('statsd');in another application but generally I think it's where we want to go. Currently the main application file,stats.js, is not a proper node_module as statsd was written when nodejs was new and best practices for Common.js requires and the like were still being developed.I've gone ahead and added your request to the 1.0 milestone as I think that this is something that should be addressed but is still a major refactor.