DOCS-512 - Remove Root Cause Explorer (#5306)

jpipkin1 · web-flow · commit ef099523d6c1 · 2025-06-03T17:44:15.000Z
* Remove Root Cause Explorer * Add redirects * Fix build break * Fix broken links * Remove phrase for PR #5343 * Changed dates to 23 May 2025 * Change date to 27 May 2025 * Change date to June 3 2025
diff --git a/blog-service/2021/12-31.md b/blog-service/2021/12-31.md
@@ -649,7 +649,7 @@ Update - We have updated our [Enterprise Audit - Security Management App](/docs
 ---
 ## March 4, 2021 (Observability)
 
-Update - We're delighted to announce several enhancements to [Root Cause Explorer](/docs/observability/root-cause-explorer "Root Cause Explorer"). Root Cause Explorer now supports two additional AWS namespaces, as well as Events of Interest detection on Kubernetes and Trace metrics. Cause-impact analysis is now informed by Sumo Logic Tracing's Service Map, AWS X-ray, Kubernetes entities, and AWS inventory relationships. You'll also notice new filters and search builders at the top of the page to correlate Events of Interests at the service, orchestrator, AWS infrastructure, and host levels to speed up the identification of  root causes. You can use the Infrastructure tab for an Event of Interest to pivot to dashboards, logs, metrics and, trace searches to take the next steps in root cause analysis. 
+Update - We're delighted to announce several enhancements to Root Cause Explorer. Root Cause Explorer now supports two additional AWS namespaces, as well as Events of Interest detection on Kubernetes and Trace metrics. Cause-impact analysis is now informed by Sumo Logic Tracing's Service Map, AWS X-ray, Kubernetes entities, and AWS inventory relationships. You'll also notice new filters and search builders at the top of the page to correlate Events of Interests at the service, orchestrator, AWS infrastructure, and host levels to speed up the identification of  root causes. You can use the Infrastructure tab for an Event of Interest to pivot to dashboards, logs, metrics and, trace searches to take the next steps in root cause analysis. 
 
 ---
 ## March 1, 2021 (Metrics)
diff --git a/blog-service/2024/12-31.md b/blog-service/2024/12-31.md
@@ -294,7 +294,7 @@ We're excited to announce the general availability of AI-driven alerts for metri
 
 #### Deprecation Notice - Root Cause Explorer
 
-As part of our ongoing evaluation of the Sumo Logic service, our product team is deprecating [Root Cause Explorer](/docs/observability/root-cause-explorer), and it will no longer be available as of 30 April 2025.
+As part of our ongoing evaluation of the Sumo Logic service, our product team is deprecating Root Cause Explorer, and it will no longer be available as of 3 June 2025.
 
 Learn more [here](/docs/observability/root-cause-explorer-deprecation).
 
diff --git a/blog-service/2025-06-03-observability.md b/blog-service/2025-06-03-observability.md
@@ -0,0 +1,14 @@
+---
+title: End-of-Life Notice - Root Cause Explorer (Observability)
+image: https://help.sumologic.com/img/sumo-square.png
+keywords:
+  - apps
+  - sumo-collection
+hide_table_of_contents: true    
+---
+
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+Previously, we announced that Root Cause Explorer [was deprecated](/release-notes-service/2024/12/31/#november-01-2024-observability). As of 3 June 2025, Root Cause Explorer has reached its end of life and is no longer available.
+
+Learn more [here](/docs/observability/root-cause-explorer-deprecation/).
diff --git a/cid-redirects.json b/cid-redirects.json
@@ -1642,7 +1642,7 @@
   "/cid/6029": "/docs/integrations/saas-cloud/kaltura",
   "/cid/6030": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/snowflake-logs-source",
   "/cid/10112": "/docs/integrations/app-development/jfrog-xray",
-  "/cid/10113": "/docs/observability/root-cause-explorer",
+  "/cid/10113": "/docs/observability/root-cause-explorer-deprecation",
   "/cid/10116": "/docs/manage/fields",
   "/cid/10117": "/docs/metrics/metrics-transformation-rules",
   "/cid/10118": "/docs/metrics/metric-rules-editor",
@@ -3535,7 +3535,7 @@
   "/Observability_Solution/Reliability_Management/Creating_SLOs_and_Monitors": "/docs/observability/reliability-management-slo",
   "/Observability_Solution/Reliability_Management/SLO_Dashboards": "/docs/observability/reliability-management-slo",
   "/docs/observability/reliability-management-slo/use-cases": "/docs/observability/reliability-management-slo",
-  "/Observability_Solution/Root_Cause_Explorer": "/docs/observability/root-cause-explorer",
+  "/Observability_Solution/Root_Cause_Explorer": "/docs/observability/root-cause-explorer-deprecation",
   "/Other_Solutions": "/docs/observability",
   "/Other_Solutions/Software_Development_Optimization_Solution/01_About_the_Software_Development_Optimization_Solution": "/docs/observability/sdo/about-sdo",
   "/Other_Solutions/Software_Development_Optimization_Solution/02_Supported_Tools_and_Schema": "/docs/observability/sdo/supported-tools-schema",
@@ -3920,8 +3920,8 @@
   "/Metrics/Metrics-Sources/03Graphite-Source-for-Metrics": "/docs/send-data/installed-collectors/sources/host-metrics-source",
   "/Metrics/Working-with-Metrics/03-Create-a-Metrics-Visualization": "/docs/metrics/metrics-queries/metrics-explorer",
   "/Observability_Solution/AWS_Observability_Solution/01_Deploy_and_Use_AWS_Observability/11Configure_Alerts": "/docs/observability/aws/deploy-use-aws-observability",
-  "/Observability_Solution/AWS_Observability_Solution/01_Deploy_and_Use_AWS_Observability/12Root_Cause_Explorer": "/docs/observability/root-cause-explorer",
-  "/Observability_Solution/AWS_Observability_Solution/01_Deploy_and_Use_AWS_Observability/Root_Cause_Explorer": "/docs/observability/root-cause-explorer",
+  "/Observability_Solution/AWS_Observability_Solution/01_Deploy_and_Use_AWS_Observability/12Root_Cause_Explorer": "/docs/observability/root-cause-explorer-deprecation",
+  "/Observability_Solution/AWS_Observability_Solution/01_Deploy_and_Use_AWS_Observability/Root_Cause_Explorer": "/docs/observability/root-cause-explorer-deprecation",
   "/Observability_Solution/Kubernetes_Solution/01Set_up_collection_for_Kubernetes": "/docs/observability/kubernetes/collection-setup",
   "/Observability_Solution/Kubernetes_Solution/Global_Intelligence_for_Kubernetes_DevOps_App": "/docs/integrations/global-intelligence/kubernetes-devops",
   "/Observability_Solution/Kubernetes_Solution/Navigate_your_Kubernetes_environment": "/docs/observability/kubernetes",
@@ -4140,7 +4140,7 @@
   "/Solutions/AWS_Observability_Solution/05_Monitor_Control_Tower-Managed_Accounts": "/docs/observability/aws/other-configurations-tools/integrate-control-tower-accounts",
   "/Solutions/AWS_Observability_Solution/AWS_Observability_Application_Load_Balancer": "/docs/observability/aws/integrations/aws-application-load-balancer",
   "/Solutions/AWS_Observability_Solution/View_AWS_Observability_Solution_Dashboards": "/docs/observability/aws/deploy-use-aws-observability/view-dashboards",
-  "/Solutions/AWS_Observability_Solution/Root_Cause_Explorer": "/docs/observability/root-cause-explorer",
+  "/Solutions/AWS_Observability_Solution/Root_Cause_Explorer": "/docs/observability/root-cause-explorer-deprecation",
   "/Solutions/AWS_Observability_Solution/03_Set_Up_the_AWS_Observability_Solution": "/docs/observability/aws/about",
   "/Solutions/AWS_Observability_Solution/About_the_AWS_Observability_Solution": "/docs/observability/aws/about",
   "/Solutions/AWS_Observability_Solution/Set_Up_the_AWS_Observability_Solution": "/docs/observability/aws",
diff --git a/docs/alerts/monitors/alert-response-faq.md b/docs/alerts/monitors/alert-response-faq.md
@@ -107,7 +107,7 @@ Anomaly cards only work if we are able to infer an entity from the alerting quer
 
 ## Where are Anomaly cards for metrics-based alerts?
 
-Alert response anomaly detection only detects anomalies for metrics data coming from Kubernetes or specific sources within AWS ([learn more](../../observability/root-cause-explorer.md)). If you are setting up alerts on metrics that don’t belong to either one of these categories, anomalies will not be detected.
+Alert response anomaly detection only detects anomalies for metrics data coming from Kubernetes or specific sources within AWS. If you are setting up alerts on metrics that don’t belong to either one of these categories, anomalies will not be detected.
 
 Use the [Sumo Logic Kubernetes collection](https://github.com/SumoLogic/sumologic-kubernetes-collection#sumologic-kubernetes-collection) or the [Sumo Logic AWS observability collection](/docs/observability/aws) for this to work properly. 
 
diff --git a/docs/alerts/monitors/alert-response.md b/docs/alerts/monitors/alert-response.md
@@ -202,14 +202,14 @@ The **Log Fluctuations** context card, available for logs monitors, detects diff
 
 ### Anomalies
 
-This card detects time series anomalies for entities related to the alert. These insights are powered by the [Root Cause Explorer](../../observability/root-cause-explorer.md).
+This card detects time series anomalies for entities related to the alert.
 
 Anomalies are grouped into [golden signals](https://sre.google/sre-book/monitoring-distributed-systems/). Anomalies are also presented on a timeline; the length of the anomaly represents its duration. <br/> ![anomalies .png](/img/alerts/monitors/anomalies.png)
 
 * **A**. Name and description of the context card.
 * **B**. Count of anomalies belonging to each golden signal type.
 * **C**. A timeline view of anomalies with their start time and duration, the domain (e.g. AWS, Kubernetes), and the entity on which it was detected. Anomalies may be grouped based on connections between entities and similarity of metrics. For example, anomalies on EC2 instances that are members of an AutoScaling group may be grouped together. The count shown in each anomaly refers to the number of grouped anomalies.
-* **D**. A link to view the anomalies in the **Root Cause Explorer**.
+* **D**. A link to view the anomalies.
 
 :::note
 Only anomalies with a start time around 30 minutes before or after the alert was created show up in the card.
diff --git a/docs/apm/index.md b/docs/apm/index.md
@@ -50,6 +50,3 @@ Monitor user activity, span analytics, service maps, and transaction traces betw
 
 <br/>
 
-:::tip
-Use our [Root Cause Explorer](/docs/observability/root-cause-explorer) to investigate usage and issues.
-:::
diff --git a/docs/cse/administration/inventory-sources-and-data.md b/docs/cse/administration/inventory-sources-and-data.md
@@ -34,7 +34,7 @@ Some of the inventory sources are strictly for collecting inventory data—such
 Some inventory sources provide user inventory information, some provide computer inventory information, and some provide both. The table below lists currently available inventory sources.
 
 :::note
-The AWS Inventory Source collects the inventory of AWS resources in your AWS account, but is usable only by the Root Cause Explorer. See [AWS Inventory Source](/docs/observability/root-cause-explorer/#aws-inventory-source).
+The AWS Inventory Source collects the inventory of AWS resources in your AWS account.
 :::
 
 | Inventory source | Type of source | Inventory data collected |
diff --git a/docs/dashboards/drill-down-to-discover-root-causes.md b/docs/dashboards/drill-down-to-discover-root-causes.md
@@ -7,10 +7,6 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
 
 When you see a spike of interest on a dashboard that requires further investigation, you can easily drill into the related content to discover the root cause. This page shows you how you can easily discover related dashboards and corresponding logs searches that pertain to an issue in your environment.
 
-:::note
-If you're looking for our Root Cause Explorer observability tool, [click here](/docs/observability/root-cause-explorer).
-:::
-
 ## Drilling into related content
 
 Sumo Logic provides relevant log searches and dashboards to consider investigating, as well as other locations with relevant content. This facilitates quickly discovering the root cause and devising a plan of action.
diff --git a/docs/get-started/ai-machine-learning.md b/docs/get-started/ai-machine-learning.md
@@ -77,12 +77,6 @@ Sumo Logic offers seamless integrations with various AI-driven platforms to enab
 * [Criminal IP](/docs/platform-services/automation-service/app-central/integrations/criminal-ip)
 * [Arcanna](/docs/platform-services/automation-service/app-central/integrations/arcanna)
 
-<!-- Removed - not in Kanso
-### Root Cause Explorer
-
-Accelerates troubleshooting by surfacing events of interest correlated with application incidents. [Learn more](/docs/observability/root-cause-explorer)
--->
-
 ## Security
 
 Our Sumo Logic AI for Security functionality empowers SOC analysts and threat hunters to effectively safeguard their technology stack against evolving threats. By integrating advanced tools for discovery, detection, investigation, response, and protection, we minimize dwell time, reduce false positives, accelerate incident resolution, and proactively prevent future incidents, ensuring robust security and resilience for your cloud, container, and on-prem resources.
diff --git a/docs/get-started/sumo-logic-ui-classic.md b/docs/get-started/sumo-logic-ui-classic.md
@@ -133,7 +133,6 @@ To launch a search, metrics visualization, or live tail session, do the followin
    * [Live Tail](/docs/search/live-tail). View a real-time live feed of log events associated with a Source or Collector.
    * [Explore](/docs/dashboards/explore-view). See an intuitive visual hierarchy of your environment.
    * [Dashboard](/docs/dashboards/). Analyze metrics and log data on the same dashboard, in a streamlined user experience.
-   * [Root Cause](/docs/observability/root-cause-explorer). Accelerate troubleshooting and isolate root causes for incidents in your apps and microservices.
 
 ### View recent dashboards and searches 
 
diff --git a/docs/manage/manage-subscription/fedramp-capabilities.md b/docs/manage/manage-subscription/fedramp-capabilities.md
@@ -49,7 +49,6 @@ The following table shows the capabilities included with Sumo Logic’s FedRAMP
 | Collection - Amazon Web Services | [AWS Kinesis Firehose for Metrics](/docs/send-data/hosted-collectors/amazon-aws/aws-kinesis-firehose-metrics-source/) |![check](/img/reuse/check.png)|![check](/img/reuse/check.png)|
 | Collection - Amazon Web Services | [AWS Inventory](/docs/observability/aws/deploy-use-aws-observability/resources/) |![check](/img/reuse/check.png)|![x](/img/reuse/x.png) |
 | Collection - Amazon Web Services | [AWS Metadata](/docs/send-data/hosted-collectors/amazon-aws/aws-metadata-tag-source/) |![check](/img/reuse/check.png)|![check](/img/reuse/check.png)|
-| Collection - Amazon Web Services | [AWS XRay](/docs/observability/root-cause-explorer/#aws-x-ray-source) |![check](/img/reuse/check.png)|![check](/img/reuse/check.png)|
 | Collection - Amazon Web Services | [CSE AWS EC2 Inventory](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/cse-aws-ec-inventory-source/) |![check](/img/reuse/check.png)|![x](/img/reuse/x.png) |
 | Collection - Archive | [AWS S3 archive](/docs/manage/data-archiving/archive) |![check](/img/reuse/check.png)|![check](/img/reuse/check.png)|
 | Collection - Cloud APIs | [Akamai SIEM API](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/akamai-siem-api-source/) |![check](/img/reuse/check.png)|![check](/img/reuse/check.png)<br/>*Available upon request within 5 business days.* |
diff --git a/docs/manage/manage-subscription/sumo-logic-credits-accounts.md b/docs/manage/manage-subscription/sumo-logic-credits-accounts.md
@@ -106,7 +106,6 @@ The following table provides a summary list of key features by Credits package a
 | Partitions | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) |
 | PCI Compliance App |  | ![check](/img/reuse/check.png) |  | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) |
 | Real User Monitoring (RUM) | | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) |
-| Root Cause Explorer | | | | ![check](/img/reuse/check.png) | | ![check](/img/reuse/check.png) |
 | SAML | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) |
 | Scheduled Views | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) |
 | Search Job API |  | ![check](/img/reuse/check.png) |  | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) |
diff --git a/docs/manage/manage-subscription/sumo-logic-flex-accounts.md b/docs/manage/manage-subscription/sumo-logic-flex-accounts.md
@@ -130,7 +130,6 @@ The following table provides a summary list of key features by Flex package acco
 | Real User Monitoring (RUM) |  | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) |![check](/img/reuse/check.png) |
 | Reliability Management (SLIs/SLOs) |  | | |![check](/img/reuse/check.png) |
 | Risk Assessment |  | ![check](/img/reuse/check.png) | |![check](/img/reuse/check.png) |
-| Root Cause Explorer |  |  | | ![check](/img/reuse/check.png) |
 | Scheduled Alert Muting | |  | |![check](/img/reuse/check.png) |
 | Scheduled Views | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) | ![check](/img/reuse/check.png) |
 | Service Maps |  | ![check](/img/reuse/check.png) | |![check](/img/reuse/check.png) |
diff --git a/docs/observability/about.md b/docs/observability/about.md
@@ -74,4 +74,4 @@ The solution also offers features and capabilities that support each step of the
 
 * **Monitor** your systems effectively with new and improved alerting and dashboarding capabilities. The Observability Solution includes rich pre-built content that you can leverage to quickly start monitoring specific services. 
 * **Diagnose** issues quickly using features like the Entity Explorer, trace analytics, and the  Metrics Explorer.  
-* **Troubleshoot** issues and find root causes through Behavior insights, Root Cause Explorer, and log search.
+* **Troubleshoot** issues and find root causes through behavior insights and log search.
diff --git a/docs/observability/index.md b/docs/observability/index.md
@@ -31,12 +31,6 @@ In this section, we'll introduce the following concepts:
       <p>Set alerts that notify you about system state changes.</p>
       </div>
     </div>
-    <div className="box smallbox card">
-      <div className="container">
-      <a href="/docs/observability/root-cause-explorer"><img src={useBaseUrl('img/icons/observe.png')} alt="icon" width="35"/><h4>Root Cause Explorer</h4></a>
-      <p>Troubleshoot app and microservice incidents and isolate root causes.</p>
-      </div>
-    </div>
     <div className="box smallbox card">
       <div className="container">
       <a href="/docs/observability/aws"><img src={useBaseUrl('img/icons/observe.png')} alt="icon" width="35"/><h4>AWS Observability</h4></a>
@@ -67,6 +61,6 @@ In this section, we'll introduce the following concepts:
 
 #### Other solutions and apps for infrastructure monitoring
 
-These ready-to-run apps are a good starting point for monitoring critical parts of your infrastructure that support a work-from-home workforce:  
-* [Work from Home Solution](/docs/observability/work-from-home-vpn). This solution allows you to monitor all aspects of the infrastructure you use to enable employees to work from home, safely and securely—including your productivity apps, and the services you use for SSO, remote access, endpoint security.   
+These ready-to-run apps are a good starting point for monitoring critical parts of your infrastructure that support a work-from-home workforce:
+* [Work from Home Solution](/docs/observability/work-from-home-vpn). This solution allows you to monitor all aspects of the infrastructure you use to enable employees to work from home, safely and securely—including your productivity apps, and the services you use for SSO, remote access, endpoint security.
 * [Sumo Logic App for Cisco Meraki](/docs/integrations/security-threat-detection/cisco-meraki). You can use this app to monitor and troubleshoot network security, end-to-end performance, switch port management, and device management of your Cisco Meraki wireless infrastructure management platform.  
diff --git a/docs/observability/root-cause-explorer-deprecation.md b/docs/observability/root-cause-explorer-deprecation.md
diff --git a/docs/observability/root-cause-explorer.md b/docs/observability/root-cause-explorer.md
diff --git a/docs/observability/troubleshoot.md b/docs/observability/troubleshoot.md
diff --git a/i18n/ja/alerts/alerts/monitors/alert-response.md b/i18n/ja/alerts/alerts/monitors/alert-response.md
diff --git a/sidebars.ts b/sidebars.ts
diff --git a/static/img/get-started/ui/TUI_Left_Nav.png b/static/img/get-started/ui/TUI_Left_Nav.png
diff --git a/static/img/get-started/ui/WTS_UI_Home_landing-page.png b/static/img/get-started/ui/WTS_UI_Home_landing-page.png
diff --git a/static/img/get-started/ui/home-icons.png b/static/img/get-started/ui/home-icons.png

-Original file line number
+Diff line change
 <br/>
 -:::tip
 -Use our [Root Cause Explorer](/docs/observability/root-cause-explorer) to investigate usage and issues.
 -:::