Yeah. It's like
statsd, but with more types and less heavy
lifting, and thus an expanded protocol. statsd clients are compatible with
metricsd, but not vice versa. Sorry. If you wanted to, you could probably
implement a compatibility mode.

Specify log: true to emit metrics to STDOUT rather than the default UDP
socket.

If you provide a logger to the metricsd() factory (console.log or
compatible), it will be used to emit metric strings in the form metric: <metric>. This can be convenient if your logs streams are being consumed by
something that can more efficiently funnel data into metricsd or similar.