Stack traces

Last updated:

|Edit this page|

Error tracking enables you to view the stack trace and code context associated with an exception. This can help understand, identify and resolve the root cause of an issue.

For languages like Python, the stack trace and code context can be gathered by the PostHog client and requires no additional processing.

Stack traces example

Symbol sets

Compiled or minified languages requires additional information to perform a process called symbolification to produce the same stack trace and code context output shown above. The additional information is known as a symbol set.

The source of a frame in the exception stack trace should point to the minified code of your application which should contain the sourceMappingUrl parameter denoting the location of the source map. These files must either be publicly accessible for PostHog to fetch or uploaded manually to symbolify the stack trace.

You can see the symbol sets fetched by PostHog and the associated frames within the error tracking settings. Any missing symbol sets will also be present along with the failure reason. From here, you can also manually upload missing symbol sets or replace existing ones.

Symbol set examples

Uploading source maps

If your source maps are not publicly hosted, you will need to upload them during your build process to see unminified code in your stack traces. You can either use the @posthog/nextjs-config package or the posthog-cli to handle this process. Select your platform to view instructions.

Questions? Ask Max AI.

It's easier than reading through 698 pages of documentation

Community questions

Was this page useful?

Next article

Searching and monitoring issues

Finding specific issues You can use the search bar at the top of the issue page to filter issues based on the properties of the exceptions in that issue. Search results are matched based on properties of exceptions grouped into the issues. For example, if you search for "TypeError", we show you all issues where any exception grouped into the issue has a type of "TypeError". You may see seemingly unrelated issues in your search results because your search term matches an exception in the…

Read next article