radanskoric
commented
11 years ago Hi, you can use oink with heroku but you have to set it up a bit.
You can use the regular production log on heroku but you have to temporarily lower your log level to INFO. It's now probably set to WARN either in environments/production.rb or in heroku config variables under the LOG_LEVEL variable.
If you lower it to INFO you will see the "Memory usage: #{memory} | PID: #{$$}" lines.
To have the logs in hodel 3000 format you have to replace the regular rails logger with Hodel3000CompliantLogger (a dependancy of oink) by placing this inside either application.rb or environments/production.rb:
config.logger = Hodel3000CompliantLogger.new(STDOUT)
Also, when enabling the oink middleware you have to explicitly tell it to use the hodel 3000 logger:
config.middleware.use( Oink::Middleware, :logger => Hodel3000CompliantLogger.new(STDOUT))
You need to get the log files locally. If you've got some heroku log drains set up (like papertrail or something custom) you can use that. To quickly get some log data to try it out just do something like:
heroku logs --tail --source app --app app-name > production.log
and leave it running for a while to collect some data.
Finally, once you get the heroku logs locally, before you can analyze it with oink it you need to remove the bits at the start of all log lines that heroku adds and that look like:
2013-01-03T16:30:35+00:00 app[web.2]:
you can do that easily on mac/linux system by measuring the length of that part (if you have less than 10 dynos they'll always be of the same length) and using the cut command:
cat production.log | cut -c 39- > production-clear.log
Now you can run oink analysis normally on production-clear.log.
noahd1
gabecoyne
kakubei
benoittgt
Can you make this work on heroku? Heroku needs a puts instead of logger.info
config.middleware.use( Oink::Middleware, :logger => Rails.logger, stdout: true )
That would make it so I could see the data in the log, then you would still need a way to parse it since it's not local and it's not in Hodel3000Logger format, but I could at least see the individual "Memory usage: #{memory} | PID: #{$$}" lines.
If all Oink logs started with Oink, this might work:
heroku logs -n 5000 | grep Oink > log/oink_prod.log oink --threshold=5 log/oink_prod.log
Thanks for the Gem!