The Technical Details tab shows comprehensive data about an issue to help engineering teams diagnose and resolve it. It combines AI-driven insights and detailed technical information to streamline the process of reproducing and resolving an error.
- Error Details & Potential Solution
- Browser and OS breakdown
- Stacktrace and HTTP error details
- Last Reproduction Steps
Error Details & Potential Solution
The top section of this page lists the error message and error signature associated with the issue, as well an AI-generated summary of the cause based on available technical details.
For JavaScript issues, an AI-generated solution to the problem will be generated, if available. If a JavaScript error has a stacktrace that clearly defines the problematic line of code, Noibu uses AI to generate a suggested code snippet to fix the issue. This can be a helpful starting point for teams to begin implementing a fix.
Browser and OS breakdown
The Browser and OS impact charts show the distribution of issue occurrences broken out by browser, browser version, operating system, and operating system version. If an error's impact is significantly higher on a specific browser or OS, it may indicate there's an issue with how your code interacts with that specific browser or OS.
When analyzing these browser and OS charts, consider that the distribution of occurrences may be impacted by the market share of specific browsers and operating systems. For example,if the Browser Impact section indicates a majority of occurrences happen on Chrome, it's may be due to the market share of this browser, and not necessarily because Chrome is disproportionately affected by the issue.
By understanding which browsers and operating systems are most frequently impacted by an issue, a developer can set up an emulator with most relevant configuration when trying to reproduce the error.
Stacktrace and HTTP Error Details
Below the Browser and OS charts, Noibu provides granular technical information about where and how the issue occurs.
- For JavaScript errors, Noibu helps engineers find the exact line of code that triggered an error. Learn more about stack traces.
- For HTTP errors, Noibu will display the specific details needed to debug the error. Learn more about HTTP error details.
- For GraphQL errors, Noibu will show the source URL, error URL, and date the error was last seen. Additional detail may be presented if HTTP data collection is enabled. Learn more about How to Allow or Exclude URLs for Payload & Response
Last Reproduction Steps
The Last Reproduction Steps section summarizes the most common steps a customer took immediately preceding an error. The same error may occur at multiple steps in the customer journey, but this section helps you identify the step or steps at which the error usually occurred. This could be a click, a text entry, or a backend process like a page load. Click on one of the reproduction steps to open a list of session recordings that showcase the error at that reproduction step. Learn more about Sessions.