heroku - Attempted to Rename Transaction to "..." After Transaction Name Was Already Frozen -


i'm getting following warning on every request:

attempted rename transaction controller/sessions/new after transaction name frozen.

i'm running on cedar on heroku ruby 2.0.0p195, rails 4.0.0.rc, unicorn 4.6.2 , rpm 3.6.2.96. i've traced exception following file (line 108) i'm unsure of fix:

https://github.com/newrelic/rpm/blob/master/lib/new_relic/agent/transaction.rb

i work @ new relic.

when message this, it's due component of our app known real user monitoring (rum), attempts monitor page load time in customer's browser. why should affect ability rename transactions? base timing capture in user's browser on transaction id--which tied transaction name on server--and information goes footer we've created web page. time create footer, whatever transaction name continue case through end of transaction. in case have slow page load corresponds slow app server transaction , captured both traces, in our ui you'll able click between 2 (this slow page load came that specific slow transaction).

rails 4 makes rather harder if you're using turbolink feature. we're working on explicit support soon, stands, turbolinks preclude rum working after first page load (if app has links in it, anyway).

so, options fixing are:

  1. rename transaction earlier in code sequence--preferably rather far before end of content generation (necessarily before gets output, in cases rather sooner)
  2. turn off browser monitoring app, can rename transactions @ point in execution

note suggestion 1 might not work considering state of our turbolinks support. we'll have support can--certainly sometime year. unfortunately don't promise timelines, deliver features, can't more specific on timing.


Comments

Popular posts from this blog

blackberry 10 - how to add multiple markers on the google map just by url? -

php - guestbook returning database data to flash -

java - Using an Integer ArrayList in Android -