It would be _amazing_ to have a Sentry plugin that queries fullstory API and adds a link in the Sentry UI that takes you directly to the fullstory session that triggered the Sentry - maybe couple seconds before the event fired
The full story url is basically the fs_uid from the cookie data already saved in Sentry.
Example:
fullstory.com`ABC123`23094802384:239085039485904`90348`
Basically translates to:
https://app.fullstory.com/ui/ABC123/session/23094802384:239085039485904/90348/
Of course a plugin would be a better long term solution but that data could simply be parsed from the cookie info if needed.
i know this is old but one solution is to add the URL in the tags:
dataCallback: function (data) {
if (!data.tags) {
data.tags = {}
}
// Adds the FullStory URL to the tags in Sentry
if (window['FS']) {
data.tags.fullStorySessionUrl = window.FS.getCurrentSessionURL(true)
}
return data
}
Just confirming if fullstory plugin is a possibility in the near future :)
We use the following snippet and it just works:
Sentry.configureScope(scope => {
scope.addEventProcessor(async (event) => {
if(event.extra == null) {
event.extra = {}
}
event.extra.sessionURL = FS.getCurrentSessionURL(true)
return event
})
})
@mkj28 @bcmcq @devdazed @grv231 @buremba
Hey there, in fact, there is a Sentry-Fullstory integration as of a few weeks ago! Check it out here: https://www.npmjs.com/package/@sentry/fullstory
At the core of it, it works pretty much how @buremba's code snippet works. But there is actually additional functionality of linking to the Sentry error from FullStory. Please don't hesitate to reach out if you have any questions (preferably here: https://github.com/getsentry/sentry-fullstory/issues)
WOOOT!!! WOOOT!!!
Nice, will check it out today itself. Forgot about this that I had asked a question here :)
Awesome, thanks!
Most helpful comment
@mkj28 @bcmcq @devdazed @grv231 @buremba
Hey there, in fact, there is a Sentry-Fullstory integration as of a few weeks ago! Check it out here: https://www.npmjs.com/package/@sentry/fullstory
At the core of it, it works pretty much how @buremba's code snippet works. But there is actually additional functionality of linking to the Sentry error from FullStory. Please don't hesitate to reach out if you have any questions (preferably here: https://github.com/getsentry/sentry-fullstory/issues)