Merge branch 'main' into azure-servicebus-doc-update

Author: amee-sumo

blog-csoar/2025-02-06-application-update.md

@@ -9,7 +9,7 @@ hide_table_of_contents: true
 
 import useBaseUrl from '@docusaurus/useBaseUrl';
 
-
+## January release
 
 ### Changes and Enhancements
 

blog-csoar/2025-02-24-application-update.md

@@ -9,7 +9,7 @@ hide_table_of_contents: true
 
 import useBaseUrl from '@docusaurus/useBaseUrl';
 
-
+## February release
 
 ### Changes and Enhancements
 

blog-csoar/2025-04-21-content.md

@@ -1,5 +1,5 @@
 ---
-title: April 21, 2025 - Content Release
+title: April 21, 2025 - Application Update
 hide_table_of_contents: true
 image: https://help.sumologic.com/img/sumo-square.png
 keywords:

blog-csoar/2025-06-03-application-update.md

@@ -0,0 +1,56 @@
+---
+title: June 3, 2025 - Application Update
+hide_table_of_contents: true
+image: https://help.sumologic.com/img/sumo-square.png
+keywords:
+  - automation service
+  - cloud soar
+  - soar
+---
+
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+## May release
+
+### Changes and enhancements
+
+#### New feature: Enable/disable playbooks
+
+This feature allows users to easily enable or disable playbooks without deleting them, offering greater control over their execution.
+
+What's new:
+* Switch playbooks' status to enabled or disabled directly from the playbook details page.
+* The playbooks listing page now shows a status column to display the status of the playbooks.
+* Disabled playbooks will not execute from any linked triggers like monitors, insights, or incident rules, enhancing operational safety.
+* By default, playbooks with any published version are set to enabled, while those that are draft-only or have been deleted remain disabled.
+* Audit logs are generated whenever playbooks are enabled or disabled manually.
+
+For more information, see [Enable or disable playbooks](/docs/platform-services/automation-service/automation-service-playbooks/#enable-or-disable-playbooks).
+
+#### Integrations
+
+* [NEW] [Google Workspace IDP](/docs/platform-services/automation-service/app-central/integrations/google-workspace-idp/) – This integration automates user and group management in Google Workspace, simplifying identity and access control for improved security and efficiency.
+* [UPDATED] [Microsoft EWS Daemon](/docs/platform-services/automation-service/app-central/integrations/microsoft-ews-daemon/) - Enhanced the handling of email attachments that may lack file extension, ensuring consistent detection and processing.
+* [UPDATED] [TheHive](/docs/platform-services/automation-service/app-central/integrations/thehive/) - Modified TheHive integration with case and observable enhancements:
+   * Fixed parsing issues for date related inputs with inconsistent formatting.
+   * Fixed SSL-related warning issues.
+   * Added organization name field in resource which will included in the headers.
+   * Enhanced error handling and made the integration more resilient to malformed inputs.
+* [UPDATED] [Sumo Logic Automation Tools](/docs/platform-services/automation-service/app-central/integrations/sumo-logic-automation-tools/) - Introduced the new "Scaled Decimal to Percentage" action, which converts a scaled decimal value into a percentage.
+* [UPDATED] [Microsoft Sentinel](/docs/platform-services/automation-service/app-central/integrations/microsoft-sentinel/) - Enhanced the "Microsoft Sentinel Incidents Daemon" action, and added support to seamlessly fetch subsequent paginated data.
+
+### Bug Fixes
+
+#### Playbooks
+
+* Fixed an issue where users were unable to use the "Answer by Email" option when selecting  the authorizer as a playbook input variable.
+* Fixed long text getting cropped in filter and conditions nodes preview.
+
+#### Rules
+
+* Resolved an issue where empty keys within nested list objects were not properly filtered during rule execution. This fix ensures accurate evaluation of `isnot` and `notcontains` conditions by excluding empty keys, resulting in improved data processing accuracy and rule performance.
+
+#### Incidents
+
+* Resolved data loading issue on incidents and triage listing tables.
+* Fixed issue related to user redirection to the logic page on session timeout.

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,9 @@
   "/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",
+  "/docs/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 +4141,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.