Merge branch 'main' into update-the-FAQ

JV0812 · web-flow · commit 2e09d23c4e09 · 2025-09-03T15:53:47.000+05:30
diff --git a/blog-collector/2025-07-04-installed.md b/blog-collector/2025-07-04-installed.md
diff --git a/blog-collector/2025-09-02-download-ic.md b/blog-collector/2025-09-02-download-ic.md
@@ -0,0 +1,14 @@
+---
+title: Download a collector using the CDN URL (Installed Collector)
+image: https://help.sumologic.com/img/reuse/rss-image.jpg
+keywords:
+  - installed-collector
+  - download-collector
+hide_table_of_contents: true    
+---
+
+We’re pleased to announce a new method for downloading the latest version of our installed collectors. While the static URL method is still available, you now have the option to use a CDN URL via UI for better performance.
+
+:::info
+This change does not affect the UI itself. The download process looks the same, but the underlying URL now uses a CDN to improve reliability and speed. 
+:::
diff --git a/blog-collector/2025-09-02-installed.md b/blog-collector/2025-09-02-installed.md
@@ -0,0 +1,9 @@
+---
+title: Version 19.525-59 (Installed Collector)
+hide_table_of_contents: true
+image: https://help.sumologic.com/img/reuse/rss-image.jpg
+---
+
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+In this release, we've upgraded the collector JRE to **Amazon Corretto Version `8.462.08.1`** to enhance security and optimize performance for faster execution.
diff --git a/docs/dashboards/panels/table-charts.md b/docs/dashboards/panels/table-charts.md
@@ -30,7 +30,11 @@ To add a panel with a table chart:
 
     To create a metrics query utilize the [Metrics Search](/docs/metrics/metrics-queries).
 
-1. Once the query runs you will need to flip the chart type to **Table**.<br/><img src={useBaseUrl('/img/dashboards/panels/table-charts/new-table-chart.png')} alt="new table chart" style={{border: '1px solid gray'}} width="700" />
+1. Once the query runs, you will need to flip the chart type to **Table**.
+    1. (Optional) **Missing Data Display**. Enter the text that needs to be displayed when data is missing.
+    1. (Optional) **Font Size**. Font size of the text displayed. By default, `12` is set as font size. You can change this based on your requirement.
+    1. (Optional) **Decimals**. Sets the precision of units displayed. Select the number of decimals to show with a unit, up to 10.
+    1. (Optional) **Rows Per Page**. Set the numbers of rows to display in the table.<br/><img src={useBaseUrl('/img/dashboards/panels/table-charts/new-table-chart.png')} alt="new table chart" style={{border: '1px solid gray'}} width="800" />
 1. [Modify the chart](./modify-chart.md) as desired.
 1. Click the **Add to Dashboard** button on the top right of the window to add the panel to your dashboard.<br/><img src={useBaseUrl('/img/dashboards/create-dashboard/Add-to-Dashboard-button.png')} alt="Add to Dashboard button" style={{border: '1px solid gray'}} width="300" />
 
diff --git a/docs/integrations/google/cloud-security-command-center.md b/docs/integrations/google/cloud-security-command-center.md
@@ -468,8 +468,8 @@ This section describes the Sumo Logic pipeline for collecting the data from Goog
 Follow the steps below to integrate the Google Cloud Security Command Center (SCC) app:
 
 1. Enable the [Security Command Center (SCC)](https://cloud.google.com/security-command-center/docs/activate-scc-overview) at the GCP console.
-1. In Sumo Logic, [configure the Google Cloud Platform source](https://help.sumologic.com/docs/send-data/hosted-collectors/google-source/google-cloud-platform-source/#configure-agoogle-cloud-platform-source).
-1. In the GCP console, configure a Pub/Sub Topic for [GCP](https://help.sumologic.com/docs/send-data/hosted-collectors/google-source/google-cloud-platform-source/#configure-a-pubsub-topicfor-gcp). This topic will be used to send SCC findings from GCP to Sumo Logic.
+1. In Sumo Logic, [configure the Google Cloud Platform source](/docs/send-data/hosted-collectors/google-source/google-cloud-platform-source/#configure-agoogle-cloud-platform-source).
+1. In the GCP console, configure a Pub/Sub Topic for [GCP](/docs/send-data/hosted-collectors/google-source/google-cloud-platform-source/#configure-a-pubsub-topicfor-gcp). This topic will be used to send SCC findings from GCP to Sumo Logic.
 1. In the SCC blade of the GCP console, click **Continuous Exports**. <br/><img src={useBaseUrl('https://sumologic-app-data-v2.s3.us-east-1.amazonaws.com/dashboards/Google+Cloud+-+Security+Command+Center/step4.png')} alt="Google Cloud Storage dashboards" width="500" />
 1. In the GCP console, export the findings from SCC to the [Pub/Sub Topic](https://cloud.google.com/security-command-center/docs/how-to-export-data?_gl=1*1dt4zsw*_ga*ODU1MTc4OTQ1LjE3Mzg3ODM5NzI.*_ga_WH2QY8WWF5*czE3NDY2Mzc3MzQkbzMkZzEkdDE3NDY2MzgxNDUkajYwJGwwJGgw#configure-pubsub-exports) created above.
 
diff --git a/docs/integrations/sumo-apps/opentelemetry-collector-insights.md b/docs/integrations/sumo-apps/opentelemetry-collector-insights.md
@@ -29,11 +29,8 @@ Following are the [fields](/docs/manage/fields/) which will be created as part o
 
 ### For OTLP endpoint configuration
 
-Before configuring the OTEL Collector integration, ensure you have the following prerequisites in place:
 
-1. **Sumo Logic OTLP Source**: You need to create an OTLP source in your Sumo Logic hosted collector. The OTLP source will provide the endpoint URL that the OTEL Collector will use to send telemetry data.
-
-  **Documentation**: [Creating a Sumo Logic OTLP Source](https://help.sumologic.com/docs/send-data/hosted-collectors/http-source/otlp/)
+Before configuring the OTEL Collector integration, you need to create an OTLP source in your Sumo Logic hosted collector. The OTLP source will provide the endpoint URL that the OTEL Collector will use to send telemetry data. Learn more at [Creating a Sumo Logic OTLP Source](/docs/send-data/hosted-collectors/http-source/otlp/).
 
 ### For metrics collection
 
@@ -77,7 +74,7 @@ In this step, you will configure the OpenTelemetry Collector's built-in telemetr
 
 Below are the inputs required:
 
-- **OTLP Endpoint**: Your Sumo Logic OTLP endpoint URL.
+- **OTLP Endpoint**. Your Sumo Logic OTLP endpoint URL.
 
 
 ```yaml
@@ -107,13 +104,13 @@ service:
       deployment.environment: ${DEPLOYMENT_ENVIRONMENT}
 ```
 
-You can add any custom fields which you want to tag along with the data ingested in Sumo.
+You can add any custom fields which you want to tag along with the data ingested in Sumo Logic.
 
 import EnvVar from '../../reuse/apps/opentelemetry/env-var-required.md';
 
 <EnvVar/>
 
-<img src='https://sumologic-app-data-v2.s3.us-east-1.amazonaws.com/dashboards/OpenTelemetry-Collector-Insights/opentelemetry-collector-insights-configure-form.png' style={{border:'1px solid gray'}} alt="YAML" />
+<img src='https://sumologic-app-data-v2.s3.us-east-1.amazonaws.com/dashboards/OpenTelemetry-Collector-Insights/opentelemetry-collector-insights-configure-form.png' style={{border:'1px solid gray'}} alt="YAML" width="700"/>
 
 ### Step 3: Send logs and metrics to Sumo Logic
 
@@ -137,31 +134,31 @@ import LogsIntro from '../../reuse/apps/opentelemetry/send-logs-intro.md';
 
 1. Add the telemetry configuration to your existing collector configuration file in `/etc/otelcol-sumo/conf.d/` or directly in the main configuration file.
 2. Place Env file in the following directory:
-  ```sh
-  /etc/otelcol-sumo/env/
-  ```
+   ```sh
+   /etc/otelcol-sumo/env/
+   ```
 3. Restart the collector using:
-  ```sh
-  sudo systemctl restart otelcol-sumo
-  ```
+   ```sh
+   sudo systemctl restart otelcol-sumo
+   ```
 
 </TabItem>
 <TabItem value="Windows">
 
 1. Add the telemetry configuration to your existing collector configuration file in `C:\ProgramData\Sumo Logic\OpenTelemetry Collector\config\conf.d` or the main configuration file.
 2. Restart the collector using:
-  ```sh
-  Restart-Service -Name OtelcolSumo
-  ```
+   ```sh
+   Restart-Service -Name OtelcolSumo
+   ```
 
 </TabItem>
 <TabItem value="macOS">
 
 1. Add the telemetry configuration to your existing collector configuration file in `/etc/otelcol-sumo/conf.d/` or the main configuration file.
 2. Restart the otelcol-sumo process using:
-  ```sh
-  otelcol-sumo --config /etc/otelcol-sumo/sumologic.yaml --config "glob:/etc/otelcol-sumo/conf.d/*.yaml"
-  ```
+   ```sh
+   otelcol-sumo --config /etc/otelcol-sumo/sumologic.yaml --config "glob:/etc/otelcol-sumo/conf.d/*.yaml"
+   ```
 
 </TabItem>
 <TabItem value="Chef">
@@ -419,4 +416,4 @@ import CreateMonitors from '../../reuse/apps/create-monitors.md';
 | `OpenTelemetry Collector Insights - Collector Instance is Down` | This alert fires when a Collector instance stops sending telemetry for more than 10 minutes, indicating it is down or has a connectivity issue. | Missing Data | Data Found |
 | `OpenTelemetry Collector Insights - Exporter Queue Nearing Capacity` | This alert fires when an exporter's sending queue is over 90% full. This is a strong leading indicator of back pressure and imminent data loss. | Count > = 90 | Count < 90 |
 | `OpenTelemetry Collector Insights - High Memory Usage (RSS)` | This alert fires when a Collector's memory usage (RSS) exceeds 2GB. This could be an early indicator of a memory leak or an under-provisioned host. | Count > 2000000000 | Count < = 2000000000 |
-| `OpenTelemetry Collector Insights  - High Metadata Cardinality` | This alert fires when the batch processor is handling more than 1000 unique combinations of metadata. This is a known cause of performance degradation, high CPU, and high memory usage. | Count > 1000 | Count < = 1000 |
+| `OpenTelemetry Collector Insights  - High Metadata Cardinality` | This alert fires when the batch processor is handling more than 1000 unique combinations of metadata. This is a known cause of performance degradation, high CPU, and high memory usage. | Count > 1000 | Count < = 1000 |
diff --git a/docs/search/query-assist.md b/docs/search/query-assist.md
@@ -8,6 +8,10 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
 
 Query Assist enhances the query-building experience in Sumo Logic by providing real-time syntax suggestions, schema prompts, and partial query predictions. These enhancements simplify the process for users at all skill levels, making it easier to write accurate and efficient queries, enabling easier discovery of relevant fields, minimizing errors, and providing intelligent assistance for query creation. The suggestions that appear comply with the user's role-based access restrictions.
 
+:::info
+Logs Query Assist is also supported in [Dashboards](/docs/dashboards) and [Scheduled Searches](/docs/alerts/scheduled-searches).
+:::
+
 <img src={useBaseUrl('img/search/get-started-search/query-assist-preview1.gif')} alt="query assist demo gif" style={{border: '1px solid gray'}} width="700"/>
 
 ## Key enhancements
diff --git a/docs/search/search-query-language/search-operators/geoip.md b/docs/search/search-query-language/search-operators/geoip.md
@@ -36,7 +36,7 @@ all the optional fields or choose a subset:
 * state_cf
 * city_cf
 
-Details of these data fields can be found in [Neustar's documentation](/files/IP-Geo-Point-Data-Glossary.pdf) under the GeoPoint Data Glossary topic.
+Details of these data fields can be found in <a href="/files/IP-Geo-Point-Data-Glossary.pdf" target="_blank">Neustar's documentation</a> under the GeoPoint Data Glossary topic.
 
 ## Syntax to Map
 
diff --git a/docs/send-data/reference-information/collect-multiline-logs.md b/docs/send-data/reference-information/collect-multiline-logs.md
@@ -7,7 +7,7 @@ description: Sumo Logic Sources can be configured to detect log boundaries autom
 Sumo Logic Sources, by default, have multiline processing enabled. Multiline processing is used to ensure that a log message made up of multiple lines, with each line separated by a line break or carriage return, is correctly grouped as a single log message when ingested into Sumo Logic.
 
 :::warning
-The line breaks or carriage returns are control characters used to create new lines, usually represented by the escape sequences `\r` and `\r\n`, but are often invisible in text editors. Sumo Logic will not be able to split your log messages that do not contain these characters.
+The line breaks or carriage returns are control characters used to create new lines, usually represented by the escape sequences `\n` and `\r\n`, but are often invisible in text editors. Sumo Logic will not be able to split your log messages that do not contain these characters.
 :::
 
 ## Multiline Processing Caveats
diff --git a/static/img/dashboards/panels/table-charts/new-table-chart.png b/static/img/dashboards/panels/table-charts/new-table-chart.png
