last edits

Author: kimsauce

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

@@ -1,23 +1,14 @@
-To illustrate the setup and configuration process, we'll use an example scenario where you'd need to monitor Apache error logs from 50 Linux servers.
+In this step, we'll install the collector and add a uniquely identifiable tag to these collectors.
 
-First, you'll need to install the OpenTelemetry collectors on each of the 50 Linux servers and tag them to indicate that they are running Apache.
-
-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. [**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:
-   <!-- ![Linux install](img/send-data/linux-install.png)-->
-   1. Choose your platform (in this example, **Linux**).
+   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 (we'll use `application = Apache`).
+   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.
-      <!-- ![Linux terminal installation](img/send-data/linux-terminal-installation.png)-->
 1. After installation is complete, click **Next** to proceed.
-1. For this example, we'll select **Apache Source Template** to apply the source template to start collecting logs from all linked collectors, then proceed with the data configuration.
-   <!--![Source template page](img/send-data/source-template.png)-->
+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%" />
 
-To revisit this screen later:
-* [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Collection > Source Template**.
-* [**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

@@ -4,15 +4,11 @@ A new source template will always be created with the latest version of the sour
 
 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 error 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. In this Apache example, we will add the tag `application = Apache`.
-  <!-- ![Screenshot of the file path configuration for Apache logs](img/send-data/local-file-apache.png)-->
-1. Preview and confirm the collectors that will be linked (fetched automatically) to the newly created source template.
-  <!-- ![Screenshot showing the linked collectors preview](img/send-data/link-collectors.png)-->
+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 **Metric Search** icons to search for data collected for this source template.
-
-Use [Log Search](/docs/search) and [Dashboards](/docs/dashboards) to monitor and analyze your collected data. In the example above, you'd look at your collected error logs and gain insights from your Apache servers.
+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
 

docs/reuse/apps/opentelemetry/logs-advance-option-otel.md

@@ -1,6 +1,5 @@
-**Advance options** for log collection can be used as follows : 
-
-    **Timestamp Format**. By default, Sumo Logic will automatically detect the timestamp format of your logs. However, you can manually specify a timestamp format for a source by specifying the following:
-        - **Timestamp locator**. This will be a [Go regular expression](https://github.com/google/re2/wiki/Syntax) which should have timestamp matched using a named capture group. Name of this captured group should be “timestamp_field”.
-        - **Layout**. The exact layout of the timestamp to be parsed for example - %Y-%m-%dT%H:%M:%S.%LZ. To learn more about the rules, [refer here](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/internal/coreinternal/timeutils/internal/ctimefmt/ctimefmt.go#L68).
-        - **Location (Time zone)** : The geographic location (timezone) to use when parsing a timestamp that does not include a timezone. The available locations depend on the local IANA Time Zone database. [This page](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) contains many examples, such as America/New_York.
+**Advance options** for log collection can be used as follows:
+   * **Timestamp Format**. By default, Sumo Logic will automatically detect the timestamp format of your logs. However, you can manually specify a timestamp format for a source by configuring the following:
+      - **Timestamp locator**. Use a [Go regular expression](https://github.com/google/re2/wiki/Syntax) to match the timestamp in your logs. Ensure the regular expression includes a named capture group called `timestamp_field`.
+      - **Layout**. Specify the exact layout of the timestamp to be parsed. For example, `- %Y-%m-%dT%H:%M:%S.%LZ`. To learn more about the formatting rules, refer to [this guide](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/internal/coreinternal/timeutils/internal/ctimefmt/ctimefmt.go#L68).
+      - **Location (Time zone)**. Define the geographic location (timezone) to use when parsing a timestamp that does not include a timezone. The available locations depend on the local IANA Time Zone database. For example, `America/New_York`. This [IANA Time Zone page](link-to-timezone-examples) provides many examples.

docs/send-data/opentelemetry-collector/remote-management/source-templates/manage-source-templates.md

@@ -35,25 +35,35 @@ Read up on how to [configure your OpenTelemetry collector for remote management]
 
 1. From the [**Classic UI**](/docs/get-started/sumo-logic-ui-classic), go to **Manage Data > Collection > Source Template**. Or, from the [**New UI**](/docs/get-started/sumo-logic-ui), go to the Sumo Logic top menu and select **Configuration > Collection > Source Template**.
 1. Click **Create Source Template** > **Add Source Template** and fill in the required details, such as name and configuration settings. When you're done, click **Next**.<br/><img src={useBaseUrl('img/send-data/local-file-apache.png')} alt="local-file-apache" style={{border:'1px solid gray'}} width="500"/>
-1. On the **Link Collectors** page, you will have the option to link the collectors using the **Collector Name** or by adding **Collector Tags** to find the group of collectors.
-1. Navigate to **Preview Collector(s)** to view details about the compatibility of the collectors and the collectors that will be linked to the newly created source template. If we have mapped the collectors using both the **Collector Name** and **Collector Tags**, you will get a separate preview sections for the collectors identified by collector name and collector tags.<br/><img src={useBaseUrl('img/send-data/link-collectors.png')} alt="link-collectors" style={{border: '1px solid gray'}} width="800" />
+1. On the **Link Collectors** page, you will have the option to link the collectors using the **Collector Name** or by adding **Collector Tags** to find the group of collectors.<br/><img src={useBaseUrl('img/send-data/link-collectors.png')} alt="link-collectors" style={{border: '1px solid gray'}} width="800" />
+1. Navigate to **Preview Collector(s)** to view details about the compatibility of the collectors and the collectors that will be linked to the newly created source template. If we have mapped the collectors using both the **Collector Name** and **Collector Tags**, you will get separate preview sections for the collectors identified by collector name and collector tags.<br/> ![Screenshot showing the linked collectors preview](/img/send-data/preview-collectors1.png)<br/>![Screenshot showing the linked collectors preview](/img/send-data/preview-collectors2.png)
     :::note
-    Incompatible version conflict will be found if your collectors cannot be linked to the source template due to version incompatibility or unsupported operating system. To move to the next step, make sure you update the collect version of the incompatible collector.<br/><img src={useBaseUrl('img/send-data/incompatible-collectors.png')} alt="incompatible-collectors" style={{border:'1px solid gray'}} width="800"/>
+    Incompatible version conflict will be found if your collectors cannot be linked to the source template due to version incompatibility or unsupported operating system. To move to the next step, make sure you update the collect version of the incompatible collector.<br/><img src={useBaseUrl('img/send-data/incompatible-collectors.png')} alt="incompatible-collectors" style={{border:'1px solid gray'}} width="700"/>
     :::
 1. Click **Next** to complete source template creation. In the background, the system will apply the configuration to all the compatible linked collectors and starts collecting the required files.
 1. Apply the source template to the linked collectors and manage or update it as needed.
 
 Use our [Log Search](/docs/search) and [dashboards](/docs/dashboards) to monitor and analyze your collected logs.
 
+### Example: Apache error logs
 
-### Example scenario: Nginx access logs
+To illustrate the setup and configuration process, we'll use an example scenario where you'd need to monitor Apache error logs from 50 Linux servers.
+
+First, you'll need to install the OpenTelemetry collectors on each of the 50 Linux servers and add a uniquely identifiable tag to indicate that they are running Apache.
+
+1. **Create source template**. Name it `Apache Error Logs` and specify the log file path.
+2. **Link collectors**. Under **Collector Tags**, tag your web servers with `application = Apache` and link these collectors to the source template.
+3. **Deploy**. Apply the source template to start collecting logs from all linked collectors.
+4. **Monitor**. Use Log Search, Metrics, and Dashboards to look at your collected error logs and gain insights from your Apache servers.
+
+### Example: Nginx access logs
 
 To monitor Nginx access logs from a group of web servers:
 
 1. **Create source template**. Name it `Nginx Access Logs` and specify the log file path.
-2. **Link collectors**. Tag your web servers with `application=nginx` and link these collectors to the source template.
+2. **Link collectors**. Under **Collector Tags**, tag your web servers with `application=nginx` and link these collectors to the source template.
 3. **Deploy**. Apply the source template to start collecting logs from all linked collectors.
-4. **Monitor**. Use our [Log Search](/docs/search) and [Dashboards](/docs/dashboards) to monitor and analyze the collected Nginx access logs.
+4. **Monitor**. Use Log Search, Metrics, and Dashboards to monitor and analyze the collected Nginx access logs.
 
 :::tip
 For more details on source templates, see [Installed Collector Sources](/docs/send-data/installed-collectors/sources).