Recent activity
Subscribe to this feed
Bill Kayser replied on November 05, 2009 22:16 to the idea "Support for Rails Metal" in New Relic:
Joe I think this is a good increment. I will put this in the backlog. It's not trivial because I don't have a mechanism to ignore a method based on a return value right now. By the time you can determine if it should be ignored, it's already too late. You can look at the rack instrumentation module and think about how this might work.
Meanwhile you can work around it by instrumenting the block manually. I updated the doc to give an example of this. Check out the section on chaining calls at http://newrelic.github.com/rpm/classe...
Bill Kayser replied on November 02, 2009 18:24 to the problem "Resource graph colors not matching key colors" in New Relic:
Bill Kayser replied on October 13, 2009 20:54 to the idea "Support for Rails Metal" in New Relic:
Bill Kayser replied on October 13, 2009 19:36 to the idea "Support for Rails Metal" in New Relic:
Yes I'm actually pretty close to automatic Metal support. However in the current edge agent, you can easily get full visibility into your metal apps, by adding a custom metric call. This is still an early version but if you'd like to try it out, check out the docs on the new controller instrumentation method "perform_action_with_newrelic_trace"
http://newrelic.github.com/rpm/classe...
Or if you want to instrument a single method like it's a controller action, use "add_transaction_tracer"
http://newrelic.github.com/rpm/classe...
If you try it out, let us know how it goes. Report any feedback to support@newrelic.com.
Thanks!
Bill Kayser replied on October 10, 2009 18:16 to the question "Can I disable New Relic for script/console and script/runner?" in New Relic:
Thomas, this will only happen if you have agent_enabled=true (or monitor_daemons=true). Is that right?
The only reason you would change that setting to true is if your dispatcher is not being recognized. Maybe FastCGI or LiteSpeed. Is that also the case?
Would be better if you could follow up with me by submitting a support issue at support.newrelic.com.
A comment on the question "Can I disable New Relic for script/console and script/runner?" in New Relic:
Bhavin this should be working in that version of the agent. Can you please edit the newrelic.yml file, change the log_level to 'debug', then start up the script/console again? Then please send the log to me at support@newrelic.com. – Bill Kayser, on August 05, 2009 15:17
Bill Kayser replied on August 03, 2009 23:52 to the question "Strange NoMethodError during request is unhandled: undefined method `each' for 1:Fixnum" in New Relic:
Bill Kayser replied on July 24, 2009 05:28 to the problem "New plugin version incompatible with older newrelic.yml" in New Relic:
Bill Kayser set one of Bill Kayser's replies as an official response to "No data regarding Physical Memory Utilization is being collected anymore." in New Relic
Bill Kayser replied on July 24, 2009 05:27 to the problem "No data regarding Physical Memory Utilization is being collected anymore." in New Relic:
Bill Kayser set one of Bill Kayser's replies as an official response to "NewRelic error when run under Glassfish 2.1" in New Relic
Bill Kayser replied on July 24, 2009 05:26 to the problem "NewRelic error when run under Glassfish 2.1" in New Relic:
Bill Kayser replied on July 24, 2009 05:25 to the problem "Nginx + Passenger supported? No data being reported..." in New Relic:
Bill Kayser set one of Steve's replies as an official response to "differentiate applications with modrails?" in New Relic
Bill Kayser replied on July 24, 2009 05:24 to the question "Strange NoMethodError during request is unhandled: undefined method `each' for 1:Fixnum" in New Relic:
I can't make out the full stack trace.
Can you send this to support@newrelic.com so we can track it?
Thanks,
Bill
A comment on the question "Passenger 2.1.0 Support?" in New Relic:
Using passenger in dev mode is problematic becaused dev mode stores history in the instance and you might have multiple instances.
Please see http://support.newrelic.com/faqs/trou... for details. – Bill Kayser, on July 01, 2009 20:33
Bill Kayser set one of Bill Kayser's replies as an official response to "Error initializing New Relic plugin !" in New Relic
Bill Kayser replied on June 10, 2009 21:05 to the problem "Error initializing New Relic plugin !" in New Relic:
Well the issue is pretty clear. New Relic needs to be able to write to a log file in the rails logs directory. If it's not there, it needs to be able to create the file with write permissions for the directory. If it can't do that, there can only be a couple of causes: 1) The plugin is running as a UID that does not have the ability to create a log file in that directory, 2) the UID does not have permissions to modify the file that is already there, possibly because it is owned by another user, such as would happen when another rails app ran (like a rake task) as another user.
The best bet is to create the log file described in the error message manually, then set the permissions on it so it can be written by any user.
Bill Kayser set one of Bill Kayser's replies as an official response to "Disable STDOUT" in New Relic
| next » « previous |
Loading Profile...

