oink issues

invalid byte sequence

5

[root@vps-626-1 thirsty]# bundle exec oink log ---- MEMORY THRESHOLD ---- THRESHOLD: 75 MB /usr/lib/ruby/gems/1.9.1/gems/oink-0.9.3/lib/oink/reports/memory_usage_report.rb:20:in `=~': invalid byte sequence in UTF-8 (ArgumentError) from /usr/lib/ruby/gems/1.9.1/gems/oink-0.9.3/lib/oink/reports/memory_usage_report.rb:20:in`block (2 levels) in print' from /usr/lib/ruby/gems/1.9.1/gems/oink-0.9.3/lib/oink/reports/memory_usage_report.rb:16:in `each_line'...

thepixelmonk

Add Support for Mongoid

Currently it doesn't work, e.g. no module for Mongoid https://github.com/noahd1/oink/tree/master/lib/oink/instrumentation

maciejkowalski

Dyno PIDs on Heroku

Am I right in thinking that oink uses the pid to evaluate changes in heap size? Heroku logs come out looking some thing like: ``` Nov 12 16:06:16 app-name app/web.3:...

tooky

Mongo mapper

Here's mongo mapper support. We've been using it in production for a while. Best, Scott (smtlaissezfaire)

smtlaissezfaire

Oink not logging to STDOUT in Rails 4.1 app on Heroku

1

We are using Rails 4.1.4 and currently can't get Oink to log to standard out in Heroku. Our setup: **Gemfile:** ``` ... gem 'oink', '~> 0.10.1' ... ``` **application.rb:** ```...

mcoetzee

thread safety

1

Oink is currently not thread safe. The use of class variables in the ActiveRecord instrumentation allows for two threads to step on each other. Instead, Thread.current['some_key'] should be used.

ghazel

Fix to make oink skip lines with bad character encoding

1

Tweak to avoid crashing on non-UTF8 log lines. Simply skips processing for those lines.

sgibbons

Scrub out characters with invalid encoding

1

I know the String#scrub method is new, so I check to make sure we're on a ruby that supports this... maybe someone else could chime in about a more compatible...

ghost