ryandotsmith / l2met

Convert a formatted log stream into metrics
http://r.32k.io/l2met-introduction
GNU General Public License v3.0
284 stars 26 forks source link

heroku install from scratch using script causes I/O errors when posting to librato #124

Open jakeyr opened 10 years ago

jakeyr commented 10 years ago

Hi-

I just installed a fresh heroku app running l2met using the tarball and setup script. After setting up the drain, I see l2met processing incoming requests in the logs, but no data in librato.

I am seeing these lines in the logs which makes me believe that the data posts to librato are failing:

2013-12-04T22:31:46.709885+00:00 app[web.1]: measure.librato.error user=__REDACTED__@heroku.com msg=Post https://metrics-api.librato.com/v1/metrics: read tcp 54.225.173.29:443: i/o timeout attempt=0

any ideas? i tested the credentials i supplied to the setup script by using command-line curl calls to the api and they worked fine, i was able to submit metrics and see them in librato.

thanks!

ryandotsmith commented 10 years ago

Hello, @jakeyr. Did you know that Librato now runs l2met as a service? They have a bullet proof setup and unless you are just wanting to hack, I would highly recommend you use their service.

https://devcenter.heroku.com/articles/librato#custom-log-based-metrics

ryandotsmith commented 10 years ago

As a side note, I think I am going to make a note of this in the README.

jakeyr commented 10 years ago

Awesome, thanks for the tip, I'll switch to that.

Meanwhile, just to satisfy curiosity... any idea what I did wrong here?

Thanks!

-jake

ryandotsmith commented 10 years ago

So the log line is reporting that the POST operation to librato's api timed out. You can increase the timeout on this operations via the outlet-ttl flag. (e.g. $ ./l2met -outlet-ttl=5s)