Issues

Last updated:

|Edit this page|

What is an issue?

Errors are captured as $exception events which means that you can create insights, filter recordings, trigger surveys, and more in the same way you can for any other type of event.

Exception events are grouped into issues based on event information, such as the exception type, message, and stack trace. The data used for grouping depends on what is available. This enables you to evaluate which issues are most important and prioritize work on fixing them.

We're working on improving our grouping algorithm. If you spot two issues that you think should have been one, or one issue that you think should have been split into two, please let us know in-app.

You can also manually combine two or more issues by merging them.

Issue list

In addition to using events in insights, replays, and surveys as mentioned above customers can also visit the error tracking page.

Exceptions are grouped by type, each with aggregated counts and sparklines providing an indication of the severity of each group.

Error tracking overview

Issue page

Clicking through to an individual group shows you all the associated exceptions, including the associated stack trace, active feature flags when the exception was captured, and a link to the relevant session replay.

Error tracking issue page

Questions? Ask Max AI.

It's easier than reading through 698 pages of documentation

Community questions

Was this page useful?

Next article

Stack traces

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. 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…

Read next article