diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml index daca03a3e54..954a4535f9b 100644 --- a/config/_default/menus/main.en.yaml +++ b/config/_default/menus/main.en.yaml @@ -2357,11 +2357,6 @@ menu: parent: error_tracking identifier: error_tracking_monitors weight: 6 - - name: Issue Correlation - url: error_tracking/issue_correlation - parent: error_tracking - identifier: error_tracking_issue_correlation - weight: 7 - name: Identify Suspect Commits url: error_tracking/suspect_commits parent: error_tracking diff --git a/config/_default/menus/main.es.yaml b/config/_default/menus/main.es.yaml index f67138c8321..3a6e51f9440 100644 --- a/config/_default/menus/main.es.yaml +++ b/config/_default/menus/main.es.yaml @@ -2217,11 +2217,6 @@ menu: parent: error_tracking identifier: error_tracking_monitors weight: 6 - - name: Issue Correlation - url: error_tracking/issue_correlation - parent: error_tracking - identifier: error_tracking_issue_correlation - weight: 7 - name: Identificar confirmaciones sospechosas url: error_tracking/suspect_commits parent: error_tracking diff --git a/config/_default/menus/main.fr.yaml b/config/_default/menus/main.fr.yaml index ef3febcba36..86e3c703083 100644 --- a/config/_default/menus/main.fr.yaml +++ b/config/_default/menus/main.fr.yaml @@ -2217,11 +2217,6 @@ menu: parent: error_tracking identifier: error_tracking_monitors weight: 6 - - name: Issue Correlation - url: error_tracking/issue_correlation - parent: error_tracking - identifier: error_tracking_issue_correlation - weight: 7 - name: Identify Suspect Commits url: error_tracking/suspect_commits parent: error_tracking diff --git a/config/_default/menus/main.ja.yaml b/config/_default/menus/main.ja.yaml index 04f954e5982..599f2abd9cc 100644 --- a/config/_default/menus/main.ja.yaml +++ b/config/_default/menus/main.ja.yaml @@ -2217,11 +2217,6 @@ menu: parent: error_tracking identifier: error_tracking_monitors weight: 6 - - name: Issue Correlation - url: error_tracking/issue_correlation - parent: error_tracking - identifier: error_tracking_issue_correlation - weight: 7 - name: Identify Suspect Commits url: error_tracking/suspect_commits parent: error_tracking diff --git a/config/_default/menus/main.ko.yaml b/config/_default/menus/main.ko.yaml index 635b0d24fc2..d64fd9e2632 100644 --- a/config/_default/menus/main.ko.yaml +++ b/config/_default/menus/main.ko.yaml @@ -2217,11 +2217,6 @@ menu: parent: error_tracking identifier: error_tracking_monitors weight: 6 - - name: Issue Correlation - url: error_tracking/issue_correlation - parent: error_tracking - identifier: error_tracking_issue_correlation - weight: 7 - name: 추정 커밋 식별 url: error_tracking/suspect_commits parent: error_tracking diff --git a/content/en/error_tracking/_index.md b/content/en/error_tracking/_index.md index 84731e44186..2de69d0aa70 100644 --- a/content/en/error_tracking/_index.md +++ b/content/en/error_tracking/_index.md @@ -1,5 +1,7 @@ --- title: Error Tracking +aliases: +- /error_tracking/issue_correlation/ disable_toc: false further_reading: - link: "/ide_plugins/idea/error_tracking/" diff --git a/content/en/error_tracking/issue_correlation.md b/content/en/error_tracking/issue_correlation.md deleted file mode 100644 index 44515cc8b14..00000000000 --- a/content/en/error_tracking/issue_correlation.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Issue Correlation with Error Tracking -description: Understand how errors are grouped into issues. -further_reading: -- link: '/monitors/types/error_tracking' - tag: 'Documentation' - text: 'Learn about Error Tracking Monitors' -- link: '/error_tracking/issue_states/' - tag: 'Documentation' - text: 'Issue States in Error Tracking' ---- -{{< callout url="https://www.datadoghq.com/product-preview/error-tracking-issue-correlation/">}} -Issue Correlation with Error Tracking is currently in Preview, but you can easily request access! Use this form to submit your request. Once approved, you can automatically map related issues across services, helping you trace problems to their true origin. -{{< /callout >}} -## Overview - -{{< img src="error_tracking/issue-correlation-overview-2.png" alt="The view of the correlated issues tab in the context of the Error Tracking Explorer" style="width:100%;" >}} - -You use Error Tracking to simplify debugging by grouping thousands of similar errors into a single issue. Use issue correlation to determine the cause of the issue, the impact it has on other services, and if the error is a result of a downstream dependency. - -Issue correlation also helps reduce noise from the issue list by identifying the most critical issues. This allows you to alert the right team and reach a quicker resolution. - -## Identify correlated issues -To identify which issues across your services are correlated, navigate to the Error Tracking page at [{{< ui >}}Error{{< /ui >}} > {{< ui >}}Issues{{< /ui >}}][1]. - -{{< img src="error_tracking/issue-correlation-et-page-2.png" alt="The issues list in the Error Tracking Explorer" style="width:70%;" >}} - -Select an issue to open the issue's details side panel. - -{{< img src="error_tracking/issue-correlation-side-panel-2.png" alt="The details of an issue in the Error Tracking Explorer" style="width:70%;" >}} - -Open the {{< ui >}}Correlated issues{{< /ui >}} tab to see the issue correlation map. - -{{< img src="error_tracking/issue-correlation-correlation-tab-2.png" alt="The details of an issue in the Error Tracking Explorer focusing on the issue correlation tab" style="width:70%;" >}} - -The issue correlation map shows the following information about a given issue: -- {{< ui >}}Root cause{{< /ui >}}: the services that are likely to be causing the issue -- {{< ui >}}Current issue{{< /ui >}}: the issue selected along with whether it is assigned to a team -- {{< ui >}}Impact{{< /ui >}}: the resources, users, and sessions that are impacted - - -## Further Reading - -{{< partial name="whats-next/whats-next.html" >}} - - - -[1]: https://app.datadoghq.com/error-tracking diff --git a/content/es/error_tracking/issue_correlation.md b/content/es/error_tracking/issue_correlation.md deleted file mode 100644 index 5000fbdb910..00000000000 --- a/content/es/error_tracking/issue_correlation.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -description: Entiende cómo se agrupan los errores en incidentes. -further_reading: -- link: /monitors/types/error_tracking - tag: Documentación - text: Más información sobre los monitores de seguimiento de errores -- link: /error_tracking/issue_states/ - tag: Documentación - text: Estados de incidentes en Error Tracking -title: Correlación de incidentes con Error Tracking ---- -{{< callout url="https://www.datadoghq.com/product-preview/error-tracking-issue-correlation/" d-toggle="modal" d_target="#signupModal" custom_class="sign-up-trigger">}} -La Correlación de incidentes con Error Tracking está actualmente en vista previa, pero puedes solicitar acceso fácilmente. Utiliza este formulario para enviar tu solicitud. Una vez aprobada, podrás asignar automáticamente incidentes relacionados entre servicios, lo que te ayudará a rastrear el verdadero origen de un incidente. -{{< /callout >}} -## Información general - -{{< img src="error_tracking/issue-correlation-overview-2.png" alt="Vista de la pestaña de incidentes correlacionados en el contexto del explorador de Error Tracking" style="width:100%;" >}} - -Utiliza Error Tracking para simplificar la depuración agrupando miles de errores similares en un único incidente. Utiliza la correlación de incidentes para determinar la causa del incidente, el impacto que tiene en otros servicios y si el error es consecuencia de una dependencia posterior. - -La correlación de incidentes también ayuda a reducir el ruido de la lista de incidentes identificando los más críticos. Esto te permite alertar al equipo adecuado y lograr una resolución más rápida. - -## Identificar incidentes correlacionados -Para identificar qué incidentes de tus servicios están correlacionadas, ve a la página de Error Tracking en [**Error > Issues** (Error > Incidentes)][1]. - -{{< img src="error_tracking/issue-correlation-et-page-2.png" alt="Lista de incidentes en el explorador de Error Tracking" style="width:70%;" >}} - -Selecciona un incidente para abrir el panel lateral y ver su información. - -{{< img src="error_tracking/issue-correlation-side-panel-2.png" alt="Información de un incidente en el explorador de Error Tracking" style="width:70%;" >}} - -Abre la pestaña `Correlated issues` para ver el mapa de correlación de incidentes. - -{{< img src="error_tracking/issue-correlation-correlation-tab-2.png" alt="Información de un incidente en el explorador de Error Tracking, centrada en la pestaña de correlación de incidentes" style="width:70%;" >}} - -El mapa de correlación de incidentes muestra la siguiente información de un incidente determinado: -- **Root cause** (Causa de origen): servicios que probablemente estén causando el incidente -- **Current issue** (Incidente actual): incidente seleccionado y si está asignado a un equipo -- **Impact** (Impacto): recursos, usuarios y sesiones afectados - - -## Referencias adicionales - -{{< partial name="whats-next/whats-next.html" >}} - - - -[1]: https://app.datadoghq.com/error-tracking \ No newline at end of file