snowplow javascript tracker with page view event slows down New Relic

104 views
Skip to first unread message

tkut...@dotandbo.com

unread,
Feb 12, 2015, 8:19:32 PM2/12/15
to snowpl...@googlegroups.com
Issue: We are trying to add the snowplow javascript tracker to our site but sending events has caused New Relic to think pages are rendering around 3x as long as usual.  

Specifically, sending a page view event as an unstructured event causes the slow. That said, we haven't been able to reproduce any user-facing issues that corroborate the slows down New relic is reflecting.

Also, we pass all events as unstructured events, and without the "Page View" event we don't see any issues.

Anyone run into this issue before or have any thoughts as to why tracking this "Page View" event as an unstructured event would cause New Relic to think the page hasn't rendered for longer than normal?


Screen Shot 2015-02-12 at 5.17.18 PM.png

Ryan Doherty

unread,
Feb 12, 2015, 9:30:33 PM2/12/15
to snowpl...@googlegroups.com
When are you firing the event? Before window.onload? Make sure you don't fire that event until everything else has loaded. NR overrides a lot of global JS objects and sees every request being made. 

How long does the HTTP request take to complete? Take a look at your HTTP traffic in a browser.

--
You received this message because you are subscribed to the Google Groups "Snowplow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to snowplow-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
-Ryan

Tim Kutnick

unread,
Feb 13, 2015, 7:44:45 PM2/13/15
to snowpl...@googlegroups.com
We are firing the page view event on document ready
$(function(){
setTimeout(function(){ 
DotBo.trackEvent("Page View", { "url" : document.location.pathname });
}, 0);
});

We took the page view event off our site so not sure what it was.  There wasn't any user-facing interruption so I'd assume it was within a 2-6s range for most users.  Snowplow events have been taking 100-300ms I think.

Are you aware of any reason why firing the page view event after the document is ready vs loaded would impact NR?  

Thanks for the help,

Tim

p.s. We're planning to try sending the pageview event after window.onload on Monday

--
You received this message because you are subscribed to a topic in the Google Groups "Snowplow" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/snowplow-user/kfEd3dvIrAE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to snowplow-use...@googlegroups.com.

Ryan Doherty

unread,
Feb 16, 2015, 1:00:07 PM2/16/15
to snowpl...@googlegroups.com
Document ready is different than document loaded. Ready is usually when the DOM has been constructed but not everything has loaded. 

You really need to look at your network waterfalls and response times for your pages when you fire the event. Does NR have the network waterfalls available for the slow page loads? That graph shows averages, you should look at percentiles to figure out if if was a small % of your users having slow response times.
Reply all
Reply to author
Forward
0 new messages