The goal here was to solve our issues with Librato and Node.js only on a distributed system on Heroku. Here's the list of our issues / questions :
- we loved how easy the log drain was to use
- but we sent too much data to use the log drain w/ Heroku so some of it was skipped and the data was inconsistent
- we had multiple machines updating the same counters (e.g. # of concurrent jobs) and we wanted a rate (concurrent jobs / s accross all machines) : you can't do using
counters
librato-node
uses counters internally when you callincrement
- using
librato-node
indev
environment requires you to wrap it - making a request to the API every 15s would induce performance issues