[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-02-11(UTC)"],[[["\u003cp\u003eThis page guides users on managing error groups within Error Reporting, where similar errors are grouped and a limited number of samples are kept for extrapolation.\u003c/p\u003e\n"],["\u003cp\u003eYou can change the resolution status of error groups to indicate their investigation state, with options such as Open, Acknowledged, Resolved, and Muted.\u003c/p\u003e\n"],["\u003cp\u003eError groups can be linked to external resources like issue trackers or documentation, providing easy access to related information.\u003c/p\u003e\n"],["\u003cp\u003eError Reporting allows for setting up notifications to alert users about new errors or the reoccurrence of resolved errors, and instructions on the configuration are provided.\u003c/p\u003e\n"],["\u003cp\u003eAll error events within a Google Cloud project can be deleted, using either the \u003ccode\u003egcloud\u003c/code\u003e tool or the REST API, but this will alter notification behaviour for reoccurring errors.\u003c/p\u003e\n"]]],[],null,["This page explains how you can manage your error groups in\nError Reporting.\n\nErrors that are grouped together are usually very similar, so\nError Reporting keeps only 1,000 samples and\nextrapolates the remaining information. To view all occurrences of an error,\nview the related logs with the Logs Explorer.\nFor more information about error grouping, see\n[How errors are grouped](/error-reporting/docs/grouping-errors).\n\n\u003cbr /\u003e\n\n| **Note** : If you see the message \"Set up Error Reporting\" on the **Error Reporting** page, then your Google Cloud project has no error groups to display.\n\n\u003cbr /\u003e\n\nBefore you begin\n\n- Ensure that you have least one error group. For more information, see [Collect error data by using Error Reporting](/error-reporting/docs/setup).\n\n\u003c!-- --\u003e\n\n-\n\n To get the permissions that\n you need to manage errors,\n\n ask your administrator to grant you the\n\n\n [Error Reporting User](/iam/docs/roles-permissions/errorreporting#errorreporting.user) (`roles/errorreporting.user`)\n IAM role on your project.\n\n\n For more information about granting roles, see [Manage access to projects, folders, and organizations](/iam/docs/granting-changing-revoking-access).\n\n\n You might also be able to get\n the required permissions through [custom\n roles](/iam/docs/creating-custom-roles) or other [predefined\n roles](/iam/docs/roles-overview#predefined).\n\nChange resolution status\n\nTo record the status of your investigation into an error group, do the\nfollowing:\n\n1. In the Google Cloud console, go to the **Error Reporting** page:\n\n [Go to **Error Reporting**](https://console.cloud.google.com/errors)\n\n \u003cbr /\u003e\n\n You can also find this page by using the search bar.\n2. On the error group that you want to update, click **Open**, and then select\n a resolution status. You can select any of the following values:\n\n - **Open** : The default initial state of all error groups. The other states are set manually. You can revert an error group's status back to **Open** at any time.\n - **Acknowledged**: A state for triaging error groups.\n - **Resolved** : A state for indicating that an error group is fixed and no longer expected to occur. If an error group marked as **Resolved** later reoccurs, then Error Reporting changes the resolution status back to **Open**.\n - **Muted**: A state for hiding an error group from your list. If a muted error reoccurs, then the error isn't included in the list of errors and you aren't notified.\n\nAdd links to error groups\n\nYou can link error groups to pages such as issue trackers\nor documentation with resolution steps.\n\n- To add a link to an error group, click\n *add* **Set the link to an issue tracker for this error group**,\n and then complete the dialog.\n\n- To edit the link on an error group, click\n *edit* **Set the link to an issue tracker for this error group**,\n and then complete the dialog.\n\n- To open the link for an error group, click\n *link* **Link to the issue tracker for this error group**.\n\nSet notifications\n\nError Reporting can notify you when new errors occur and when\nerrors that have been marked **Resolved** reoccur. To learn more, and for\ninstructions on setting notifications, see\n[Configure and manage notifications](/error-reporting/docs/notifications).\n\nDelete errors\n\nYou can delete all error events which are stored for the given\nGoogle Cloud project, and reset error counts to zero, using either the\n`gcloud` tool or the REST API. \n\ngcloud\n\nTo delete all error events, run this command: \n\n gcloud beta error-reporting events delete\n\nREST API\n\nTo delete all error events, use the\n[projects.deleteEvents](/error-reporting/reference/rest/v1beta1/projects/deleteEvents)\nmethod of the REST API.\n\nIf you subscribed to error\n[notifications](/error-reporting/docs/notifications) for the\nGoogle Cloud project and then deleted errors with a **Resolved** status,\nthen the resolution status changes back to **Open** and\nError Reporting sends a notification if the errors reoccur.\n\nIf you deleted errors with a status of **Open** or **Acknowledged**, then\nError Reporting doesn't send a notification if the errors\nreoccur.\n\nWhat's next\n\n- [Learn more about notifications](/error-reporting/docs/notifications)\n- [Learn more about viewing and filtering errors](/error-reporting/docs/viewing-errors)"]]
