이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.
이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

Overview

All issues in Error Tracking have a status to help you triage and prioritize issues or dismiss noise. There are five statuses:

  • FOR REVIEW: New or regressed issues that need attention.
  • REVIEWED: Triaged issues that need to be fixed, now or later.
  • RESOLVED: Issues that have been fixed and are no longer occurring.
  • IGNORED: Issues that require no further investigation or action.
  • EXCLUDED: Issues that require no further investigation, stops collecting new errors, and no longer count towards usage or billing

All issues start with a FOR REVIEW status. Error Tracking automatically updates the status in the cases described below, or you can manually update the status. You can also view the history of a given error’s state changes.

The diagram below shows how the Error Tracking states are updated automatically and manually:

Error Tracking Issue States

Automatic review

Error Tracking automatically marks issues as REVIEWED if one of the following actions has been taken:

  • The issue has been assigned
  • A case has been created from the issue
Error Tracking automatic review actions

Automatic resolution

Error Tracking automatically marks issues as RESOLVED that appear to be inactive or resolved due to a lack of recent error occurrences:

  • If the issue was last reported in a version that is more than 14 days old, and a newer version has been released but does not report the same error, Error Tracking automatically resolves the issue. Configure your services with version tags (see instructions for APM, RUM, and Logs) to ensure that automatic resolution accounts for versions of your services.
  • If version tags are not set up, Error Tracking automatically resolves an issue if there have been no new errors reported for that issue within the last 14 days.

Automatic re-opening through regression detection

See Regression Detection.

Updating the issue status

The issue status appears anywhere the issue can be viewed, such as in the issues list or on the details panel for a given issue. To manually update the status of an issue, click the status and choose a different one in the dropdown menu.

The Activity Timeline in the Error Tracking Issue

Excluding an issue

The EXCLUDED status lets you prevent specific errors from being tracked, ensuring they are not collected or counted toward billing. This helps you remove non-actionable errors or issues caused by expected failures without needing complex exclusion rules.

To exclude an issue, click its status and choose EXCLUDED in the dropdown menu. Excluded issues are still accessible in the IGNORED tab. You can review their history at any time.

Excluded in issue status dropdown

To resume collecting errors for an excluded issue, select any status other than EXCLUDED.

Issue history

View a history of your issue activity with the Activity Timeline. On the details panel of any Error Tracking issue, view the Activity Timeline by clicking the Activity tab.

The Activity Timeline in the Error Tracking Issue

Further Reading

추가 유용한 문서, 링크 및 기사: