mirror of
https://github.com/BillyOutlast/posthog.com.git
synced 2026-02-04 03:11:21 +01:00
67 lines
3.1 KiB
Plaintext
67 lines
3.1 KiB
Plaintext
---
|
|
title: Manage and resolve issues
|
|
---
|
|
|
|
Error tracking gives you multiple ways to help you manage issues and work towards resolution.
|
|
|
|
## Update issue status
|
|
|
|
You can update the status of an issue from the issue page under **Status** or issue list.
|
|
|
|
All issues are marked **Active** by default, you can mark them as **Resolved** or **Suppressed** to reflect the current state of the issue. These labels are mainly used to communicate amongst your team.
|
|
|
|
- Resolve issues that are fixed, if they reoccur, the issue is reopened.
|
|
- Suppress issues that you choose not to action. Typically, this is used for issues that are deemed noisy or not helpful.
|
|
|
|
You can also filter issues by status in the issue list:
|
|
|
|
<ProductScreenshot
|
|
imageLight="https://res.cloudinary.com/dmukukwp6/image/upload/filter_by_status_light_1f57d7d0b1.png"
|
|
imageDark="https://res.cloudinary.com/dmukukwp6/image/upload/filter_by_status_dark_f48d183989.png"
|
|
alt="Error tracking filter by issue status"
|
|
classes="rounded"
|
|
/>
|
|
|
|
A common workflow is to look for all issues that are **Active** assigned to you or your team, and triage them to be fixed or suppressed.
|
|
|
|
## View stack traces and event properties
|
|
|
|
Each issue contains detailed information about the exceptions that triggered it.
|
|
|
|
Click the **Stacktrace** tab to see exactly where the error occurred. [Stack traces](/docs/error-tracking/stack-traces) help you pinpoint the line of code and the sequence of function calls leading up to the exception.
|
|
|
|
<ProductScreenshot
|
|
imageLight="https://res.cloudinary.com/dmukukwp6/image/upload/issues_stacktrace_light_8e0c699ca2.png"
|
|
imageDark="https://res.cloudinary.com/dmukukwp6/image/upload/issues_stacktrace_dark_0b00f2d4fd.png"
|
|
alt="Error tracking stack traces"
|
|
classes="rounded"
|
|
/>
|
|
|
|
Under the **Properties** tab, you can view additional metadata about the exception event.
|
|
|
|
<ProductScreenshot
|
|
imageLight="https://res.cloudinary.com/dmukukwp6/image/upload/issues_properties_light_6fa900f42e.png"
|
|
imageDark="https://res.cloudinary.com/dmukukwp6/image/upload/issues_properties_dark_e973d3dfb2.png"
|
|
alt="Error tracking event properties"
|
|
classes="rounded"
|
|
/>
|
|
|
|
## Watch session replays
|
|
|
|
Error tracking works with [session replays](/docs/session-replay) to help you understand the context of an issue. This is useful for reproducing and debugging issues.
|
|
|
|
You can view a session replay for an exception by:
|
|
- Selecting an exception in the exception list and clicking the **Session** tab at the top of the page.
|
|
- Clicking the **View recording** button besides each exception.
|
|
|
|
<ProductScreenshot
|
|
imageLight="https://res.cloudinary.com/dmukukwp6/image/upload/session_replay_error_light_5f25f72344.png"
|
|
imageDark="https://res.cloudinary.com/dmukukwp6/image/upload/issue_exception_with_filter_dark_bf74dca1d9.png"
|
|
alt="An issue's session replay"
|
|
classes="rounded"
|
|
/>
|
|
|
|
## Assign issues to teammates
|
|
|
|
Issues can be [assigned to a teammate](/docs/error-tracking/assigning-issues) from the list or issue page. To do this, select the **assignee** option and search for the teammate you want to assign it to, and select them. You can click this dropdown again to remove the assignee.
|