Skip to main content
Console Logs

Using Console Logs to Improve Bug Tracking with Marker.io

Gary Gaspar avatar
Written by Gary Gaspar
Updated today

Below we walk through how to set up and use console logs in Marker.io. With this feature, you can capture important technical information when users report issues. This makes it easier to reproduce and fix bugs quickly.


What Are Console Logs?

Console logs are records of errors and messages that occur in the browser while a website is running. When someone reports an issue through Marker.io, these logs can provide valuable insights into what went wrong. This is like taking a snapshot of what happened at the moment an issue occurred, helping your team quickly pinpoint problems.


How to Enable Console Logs

  1. Access Settings:

    • Go to your project settings in Marker.io.

    • Navigate to Widget > Metadata > Console Logs.

  2. Install the Widget:

    • Ensure your widget is installed and linked to at least one website domain.

    • For best results, install the widget using the JavaScript snippet code. This is a small piece of code you add to your website to make the widget work. If you can’t access your website’s code, you can use the Marker.io browser extension. Click here for more details on using the browser extension.

Once the widget is set up and console logs are enabled, any issues reported will automatically include the relevant console logs.


Using Console Logs

After you've set up console logs, here's how they help you:

  • When a developer receives a bug report, they'll see a link to the console logs if any errors or warnings were recorded.

  • Clicking on this link will show the full console logs as they were captured when the issue happened. It's like having a time machine for bugs!

  • This information saves time by reducing back-and-forth communication, allowing developers to focus on fixing the problem.


Types of Console Logs Recorded

Here are the types of logs Marker.io currently records:

  • console.trace(): Shows the path through the code that led to a certain point.

  • console.debug(): Used for debugging purposes.

  • console.info(): Provides informational messages.

  • console.warn(): Highlights potential issues.

  • console.error(): Displays error messages.

  • console.log(): General output of logging information.

Also, any uncaught errors and rejected promises will be captured and shown in the logs.

Shortly, we will add support for timings, profiling, and more.


Need Help?

If you have any questions, comments, or corrections, chat with us at the bottom right of our web pages.

Did this answer your question?