Merge branch 'main' of github.com:SumoLogic/sumologic-documentation into det-1326-correct-custom-rule-article

Author: jpipkin1

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)

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

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/).

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",

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. 
 

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.

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

docs/contributing/style-guide.md

@@ -439,6 +439,39 @@ _sourceCategory=reinvent/travel/checkout
 
 For a full list of options, see [Docusaurus Code Blocks](https://docusaurus.io/docs/markdown-features/code-blocks).
 
+### Import GitHub repo file
+
+To embed a code sample from a file in a GitHub repository, use `reference` in the code block with a link to the file. The code sample is embedded using the language with a link to the original file.
+
+This code references a json script file:
+
+<Tabs
+  className="unique-tabs"
+  defaultValue="Markdown"
+  values={[
+    {label: 'Markdown', value: 'Markdown'},
+    {label: 'Result', value: 'Result'},
+  ]}>
+
+<TabItem value="Markdown">
+
+<img src={useBaseUrl('img/contributing/json-ref-codeblock.png')} alt="JSON code snippet from GitHub" style={{border: '1px solid gray'}} width="700"/>
+
+</TabItem>
+<TabItem value="Result">
+
+```json reference
+https://github.com/SumoLogic/sumologic-documentation/blob/main/static/files/c2c/1password/example.json
+```
+
+</TabItem>
+</Tabs>
+
+Optionally, you can:
+* Reference a specific range of code lines by appending `#L` with the line number or numbers at the end of the URL. For example, `https://github.com/SumoLogic/sumologic-documentation/blob/main/static/files/c2c/1password/example.json#L4-L5`.
+* Add a title to the code block, such as `json reference title="Hello"`.
+
+You'll see this used in our [C2C source docs](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework).
 
 ## Collapsible text blocks
 

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 |

docs/cse/records-signals-entities-insights/entity-criticality.md

@@ -19,7 +19,7 @@ If the formula you specify results in a number that isn’t whole, the value is
 
 ## About criticality and insight generation
 
-The maximum severity that can be assigned to a Cloud SIEM rule is 10, so normally, signal severity is also limited to 1. Note however that Cloud SIEM doesn’t impose a maximum value on the severity that results from a criticality, although the minimum value will always be 0. 
+The maximum severity that can be assigned to a Cloud SIEM rule is 10, so normally, signal severity is also limited to 10. Note however that Cloud SIEM doesn’t impose a maximum value on the severity that results from a criticality, although the minimum value will always be 0. 
 
 As described in the [insight generation](/docs/cse/get-started-with-cloud-siem/insight-generation-process/) topic, an insight is generated on an entity based on the cumulative severity of the unique signals that have fired on it over the previous two weeks, unless a different period is configured. The cumulative
 severity is referred to as the entity’s activity score. Keep in mind that higher signal severities will increase an entity’s activity score and result in insight’s being generated sooner.