Skip to content

Commit ef09952

Browse files
authored
DOCS-512 - Remove Root Cause Explorer (#5306)
* 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
1 parent 798c3fc commit ef09952

24 files changed

+36
-639
lines changed

blog-service/2021/12-31.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -649,7 +649,7 @@ Update - We have updated our [Enterprise Audit - Security Management App](/docs
649649
---
650650
## March 4, 2021 (Observability)
651651

652-
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. 
652+
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. 
653653

654654
---
655655
## March 1, 2021 (Metrics)

blog-service/2024/12-31.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -294,7 +294,7 @@ We're excited to announce the general availability of AI-driven alerts for metri
294294

295295
#### Deprecation Notice - Root Cause Explorer
296296

297-
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.
297+
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.
298298

299299
Learn more [here](/docs/observability/root-cause-explorer-deprecation).
300300

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
title: End-of-Life Notice - Root Cause Explorer (Observability)
3+
image: https://help.sumologic.com/img/sumo-square.png
4+
keywords:
5+
- apps
6+
- sumo-collection
7+
hide_table_of_contents: true
8+
---
9+
10+
import useBaseUrl from '@docusaurus/useBaseUrl';
11+
12+
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.
13+
14+
Learn more [here](/docs/observability/root-cause-explorer-deprecation/).

cid-redirects.json

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1642,7 +1642,7 @@
16421642
"/cid/6029": "/docs/integrations/saas-cloud/kaltura",
16431643
"/cid/6030": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/snowflake-logs-source",
16441644
"/cid/10112": "/docs/integrations/app-development/jfrog-xray",
1645-
"/cid/10113": "/docs/observability/root-cause-explorer",
1645+
"/cid/10113": "/docs/observability/root-cause-explorer-deprecation",
16461646
"/cid/10116": "/docs/manage/fields",
16471647
"/cid/10117": "/docs/metrics/metrics-transformation-rules",
16481648
"/cid/10118": "/docs/metrics/metric-rules-editor",
@@ -3535,7 +3535,7 @@
35353535
"/Observability_Solution/Reliability_Management/Creating_SLOs_and_Monitors": "/docs/observability/reliability-management-slo",
35363536
"/Observability_Solution/Reliability_Management/SLO_Dashboards": "/docs/observability/reliability-management-slo",
35373537
"/docs/observability/reliability-management-slo/use-cases": "/docs/observability/reliability-management-slo",
3538-
"/Observability_Solution/Root_Cause_Explorer": "/docs/observability/root-cause-explorer",
3538+
"/Observability_Solution/Root_Cause_Explorer": "/docs/observability/root-cause-explorer-deprecation",
35393539
"/Other_Solutions": "/docs/observability",
35403540
"/Other_Solutions/Software_Development_Optimization_Solution/01_About_the_Software_Development_Optimization_Solution": "/docs/observability/sdo/about-sdo",
35413541
"/Other_Solutions/Software_Development_Optimization_Solution/02_Supported_Tools_and_Schema": "/docs/observability/sdo/supported-tools-schema",
@@ -3920,8 +3920,8 @@
39203920
"/Metrics/Metrics-Sources/03Graphite-Source-for-Metrics": "/docs/send-data/installed-collectors/sources/host-metrics-source",
39213921
"/Metrics/Working-with-Metrics/03-Create-a-Metrics-Visualization": "/docs/metrics/metrics-queries/metrics-explorer",
39223922
"/Observability_Solution/AWS_Observability_Solution/01_Deploy_and_Use_AWS_Observability/11Configure_Alerts": "/docs/observability/aws/deploy-use-aws-observability",
3923-
"/Observability_Solution/AWS_Observability_Solution/01_Deploy_and_Use_AWS_Observability/12Root_Cause_Explorer": "/docs/observability/root-cause-explorer",
3924-
"/Observability_Solution/AWS_Observability_Solution/01_Deploy_and_Use_AWS_Observability/Root_Cause_Explorer": "/docs/observability/root-cause-explorer",
3923+
"/Observability_Solution/AWS_Observability_Solution/01_Deploy_and_Use_AWS_Observability/12Root_Cause_Explorer": "/docs/observability/root-cause-explorer-deprecation",
3924+
"/Observability_Solution/AWS_Observability_Solution/01_Deploy_and_Use_AWS_Observability/Root_Cause_Explorer": "/docs/observability/root-cause-explorer-deprecation",
39253925
"/Observability_Solution/Kubernetes_Solution/01Set_up_collection_for_Kubernetes": "/docs/observability/kubernetes/collection-setup",
39263926
"/Observability_Solution/Kubernetes_Solution/Global_Intelligence_for_Kubernetes_DevOps_App": "/docs/integrations/global-intelligence/kubernetes-devops",
39273927
"/Observability_Solution/Kubernetes_Solution/Navigate_your_Kubernetes_environment": "/docs/observability/kubernetes",
@@ -4140,7 +4140,7 @@
41404140
"/Solutions/AWS_Observability_Solution/05_Monitor_Control_Tower-Managed_Accounts": "/docs/observability/aws/other-configurations-tools/integrate-control-tower-accounts",
41414141
"/Solutions/AWS_Observability_Solution/AWS_Observability_Application_Load_Balancer": "/docs/observability/aws/integrations/aws-application-load-balancer",
41424142
"/Solutions/AWS_Observability_Solution/View_AWS_Observability_Solution_Dashboards": "/docs/observability/aws/deploy-use-aws-observability/view-dashboards",
4143-
"/Solutions/AWS_Observability_Solution/Root_Cause_Explorer": "/docs/observability/root-cause-explorer",
4143+
"/Solutions/AWS_Observability_Solution/Root_Cause_Explorer": "/docs/observability/root-cause-explorer-deprecation",
41444144
"/Solutions/AWS_Observability_Solution/03_Set_Up_the_AWS_Observability_Solution": "/docs/observability/aws/about",
41454145
"/Solutions/AWS_Observability_Solution/About_the_AWS_Observability_Solution": "/docs/observability/aws/about",
41464146
"/Solutions/AWS_Observability_Solution/Set_Up_the_AWS_Observability_Solution": "/docs/observability/aws",

docs/alerts/monitors/alert-response-faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ Anomaly cards only work if we are able to infer an entity from the alerting quer
107107

108108
## Where are Anomaly cards for metrics-based alerts?
109109

110-
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.
110+
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.
111111

112112
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. 
113113

docs/alerts/monitors/alert-response.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -202,14 +202,14 @@ The **Log Fluctuations** context card, available for logs monitors, detects diff
202202

203203
### Anomalies
204204

205-
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).
205+
This card detects time series anomalies for entities related to the alert.
206206

207207
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)
208208

209209
* **A**. Name and description of the context card.
210210
* **B**. Count of anomalies belonging to each golden signal type.
211211
* **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.
212-
* **D**. A link to view the anomalies in the **Root Cause Explorer**.
212+
* **D**. A link to view the anomalies.
213213

214214
:::note
215215
Only anomalies with a start time around 30 minutes before or after the alert was created show up in the card.

docs/apm/index.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,3 @@ Monitor user activity, span analytics, service maps, and transaction traces betw
5050

5151
<br/>
5252

53-
:::tip
54-
Use our [Root Cause Explorer](/docs/observability/root-cause-explorer) to investigate usage and issues.
55-
:::

docs/cse/administration/inventory-sources-and-data.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Some of the inventory sources are strictly for collecting inventory data—such
3434
Some inventory sources provide user inventory information, some provide computer inventory information, and some provide both. The table below lists currently available inventory sources.
3535

3636
:::note
37-
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).
37+
The AWS Inventory Source collects the inventory of AWS resources in your AWS account.
3838
:::
3939

4040
| Inventory source | Type of source | Inventory data collected |

docs/dashboards/drill-down-to-discover-root-causes.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,6 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
77

88
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.
99

10-
:::note
11-
If you're looking for our Root Cause Explorer observability tool, [click here](/docs/observability/root-cause-explorer).
12-
:::
13-
1410
## Drilling into related content
1511

1612
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.

docs/get-started/ai-machine-learning.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -77,12 +77,6 @@ Sumo Logic offers seamless integrations with various AI-driven platforms to enab
7777
* [Criminal IP](/docs/platform-services/automation-service/app-central/integrations/criminal-ip)
7878
* [Arcanna](/docs/platform-services/automation-service/app-central/integrations/arcanna)
7979

80-
<!-- Removed - not in Kanso
81-
### Root Cause Explorer
82-
83-
Accelerates troubleshooting by surfacing events of interest correlated with application incidents. [Learn more](/docs/observability/root-cause-explorer)
84-
-->
85-
8680
## Security
8781

8882
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.

0 commit comments

Comments
 (0)