Description
In our system, the activity of our job queues is very bursty: every day around midnight, millions of jobs are enqueued and processed, and then there are times later in the day where there is no work to do. We've been getting a bunch of 400 errors from Librato with an error like this:
{"errors":{"request":["Must contain a measurement"]}}
Looking at the Metriks librato reporter this makes sense: it submits all measurements that were taken in the last minute regardless of whether or not there were any. When there were none, it gets the 400 error from Librato.
It would be nice if the Metriks librato reporter was a bit smarter about this and would not try to submit a request with no metrics.
@eric, if you're on board with that idea I'll try to make time to submit a PR for this in the next week or so.