Merge branch 'main' into C3M-Library-content-GA

Author: JV0812

.clabot

@@ -191,7 +191,9 @@
     "naveenrama",
     "fguimond",
     "rmeyer-legato",
-    "jagan2221"
+    "jagan2221",
+    "pankaj101A",
+    "prajalb"
   ],
   "message": "Thank you for your contribution! As this is an open source project, we require contributors to sign our Contributor License Agreement and do not have yours on file. To proceed with your PR, please [sign your name here](https://forms.gle/YgLddrckeJaCdZYA6) and we will add you to our approved list of contributors.",
   "label": "cla-signed",

.github/workflows/workflow_deploy-to-pantheon-prod.yml

@@ -4,12 +4,14 @@ permissions:
   contents: write
 
 on:
-  workflow_dispatch:
   push:
     branches:
       - main
     paths-ignore:
       - .github/**
+      - .clabot
+      - CONTRIBUTING.md
+      - README.md
 
 jobs:
   build-site:

.github/workflows/workflow_deploy-to-pantheon-staging.yml

@@ -4,12 +4,14 @@ permissions:
   contents: write
 
 on:
-  workflow_dispatch:
   push:
     branches:
       - staging/**
     paths-ignore:
       - .github/**
+      - .clabot
+      - CONTRIBUTING.md
+      - README.md
 
 jobs:
   build-site:

blog-collector/2025-10-13-installed.md

@@ -0,0 +1,30 @@
+---
+title: Version 19.533-5 (Installed Collector)
+hide_table_of_contents: true
+image: https://assets-www.sumologic.com/company-logos/_800x418_crop_center-center_82_none/SumoLogic_Preview_600x600.jpg?mtime=1617040082
+---
+
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+In this release, we've added two important updates to Installed Collectors to enhance performance, security, and ensure long-term support.
+
+:::note
+Starting January 31, 2026, Sumo Logic will no longer support the collectors using Java Runtime Environment (JRE) versions older than 17 and will end support for Installed Collectors running on WIN 32 machines.
+
+To ensure continued compatibility and support, upgrade your collectors to JRE 17 or later and migrate your collectors to Windows 64-bit or another supported operating system before this date.
+:::
+
+## Java upgrade and end of support for legacy versions
+
+With Java 8 reaching its end of public updates in January 2019, and with newer Java versions offering significant improvements in both performance and security, we are upgrading our Installed Collectors to Java 17. This change applies differently depending on how your collectors are configured:
+
+- **For collectors using default Sumo Logic bundled Corretto JRE**. This deprecation will not affect you as the upgrade to JRE 17 happens automatically when you update your collector to version 19.533-5. *No immediate action is required*.
+- **For collectors with custom JRE setups**. If you're using a custom JRE configuration, including binary installer-based deployments, custom deployment scripts, or containerized collectors with JRE 8 or 11, you must manually upgrade to JRE 17 to maintain compatibility and support. After January 31, 2026, your existing collectors will continue to run. However, you will not be able to upgrade or download new collector versions using JRE 8 or 11.
+
+## End of support for Windows 32-bit (WIN 32) systems
+
+To align with Microsoft’s end-of-life for Windows 32-bit systems and ensure a secure, stable platform for all users, Sumo Logic will end support for Installed Collectors running on WIN 32 machines from January 31, 2026. After this date, the collectors on WIN 32 will no longer be supported and upgrades and new collector downloads for WIN 32 will be disabled.
+
+To maintain support and access to the latest features, migrate your collectors to Windows 64-bit or another supported operating system as soon as possible.
+
+[Learn more](/docs/send-data/collection/upgrade-collectors/#upgradecollectors-to-the-latest-build).

blog-collector/2025-10-20-installed.md

@@ -11,7 +11,3 @@ hide_table_of_contents: true
 We're excited to annouce the new **AutoPause** feature for Scheduled Views, designed to enhance system performance and optimize resource usage.
 
 With AutoPause, any Scheduled View that remains inactive for 90 consecutive days (that is, not queried or referenced) will be automatically flagged and paused. To ensure you're informed ahead of time, Scheduled View owners and active account administrators will receive email and in-app notifications 21 days and 7 days before the scheduled pause. If no action is taken, the view will be automatically paused on the 90th day, followed by a final alert. [Learn more](/docs/manage/scheduled-views/pause-disable-scheduled-views/).
-
-:::note
-This feature is currently available only for Canada (Central), Asia Pacific (Tokyo), and Asia Pacific (Seoul) regions.
-:::

blog-service/2025-10-15-manage.md

@@ -0,0 +1,12 @@
+---
+title: Varonis Alerts Source (Collection)
+image: https://assets-www.sumologic.com/company-logos/_800x418_crop_center-center_82_none/SumoLogic_Preview_600x600.jpg?mtime=1617040082
+keywords:
+  - c2c
+  - varonis-alerts-source
+hide_table_of_contents: true    
+---
+
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+We're excited to announce the release of our new cloud-to-cloud source for Varonis Alerts. This source securely collects alerts from the Varonis platform and sends them to Sumo Logic for streamlined analysis. [Learn more](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/varonis-source).

blog-service/2025-10-22-collection.md

@@ -1848,6 +1848,7 @@
   "/cid/10341": "/docs/send-data/opentelemetry-collector/remote-management/source-templates/postgresql",
   "/cid/10342": "/docs/send-data/opentelemetry-collector/remote-management/source-templates/mysql",
   "/cid/10343": "/docs/send-data/opentelemetry-collector/remote-management/source-templates/elasticsearch",
+  "/cid/10348": "/docs/send-data/opentelemetry-collector/remote-management/source-templates/customyaml",
   "/cid/10325": "/docs/send-data/opentelemetry-collector/remote-management/source-templates/apache/changelog",
   "/cid/10326": "/docs/send-data/opentelemetry-collector/remote-management/source-templates/linux/changelog",
   "/cid/10327": "/docs/send-data/opentelemetry-collector/remote-management/source-templates/localfile/changelog",
@@ -1864,6 +1865,7 @@
   "/cid/10345": "/docs/send-data/opentelemetry-collector/remote-management/source-templates/mysql/changelog",
   "/cid/10346": "/docs/send-data/opentelemetry-collector/remote-management/source-templates/elasticsearch/changelog",
   "/cid/10347": "/docs/send-data/opentelemetry-collector/remote-management/source-templates/st-with-secrets",
+  "/cid/10349": "/docs/send-data/opentelemetry-collector/remote-management/source-templates/customyaml/changelog",
   "/cid/10817": "/docs/integrations/sumo-apps/cse",
   "/cid/10818": "/docs/integrations/sumo-apps/cse",
   "/cid/1082": "/docs/metrics/introduction/get-started-metrics",
@@ -2949,6 +2951,7 @@
   "/docs/integrations/microsoft-azure/microsoft-defender-for-identity/": "/docs/integrations/microsoft-azure/azure-security-microsoft-defender-for-identity",
   "/cid/1112": "/docs/integrations/saas-cloud/carbon-black-inventory/",  
   "/cid/1111": "/docs/integrations/microsoft-azure/azure-open-ai",
+  "/cid/1114": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/varonis-source",
   "/cid/1115": "/docs/integrations/microsoft-azure/azure-security-microsoft-defender-for-cloud-apps",
   "/docs/integrations/microsoft-azure/microsoft-defender-for-cloud-apps/": "/docs/integrations/microsoft-azure/azure-security-microsoft-defender-for-cloud-apps",
   "/cid/1116": "/docs/integrations/microsoft-azure/azure-security-microsoft-entra-id-protection",

cid-redirects.json

@@ -39,19 +39,6 @@ import MetricsSource from '../../reuse/metrics-source.md';
 
 <MetricsSource/>
 
-### Configure logs collection
-
-#### Diagnostic logs
-
-In this section, you will configure a pipeline for shipping diagnostic logs from [Azure Monitor](https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-get-started) to an Event Hub.
-
-1. To set up the Azure Event Hubs source in Sumo Logic, refer to [Azure Event Hubs Source for Logs](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/).
-2. To create the **Diagnostic setting** in the Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-gb/azure/data-factory/monitor-configure-diagnostics). Perform the steps below for each Azure Functions that you want to monitor.
-   1. Choose `Stream to an event hub` as the destination.
-   1. Select `AllMetrics`.
-   1. Use the Event Hub namespace and Event Hub name configured in previous step in destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.<br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-App-Service-Plan-Configure-Diagnostic-Metrics.png')} alt="Azure App Service Plan Tag Location" style={{border: '1px solid gray'}} width="800" />
-3. Tag the location field in the source with right location value.<br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-Storage-Tag-Location.png')} alt="Azure Storage Tag Location" style={{border: '1px solid gray'}} width="400" />
-
 #### Activity logs (optional)
 
 import ActivityLogs from '../../reuse/apps/azure-activity-logs.md';

docs/integrations/microsoft-azure/azure-app-service-plan.md

@@ -29,10 +29,8 @@ For Azure Cosmos DB, you can collect the following logs and metrics:
 
 * **Resource logs**. To learn more about the different resource log category types and schemas collected for Azure Cosmos DB, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/cosmos-db/monitor-reference#resource-logs).
 
-* **Platform Metrics for Azure Cosmos DB**. For more information on supported metrics and dimensions, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/cosmos-db/monitor-reference#metrics). These metrics are available in the following namespaces:
-   * `Microsoft.DocumentDB/applicationGateways`
-   * `Microsoft.DocumentDB/cassandraClusters`
-   * `Microsoft.DocumentDB/mongoClusters`
+* **Platform Metrics for Azure Cosmos DB**. For more information on supported metrics and dimensions, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/cosmos-db/monitor-reference#metrics). These metrics are available within the namespace `Microsoft.DocumentDB/DatabaseAccounts`
+
 * **Activity logs**. Provides insight into any subscription-level or management group level events that have occurred in the Azure. To learn more, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/activity-log-schema).
 
 ## Setup