Bill Kayser's dashboard

Bill Kayser replied on February 19, 2009 17:24 to the question "What constitutes an incident for the Twitter/Campfire integration?" in New Relic:

Hi Josh, an incident is anything that is shown in our automatic incident detection feature available at Silver level or higher. The incident could be an exceeded threshold (set on the dashboard page) or activation of one of our heuristics that looks at anomalous behavior vs. the same time period a week ago. For example, if your error rate goes up by 50% or more over the same time last week, that may trigger an incident.

Bill Kayser replied on February 19, 2009 01:38 to the problem "Error loading data for longer timespans" in New Relic:

This is not expected. It may be related to the size or scope of your data. I'd like to investigate this. Can you send an email to support@newrelic.com with your account name and license key?

Bill Kayser replied on February 18, 2009 21:39 to the question "Turning off error collector doesn't work." in New Relic:

Garry, this sounds like a bug. Can you forward this to support@newrelic.com? That will allow you to track progress on the fix, and for us to follow up with some more questions.

Thanks,
Bill

Bill Kayser replied on February 18, 2009 21:22 to the question "RPM reports 28 gigs of memory use?" in New Relic:

Noah we're aware of the problems with Glassfish and JRuby. We're working to try to get on top of them. I expect to have these issues worked out in the 2.9.0 agent release. I'm sorry for the inconvenience but we really do appreciate the feedback.

If you have other questions or issues with JRuby feel free to direct them to support@newrelic.com.

A comment on the problem "NewRelic error when run under Glassfish 2.1" in New Relic:

Joe, can you send the log file to support@newrelic.com? – Bill Kayser, on February 18, 2009 17:56

Bill Kayser replied on February 18, 2009 17:55 to the problem "Problem with sending email when adding new accounts" in New Relic:

The problem should be fixed now. Please let us know if you have any more problems.

Bill Kayser set one of Bill Kayser's replies as an official response to "Passenger 2.1.0 Support?" in New Relic

Bill Kayser replied on February 18, 2009 03:16 to the question "Passenger 2.1.0 Support?" in New Relic:

I just published a fix in version 2.8.4. Please update the agent and let me know if you still see problems.

Bill Kayser replied on February 17, 2009 22:55 to the question "Passenger 2.1.0 Support?" in New Relic:

We're aware of this. I'm working on this right now. Give me a chance to rescue you from mongrel.

Bill Kayser replied on February 17, 2009 17:17 to the problem "stats engine is reporting an error and not logging any actions from my application." in New Relic:

Josh, thanks for reporting this. I'm very concerned about this. This is the first report we've had of this problem. Can you follow-up with me at support@newrelic.com?

Please send an email with some details:
- confirm you are on the latest agent, or at least 2.8.*
- what version of rails?
- JRuby? MRE?
- using any of the (somewhat obscure) agent apis, like 'add_method_tracer'?
- happens in dev mode? have you tried with server mode (enabled=true)?

Can you confirm that this does not interfere with the application running normally? Error messages (and lack of stats) should be the only side-effects.

Bill Kayser replied on February 14, 2009 21:56 to the question "Capistrano 1.4.2 with rake not working with RPM" in New Relic:

We add a cap recipes file in the plugin which will get loaded automatically if your Capfile has this line:

Dir['vendor/plugins/*/recipes/*.rb'].each { |plugin| load(plugin) }

Unfortunately it won't load properly in versions prior to 2.0.0. We'll fix the next version so it will handle the error more gracefully.

In the meantime you'll need to either delete the newrelic_rpm/recipes/recipes.rb file to be able to deploy again.

Sorry for the inconvenience.

Bill Kayser replied on February 13, 2009 18:48 to the question "Is it normal for mongrel to never release memory?" in New Relic:

No, the memory allocated to any Ruby process will never go down. This isn't a mongrel or Rails thing. In fact it's probably true of any process.

It sounds like you have a page that allocates a massive amount of temporary objects. Your best option is to tune your application to try to reduce the amount of overhead. While RPM can't show you object allocations it can show you details of your interaction with the database and where time is being spent. Look for the code where the most time is being spent and see if you have excessive use of buffers or inefficient String operations. Beware of having many many small Active Record objects.

Do you have a memory leak? Here's how to tell. Hit the page that causes the memory to jump up. Then hit it repeatedly. Is there only a bump the first time, or does it get bigger with each hit? The latter would indicate a memory leak.

Hope this helps.

Bill Kayser replied on February 13, 2009 00:13 to the question "Can I disable New Relic for script/console and script/runner?" in New Relic:

This looks like a bug in the jruby support. I'm afraid I don't have a good workaround for you but we'll look into a fix for the next major release.

Bill Kayser replied on February 12, 2009 19:10 to the problem "Problem with sending email when adding new accounts" in New Relic:

Thanks for bringing this to our attention. My inclination is to change the reply address to "no-reply@newrelic.com". Would that fix the problem?

Bill Kayser replied on February 11, 2009 20:54 to the problem "2.7.4 causes Error calling Dispatcher.dispatch" in New Relic:

I managed to reproduce the problem and have a fix in the beta download.

It seems that having some classes loaded via 'require' and others via 'const_missing' causes confusion for Desert. We were getting multiple instances of Classes (same constant, but different object_ids) in this situation.

This will be fixed in version 2.8.3 due out in a week or two. In the meantime you can preview 2.8.3 here:

http://newrelic.rubyforge.org/svn/bet...

Bill Kayser replied on February 11, 2009 17:08 to the problem "NewRelic error when run under Glassfish 2.1" in New Relic:

Steven can you try this with the latest version of the plugin? We're at 2.8.2 now.

If it still happens, can you send me the full newrelic_agent.xxxx.log file?

Also are you by any chance running in multi-threaded mode?

Bill Kayser replied on February 10, 2009 21:53 to the question "Can I disable New Relic for script/console and script/runner?" in New Relic:

can you describe in a little more detail what is happening? Is it uploading data to the server? or is it just that you noticed output to STDOUT?

When you run a rake task, does it create a newrelic_agent.?????.log file? If so, what is it called?

Bill Kayser replied on February 10, 2009 20:14 to the problem "New relic substantially slows down starts under Glassfish" in New Relic:

We're not aware of this. Can you follow-up to support@newrelic.com?

Let me know what version of glassfish and Rails, what OS version. Also is this in developer mode or server mode (enabled:true)?

If you have any other information about what might be causing the delay, forward that as well.

Bill Kayser started following the idea "new relic status in your firefox browser" in New Relic.

Bill Kayser replied on February 10, 2009 06:04 to the question "Can I disable New Relic for script/console and script/runner?" in New Relic:

Noah, can you try the latest version of the agent (2.8.2) and tell me if you still see this behavior?