Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

undefined method `apdex_t' for nil:NilClass #163

Closed
binarylogic opened this issue May 12, 2014 · 2 comments
Closed

undefined method `apdex_t' for nil:NilClass #163

binarylogic opened this issue May 12, 2014 · 2 comments

Comments

@binarylogic
Copy link

We're seeing this in our resque logs. I'm not sure how or why this would happen. Hopefully the backtrace helps you. If not, let me know and I can try to provide more detail. But I assume checking of the object is not nil will help resolve this.

undefined method `apdex_t' for nil:NilClass
/app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.8.0.218/lib/new_relic/transaction_sample.rb:204:in `force_persist_sample?'
/app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.8.0.218/lib/new_relic/agent/transaction_sample_builder.rb:113:in `finish_trace'
/app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.8.0.218/lib/new_relic/agent/transaction_sampler.rb:116:in `notice_scope_empty'
/app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.8.0.218/lib/new_relic/agent/transaction.rb:206:in `stop'
/app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.8.0.218/lib/new_relic/agent/transaction.rb:56:in `stop'
/app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.8.0.218/lib/new_relic/agent/instrumentation/controller_instrumentation.rb:355:in `perform_action_with_newrelic_trace'
/app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.8.0.218/lib/new_relic/agent/instrumentation/resque.rb:31:in `around_perform_with_monitoring'
@jasonrclark
Copy link
Contributor

Hi @yourewelcome, thanks for reporting this! That definitely shouldn't be happening.

Would it be possible for you to enter a support ticket via https://support.newrelic.com and attach the log file where you got the error. It would additionally be super helpful to get the agent logs too, which are found by default at log/newrelic_agent.log in your app directory. You can ask them to escalate it directly to the agent team so it'll come straight to me to look into further.

Thanks again!

@binarylogic
Copy link
Author

I don't have access to the logs as we're on heroku. But I filed a ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants