FullStory Developer Console FAQ

What does "Script Error" mean?

"Script Error" is what you see when the browser hides the precise origin of an error. This happens when the error occurs in a script hosted on a different domain than the site, and it's there for security reasons. Unfortunately, FullStory can't give you any further context than what is passed to us so you may sometimes see "Script Error" in the FullStory console. 

What console messages doesn't FullStory capture?

There are some messages that browsers display on their respective developer tools' consoles, but which aren't technically console messages, and thus unavailable to FullStory. These include things like deprecation warnings, and certain kinds of security and network errors.

Can I control this behavior?

When FullStory is recording console messages, and you're using the browser console yourself, you will see messages attributed to "fs.js". While this doesn't affect the user's experience in any way, it can make debugging a bit more difficult. If you want it to get out of the way, simply call FS.disableConsole() on the console (you can re-enable it with FS.enableConsole()). If you want to turn it off for all pages, you can do so using the toggle in Settings > Recording > Recording Options.

FS.log()

FS.log() provides a way to silently log messages to FullStory console, without logging the message to the user's browser console. See FS.log for additional information.

Are there any limitations on what the FullStory Console can display?

FullStory limits the console to 1024 messages and each message is limited to 1000 characters. Messages longer than 1000 characters will be truncated and any message past the 1024 limit will not be displayed.

Need to get in touch with us?

The FullStory Team awaits your every question.

Contact us