Trace data can point to things that are going wrong within your users’ digital experiences. Long spans corresponding to a particular service call might translate into a sluggish app experience, for example. Trace spans that contain errors could mean a user experience is completely broken. However, it’s impossible to really gauge the severity of user impact by looking at trace data alone.
This is where FullStory session replay URLs can help. These are deep links to session replays that you can watch to understand what users were experiencing when a trace anomaly occurs. You can also observe behavior prior to something going wrong in the trace to understand whether any precipitating user events may have triggered the issue.
Get the most out of FullStory + New Relic
View user activity prior to an error occurrence
Utilize FullStory’s session replay to see your users’ first-person view of errors and performance issues alongside essential details flowing through New Relic.
Shed light on the complex sequence of events that tripped up your system.
With a New Relic agent running alongside FullStory, your engineering team will have all the data they need to prioritize a fix, quickly. Dramatically reduce time-to-repair of system errors by accessing both your users’ first-person view of an error alongside essential trace data.
Zoom out to understand the broader impact that issue might have on your user base.
Then, zoom back in on individual sessions to see how each user’s experience differed to determine exactly why some users experienced an issue and others did not.
How it Works
With New Relic and FullStory, access deep links to session replays directly within New Relic to understand what users were experiencing when a trace anomaly occurred.
Web & Mobile Web
To enable this integration on Web, follow the instructions found here.
Native Mobile - Android & iOS
To enable this integration on your Native Mobile App, follow the instructions found here.