Merge branch 'main' into threat-intel-ga

Author: jpipkin1

blog-service/2025-01-08-otel-remote-management.md

@@ -0,0 +1,23 @@
+---
+title: Remote Management for OpenTelemetry Collector (Collection)
+image: https://help.sumologic.com/img/sumo-square.png
+keywords:
+  - collection
+  - opentelemetry
+  - otel
+  - remote-management
+hide_table_of_contents: true    
+---
+
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+<a href="https://help.sumologic.com/release-notes-service/rss.xml"><img src={useBaseUrl('img/release-notes/rss-orange2.png')} alt="icon" width="50"/></a>
+
+The Sumo Logic Distribution for OpenTelemetry Collector now supports remote management, enabling you to configure and manage data collection directly from the Sumo Logic UI. With this feature, you can:  
+
+* **Simplify configuration**. Set up and manage data collection for multiple collectors without server access.  
+* **Streamline workflows**. Use tags to group collectors and apply centralized data source templates, reducing redundancy and manual effort.  
+* **Enhance automation**. Automatically monitor new servers by tagging them during setup.  
+* **Accelerate time to value**. Start collecting data in minutes with an intuitive UI and no need to manage configuration files.  
+
+This release provides a faster, more efficient way to manage large-scale data collection, supporting scalable and automated operations. [Learn more](/docs/send-data/opentelemetry-collector/remote-management).  

cid-redirects.json

@@ -115,6 +115,7 @@
   "/03Send-Data/Collect-from-Other-Data-Sources/Auto-Subscribe_AWS_Log_Groups_to_a_Lambda_Function": "/docs/send-data/collect-from-other-data-sources/autosubscribe-arn-destination",
   "/03Send-Data/Collect-from-Other-Data-Sources/AWS_Fargate_log_collection": "/docs/send-data/collect-from-other-data-sources/aws-fargate-log-collection",
   "/03Send-Data/Collect-from-Other-Data-Sources/Azure_Blob_Storage": "/docs/send-data/collect-from-other-data-sources/azure-blob-storage/block-blob/collect-logs",
+  "/03Send-Data/Collect-from-Other-Data-Sources/Azure_Blob_Storage/Collect_Logs_for_the_Azure_Blob_Storage_App": "/docs/send-data/collect-from-other-data-sources/azure-blob-storage/block-blob/collect-logs",
   "/03Send-Data/Collect-from-Other-Data-Sources/Azure_Blob_Storage/Collect_Logs_from_Azure_Blob_Storage": "/docs/send-data/collect-from-other-data-sources/azure-blob-storage/block-blob/collect-logs",
   "/03Send-Data/Collect-from-Other-Data-Sources/Azure_Blob_Storage/Troubleshoot_Azure_Blob_Storage_Log_Collection": "/docs/send-data/collect-from-other-data-sources/azure-blob-storage/troubleshoot-log-collection",
   "/03Send-Data/Collect-from-Other-Data-Sources/Azure_Monitoring": "/docs/send-data/collect-from-other-data-sources/azure-monitoring",
@@ -2675,7 +2676,7 @@
   "/cid/9008": "/docs/alerts/webhook-connections/new-relic",
   "/cid/10333": "/docs/send-data/opentelemetry-collector/remote-management/processing-rules",
   "/cid/10334": "/docs/send-data/opentelemetry-collector/remote-management/processing-rules/include-and-exclude-rules",
-  "/cid/10335": "/docs/send-data/opentelemetry-collector/remote-management/processing-rules/metrics-include-and-exclude-rules",
+  "/cid/10335": "/docs/send-data/opentelemetry-collector/remote-management/processing-rules/include-and-exclude-rules",
   "/cid/10336": "/docs/send-data/opentelemetry-collector/remote-management/processing-rules/mask-rules",
   "/cid/9010": "/docs/send-data/opentelemetry-collector",
   "/cid/9011": "/docs/send-data/opentelemetry-collector/install-collector/linux",
@@ -2974,6 +2975,7 @@
   "/Internal_Writers/Topic_Archive/Parse_by_Data_Type/Parse_Apache_Logs/Parse_Apache_Error_Logs": "/docs/search/get-started-with-search/suggested-searches/apache-errors-parser",
   "/Internal_Writers/Topic_Archive/Parse_by_Data_Type/Parse_Cisco_ASA_Logs": "/",
   "/Knowledge_Base/Apps": "/docs/integrations",
+  "/Knowledge_Base/Parsing/Using_line_breaks_as_an_anchor_within_parse": "/docs/search/search-query-language/parse-operators/parse-predictable-patterns-using-an-anchor",
   "/Knowledge_Base/Search/How_to_Prevent_your_Scheduled_Search_from_Timing_Out": "/docs/alerts/scheduled-searches/faq",
   "/Limited_Availability/Lookup_Tables/lookupContains_Operator": "/docs/search/search-query-language/search-operators/lookupcontains",
   "/Manage": "/docs/manage",
@@ -3092,6 +3094,7 @@
   "/docs/dashboards-new/panels/scatter-charts": "/docs/dashboards/panels/scatter-charts",
   "/docs/dashboards-new/panels/single-value-charts": "/docs/dashboards/panels/single-value-charts",
   "/docs/dashboards-new/panels/table-charts": "/docs/dashboards/panels/table-charts",
+  "/Manage/Connections": "/docs/alerts/webhook-connections",
   "/Manage/Connections/Webhook_Connections": "/docs/alerts/webhook-connections",
   "/Manage/Connections/Webhook_Connections/About_Webhook_Connections": "/docs/alerts/webhook-connections",
   "/Manage/Connections/Webhook_Connections/Use_the_Audit_Index_with_Webhook_Connections": "/docs/alerts/webhook-connections/audit-index",
@@ -3344,6 +3347,7 @@
   "/Metrics/Metric-Queries-and-Alerts/09Metric_Query_Error_Messages": "/docs/metrics/metrics-queries/metric-query-error-messages",
   "/Metrics/Metric-Queries-and-Alerts/Metric_Aggregation_Tips": "/docs/metrics/metrics-queries/aggregation-tips",
   "/Metrics/Metric-Queries-and-Alerts/Filter_Time_Series": "/docs/dashboards/panels",
+  "/Monitor_and_Alert": "/docs/alerts",
   "/Monitor_and_Alert/Alerts": "/docs/alerts",
   "/Monitor_and_Alert/Dashboards/About_Dashboards": "/docs/dashboards/about",
   "/Monitor_and_Alert/Alerts/Why_Would_a_Scheduled_Search_Fail": "/docs/alerts/scheduled-searches/faq",
@@ -3472,6 +3476,7 @@
   "/release-notes-service/welcome": "/release-notes-service",
   "/release-notes-service/2023/11/27/cis-for-aws": "/release-notes-service/2023/12/31/#november-27-2023-apps",
   "/release-notes-service/2042/06/10/manage": "/release-notes-service/2024/12/31",
+  "/release-notes-service/2024/03/20/flex/": "/release-notes-service/2024/12/31/#march-20-2024-manage",
   "/Send-Data/Applications-and-Other-Data-Sources/Azure-Audit/02Collect-Logs-for-Azure-Audit-from-Event-Hub": "/docs/integrations/microsoft-azure/audit",
   "/Send-Data/Collect-from-Other-Data-Sources/Azure_Monitoring/Collect_Logs_from_Azure_Monitor": "/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/",
   "/Send-Data/Collect-from-Other-Data-Sources/Azure_Monitoring/Collect_Metrics_from_Azure_Monitor": "/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor",
@@ -3646,6 +3651,7 @@
   "/01Start-Here/01About-Sumo-Logic/What-is-the-optimal-log-format-to-use-with-Sumo-Logic": "/docs/get-started/faq",
   "/01Start-Here/01About-Sumo-Logic/Where-is-My-Data-Stored": "/docs/get-started/faq",
   "/01Start-Here/01About-Sumo-Logic/Forgot-Password": "/docs/get-started/account-settings-preferences",
+  "/01Start-Here/01About-Sumo-Logic/System-Requirements/Installed-Collector-Requirements": "/docs/get-started/system-requirements",
   "/01Start-Here/01About-Sumo-Logic/System-Requirements/Supported-Browsers": "/docs/get-started/system-requirements",
   "/03-send-data/installed-collectors": "/docs/send-data/installed-collectors",
   "/03Send-Data/Collect-from-Other-Data-Sources/Collect_Logs_from_AWS_Lambda_using_Lambda_Extension": "/docs/send-data/collect-from-other-data-sources/collect-aws-lambda-logs-extension",
@@ -3706,6 +3712,7 @@
   "/APIs/02Search_Job_API/About_the_Search_Job_API": "/docs/api/search-job",
   "/APIs/02Search_Job_API/Search_Job_API_Reference": "/docs/api/search-job",
   "/APIs/02Sumo-Logic-APIs/Deployment-Specific-Endpoints": "/docs/api/getting-started",
+  "/APIs/03Search_Job_API": "/docs/api/search-job",
   "/Apps/01_Apps_in_Sumo_Logic/Custom_Data_Filters": "/docs/get-started/apps-integrations",
   "/Apps/02_Active_Directory_App": "/docs/integrations/microsoft-azure/active-directory-azure",
   "/Apps/05_Amazon_VPC_Flow_Logs_App/Amazon_VPC_Flow_Logs_App_Dashboards": "/docs/integrations/amazon-aws/vpc-flow-logs",
@@ -3722,6 +3729,7 @@
   "/Apps/Installing_Apps_from_the_Library": "/docs/get-started/apps-integrations",
   "/Apps/Linux_App/Linux_App_Dashboards": "/docs/integrations/hosts-operating-systems/linux",
   "/Apps/Linux_Performance_App/Collect_Logs_for_the_Linux_Performance_App": "/docs/integrations/hosts-operating-systems/linux",
+  "/Apps/Preview_Apps/Cylance": "/docs/integrations/security-threat-detection/cylance",
   "/Apps/Preview_Apps/Cylance_App": "/docs/integrations/security-threat-detection/cylance",
   "/Apps/Preview_Apps/AWS_Lambda/AWS_Lambda_App_Dashboards": "/docs/integrations/amazon-aws/lambda",
   "/Apps/Preview_Apps/Amazon_EC2_Container_Service_(ECS)_App": "/docs/integrations/amazon-aws/ec2-host-metrics",
@@ -3748,6 +3756,7 @@
   "/Beta/Dashboard-Data-API": "/docs/api/dashboard",
   "/Beta/Dashboard_(New)": "/docs/dashboards",
   "/Beta/Dashboard_(Beta)/Create_a_New_Dashboard_(Beta)": "/docs/dashboards",
+  "/Beta/Fields": "/docs/manage/fields",
   "/Beta/Grant_Access_to_Data_in_Audit_Indexes": "/docs/manage/users-roles/roles/create-manage-roles",
   "/Beta/Health_Events": "/docs/manage/health-events",
   "/Beta/Ingest_Budgets": "/docs/manage/ingestion-volume/ingest-budgets",
@@ -4104,6 +4113,7 @@
   "/docs/dashboards/edit-dashboards": "/docs/dashboards",
   "/docs/dashboards/chart-panel-types/numerical-single-value-charts": "/docs/dashboards/panels/single-value-charts",
   "/docs/dashboards/edit-dashboards/manage-axis": "/docs/dashboards",
+  "/docs/dashboards/edit-dashboards/manage-dashboards": "/docs/dashboards",
   "/docs/dashboards/chart-panel-types/box-plot-charts": "/docs/dashboards/panels/box-plot-charts",
   "/docs/dashboards/chart-panel-types/line-charts": "/docs/dashboards/panels/line-charts",
   "/docs/dashboards/chart-panel-types/table-charts": "/docs/dashboards/panels/table-charts",

docs/manage/partitions/data-tiers/faq.md

@@ -29,7 +29,7 @@ In contrast, debug or other verbose log sources that are only used to troublesho
 
 You can use [Role-Based Access Control (RBAC)](/docs/manage/users-roles/roles/role-based-access-control) to restrict access to partitions in the Infrequent or Frequent Tiers. Although you can’t use a role search filter to restrict access to a partition by name, you can filter by the metadata that forms the routing expression for a partition. 
 
-For example, if you want to strict access to a partition whose routing expression is:
+For example, if you want to restrict access to a partition whose routing expression is:
 
 ```
 _sourceCategory=staging/*

docs/manage/partitions/flex/faq.md

@@ -28,7 +28,7 @@ With Flex Pricing, there is no cost to ingest and index log data, and no require
 
 Yes, you can use [Role-Based Access Control (RBAC)](/docs/manage/users-roles/roles/role-based-access-control) to restrict access to partitions in Flex. Although you can’t use a role search filter to restrict access to a partition by name, you can filter by the metadata that forms the routing expression for a partition.
 
-For example, if you want to strict access to a partition whose routing expression is:
+For example, if you want to restrict access to a partition whose routing expression is:
 
 ```
 _sourceCategory=staging/*

docs/reuse/apps/opentelemetry/collector-installation.md

@@ -1,17 +1,14 @@
-import useBaseUrl from '@docusaurus/useBaseUrl';
+In this step, we'll install the collector and add a uniquely identifiable tag to these collectors.
 
-In this step, we will install the collector and add a uniquely identifiable tag to these collectors.
+1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Collection > OpenTelemetry Collection**.<br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the Sumo Logic top menu select **Configuration**, and then under **Data Collection** select **OpenTelemetry Collection**. You can also click the **Go To...** menu at the top of the screen and select **OpenTelemetry Collection**.
+1. On the **OpenTelemetry Collection** page, click **+ Add Collector**.
+1. In the **Set up Collector** step:
+   1. Choose your platform (for example, Linux).
+   1. Enter your **Installation Token**.
+   1. Under **Tag data on Collector level**, add a new tag to identify these collectors as having Apache running on them (for example, `application = Apache`).
+   1. Leave the **Collector Settings** at their default values to configure collectors as remotely managed.
+   1. Under **Generate and run the command to install the collector**, copy and run the installation command in your system terminal where the collector needs to be installed.
+1. After installation is complete, click **Next** to proceed.
+1. Select a source template (for example, Apache source template) to start collecting logs from all linked collectors, then proceed with the data configuration.<br/><img src="/img/send-data/source-template.png" alt="source template page" style={{border:'1px solid gray'}} width="90%" />
 
-1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Collection > OpenTelemetry Collection**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the Sumo Logic top menu select **Configuration**, and then under **Data Collection** select **OpenTelemetry Collection**. You can also click the **Go To...** menu at the top of the screen and select **OpenTelemetry Collection**. 
-1. On the **OpenTelemetry Collection** page, click **Add Collector**.
-1. Select the platform of the remote host in the **Set up Collector**  section.<br/><img src={useBaseUrl('img/send-data/linux-install.png')} alt="Linux-install" style={{border: '1px solid gray'}} width="800"/>
-1. Enter your **Installation Token**.
-1. Under **Tag data on Collector level**, add a new key-value pair by clicking **+New tags**, for example, `application = Apache` to identify these collectors as having Apache running on them.
-1. For **Collector Settings**, leave it as default.
-1. Under **Generate and run the command to install the collector**, copy the command and execute it in your system terminal, where the collector needs to be installed.<br/><img src={useBaseUrl('img/send-data/linux-terminal-installation.png')} alt="Linux-terminal-installation" width="800"/>
-1. Wait for the installation process to complete, then click **Next** to proceed.
-1. On the next screen, you will see a list of available Source Templates.
-
-:::note
-If you close this Source template creation screen, you can navigate back. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Collection > Source Template**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the Sumo Logic top menu select **Configuration**, and then under **Data Collection** select **Source Template**. You can also click the **Go To...** menu at the top of the screen and select **Source Template**. 
-:::
+To revisit this screen later: From the [**Classic UI**](/docs/get-started/sumo-logic-ui-classic), select **Manage Data > Collection > Source Template**. From the [**New UI**](/docs/get-started/sumo-logic-ui), select **Configuration** > **Source Template**.

docs/reuse/apps/opentelemetry/data-configuration.md

@@ -1,9 +1,48 @@
-import useBaseUrl from '@docusaurus/useBaseUrl';
-
-In this step, we'll create a data collection configuration and link them to all the collectors that have particular tags.
-		
-1. Complete the Source Template form by providing the necessary details, then click **Next**.
-1. On the **Link Collectors** step, you will have the option to link the collectors using the Collector name or by adding tags to find the group of collectors. For our scenario, we will add the tag `application = Apache`.<br/><img src={useBaseUrl('img/send-data/local-file-apache.png')} alt="local-file-apache" style={{border: '1px solid gray'}} width="300"/>
-1. Click **Preview Collector(s)** to see the list of collectors that will be linked to the newly created source template.<br/><img src={useBaseUrl('img/send-data/link-collectors.png')} alt="link-collectors" style={{border: '1px solid grey'}} width="800"/>
-1. Click **Next** to complete the Source Template creation. In the background, the system will apply the configuration to all the linked collectors and will start collecting the respective telemetry data from the remote host.
-1. Click the **Log Search** or **Metric Search** icon to search for data collected for this Source Template.
+:::info
+A new source template will always be created with the latest version of the source template.
+:::
+
+Follow the below steps to create a data collection configuration to gather the required logs and link them to all the collectors with the help of collector tags.
+
+1. Complete the source template form with the name and file path for your logs (for example, error logs or access logs), then click **Next**.
+1. Under **Link Collectors**, you will have the option to link the collectors using the collector name or by adding tags to find the group of collectors (for example, `application = Apache`).<br/><img src="/img/send-data/local-file-apache.png" alt="Screenshot of the file path configuration for Apache logs" style={{border:'1px solid gray'}} width="80%" />
+1. Preview and confirm the collectors that will be linked (fetched automatically) to the newly created source template.<br/><img src="/img/send-data/preview-collectors1.png" alt="Screenshot showing the linked collectors preview" style={{border:'1px solid gray'}} width="90%" /><br/><img src="/img/send-data/preview-collectors2.png" alt="Screenshot showing the linked collectors preview" style={{border:'1px solid gray'}} width="90%" />
+1. Click **Next** to complete the source template creation. In the background, the system will apply the configuration to all the linked collectors and will start collecting the respective telemetry data from the remote host (in the example, it would start collecting Apache error logs).
+1. Click the **Log Search** or **Metrics Search** icons to search for and analyze your data collected for this source template.
+
+<!-- Remove temporarily; not yet released
+
+### Collector tags
+
+#### Add a collector tag
+
+You can add collector tags during OTEL collector setup - as described in the previous section - or after creation:
+
+1. Navigate to the **OpenTelemetry Collection** page.
+1. Click on the desired collector where you need to add collector tags.
+1. In the right pane, scroll to the **Collector Tags** section and click **Edit**.
+1. In the edit window, click **+ Add tags**.
+1. Add the required tags and click **Proceed**.
+1. A new **Update Collector Tag(s)** window appears. Click the **click here** link to understand the impact of this update.
+1. You will be redirected to the **Mapped Source Template** section, which displays the mapped source templates for the collector tags added. This window also displays the **Compatible** and **Incompatible Version** details for the mapped source template for the collector.
+1. If there are any incompatible source templates, [upgrade the source template](/docs/send-data/opentelemetry-collector/remote-management/source-templates/manage-source-templates/#upgrade-a-source-template) to ensure compatibility.
+1. Once the source template is upgraded and is compatible, enter **PROCEED** and click **Confirm**.
+
+#### Edit or delete a collector tag
+
+:::note
+- For default collector tags, you can only edit the **Values**.
+- System collector tags like `sumo.disco.enabled` cannot be edited.
+:::
+
+To edit or delete a collector tag:
+
+1. Go to the **OpenTelemetry Collection** page.
+1. Click on the desired collector where you need to add the collector tags.
+1. In the right pane, scroll to the **Collector Tags** section and click **Edit**.
+1. Edit or delete the required tags and click **Proceed**.
+1. A new **Update Collector Tag(s)** window appears. Click the **click here** button to see the impact of this update.
+1. You will be redirected to a **Mapped Source Template** section, which displays the mapped source templates for the edited or deleted collector tags, along with **Compatible** and **Incompatible Version** details.
+1. If find you find an incompatible source template, [upgrade the source template](/docs/send-data/opentelemetry-collector/remote-management/source-templates/manage-source-templates/#upgrade-a-source-template).
+1. Once the source template is upgraded and is compatible, enter **PROCEED** and click **Confirm**.
+-->