Finish send-data

Author: jpipkin1

docs/send-data/installed-collectors/sources/define-boundary-regex-multiline-messages.md

@@ -4,15 +4,15 @@ title: Define Boundary Regex for Multiline Messages
 description: By default, Sumo Logic Sources have multiline processing enabled, which is useful when logs contain messages that span multiple lines separated by line breaks, such as a stack trace.
 ---
 
-
+import useBaseUrl from '@docusaurus/useBaseUrl';
 
 For details on how the Collector processes multiline logs see [Collecting MultilineLogs](/docs/send-data/reference-information/collect-multiline-logs.md)
 
 By default, Sumo Logic Sources have multiline processing enabled, which is useful when logs contain messages that span multiple lines separated by line breaks, such as a stack trace. This way, the Source can detect when a log message spans multiple lines and then indexes this message as a single message.
 
 If you want your Source to treat each log line as a separate message, you can deselect this option, **Detect messages spanning multiple lines**. 
 
-![img](/img/send-data/multiline.png)
+<img src={useBaseUrl('img/send-data/multiline.png')} alt="Checkbox for Detect messages spanning multiple lines" style={{border: '1px solid gray'}} width="600" />
 
 Multi-line processing gives you two primary options:
 

docs/send-data/installed-collectors/sources/docker-sources.md

@@ -33,10 +33,7 @@ There are alternative methods for collecting Docker logs and metrics. See [Dock
 
 1. [**New UI**](/docs/get-started/sumo-logic-ui). In the Sumo Logic main menu select **Data Management**, and then under **Data Collection** select **Collection**. You can also click the **Go To...** menu at the top of the screen and select **Collection**. <br/>[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. 
 1. Navigate to the collector you installed on the Docker host, and select **Add > Add Source**.
-1. Select **Docker Logs**. The Docker Logs page appears.
-
-    ![docker logs source.png](/img/send-data/docker-logs-source.png)
-
+1. Select **Docker Logs**. The Docker Logs page appears.<br/><img src={useBaseUrl('img/send-data/docker-logs-source.png')} alt="Docker logs source" style={{border: '1px solid gray'}} width="600" />
 1. Configure the source fields:
 
    * **Name**. (Required).
@@ -91,7 +88,7 @@ There are alternative methods for collecting Docker logs and metrics. See [Dock
    :::note
    To collect metrics for the Docker ULM App, select **Metrics** as the Content Type.
    :::
-   ![docker-stats.png](/img/send-data/docker-stats.png)
+   <img src={useBaseUrl('img/send-data/docker-stats.png')} alt="Docker stats" style={{border: '1px solid gray'}} width="600" />
 1. Configure the source fields:
 
    * **Name.** (Required)

docs/send-data/installed-collectors/sources/host-metrics-source.md

@@ -4,7 +4,7 @@ title: Host Metrics Source
 description: An installed Sumo Logic Collector can collect host metrics from a local host.
 ---
 
-
+import useBaseUrl from '@docusaurus/useBaseUrl';
 
 An installed Sumo Logic Collector can collect host metrics pertaining to the local host. The metrics are ingested and become available for metrics visualization. The host metrics are gathered by the open-source [SIGAR library](https://github.com/hyperic/sigar). 
 
@@ -36,13 +36,8 @@ A host metric source running on an Installed Collector on an Amazon EC2 instance
 ## Manually Configure a Host Metrics Source
 
 1. [**New UI**](/docs/get-started/sumo-logic-ui). In the Sumo Logic main menu select **Data Management**, and then under **Data Collection** select **Collection**. You can also click the **Go To...** menu at the top of the screen and select **Collection**.<br/>[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Collection > Collection**.  
-1. Find the name of the installed collector to which you'd like to add a source. Click **Add** and then choose **Add Source**.
-
-    ![add-source2.png](/img/send-data/add-source2.png)
-
-1. Select **Host Metrics** as the source type.
-
-    ![InstalledCollector.png](/img/send-data/host-metrics-icon.png)
+1. Find the name of the installed collector to which you'd like to add a source. Click **Add** and then choose **Add Source**.<br/><img src={useBaseUrl('img/send-data/add-source2.png')} alt="Add Source button" style={{border: '1px solid gray'}} width="800" />
+1. Select **Host Metrics** as the source type.<br/><img src={useBaseUrl('img/send-data/host-metrics-icon.png')} alt="Host Metrics tile" style={{border: '1px solid gray'}} width="600" />
 1. Set the following:
 
    * **Name**. Enter the name you'd like to display for the new Source. Description is optional. Source name metadata is stored in a searchable field called `_sourceCategory`.
@@ -51,11 +46,8 @@ A host metric source running on an Installed Collector on an Amazon EC2 instance
    * **Fields**. Click the **+Add Field** link to add custom metric metadata. Define the fields you want to associate, providing a name (key) and value for each.
    * **Scan Interval**. Select the frequency for the Source to scan for host metrics data. Selecting a short interval will increase the message volume and could cause your deployment to incur additional charges. The default is 1 minute.
    * **Metrics**. Select check boxes for the metrics to collect. By default, all CPU and memory metrics are collected.
-
-     * Select the top level check box to select all metrics in that category. A blue checkmark icon ![check](/img/send-data/icon_blue_checkmark.png) indicates that the category is selected.
-     * To select individual metrics, click the right-facing arrow to expand the category and select the individual metrics. The icon changes to ![minus](/img/send-data/icon_blue_minus.png) , as shown in the screenshot.        
-
-    ![host-metrics-source.png](/img/send-data/host-metrics-source.png)
+     * Select the top level check box to select all metrics in that category. A blue checkmark icon <img src={useBaseUrl('img/send-data/icon_blue_checkmark.png')} alt="Blue checkmark" width="20" /> indicates that the category is selected.
+     * To select individual metrics, click the right-facing arrow to expand the category and select the individual metrics. The icon changes to <img src={useBaseUrl('img/send-data/icon_blue_minus.png')} alt="Minus mark" width="20" />, as shown in the screenshot.<br/><img src={useBaseUrl('img/send-data/host-metrics-source.png')} alt="Select individual metrics" style={{border: '1px solid gray'}} width="600" />
 
 1. When you are finished configuring the Source, click **Save**.
 

docs/send-data/installed-collectors/sources/local-file-source.md

@@ -42,15 +42,9 @@ When the Sumo collector accesses a log file to read its content, the collector o
 ## Configure a Local File Source
 
 1. [**New UI**](/docs/get-started/sumo-logic-ui). In the Sumo Logic main menu select **Data Management**, and then under **Data Collection** select **Collection**. You can also click the **Go To...** menu at the top of the screen and select **Collection**. <br/>[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. 
-1. Find the name of the Installed Collector to which you'd like to add a Source. Click **Add...** then choose **Add Source** from the pop-up menu.
-
-    ![img](/img/send-data/add-source.png)    
-1. Select **Local File** for the Source type.
-
-    ![local file source icon.png](/img/send-data/local-file-source-icon.png) 
-1. Set the following choices:
-
-    ![local file source.png](/img/send-data/local-file-source.png)
+1. Find the name of the Installed Collector to which you'd like to add a Source. Click **Add...** then choose **Add Source** from the pop-up menu.<br/><img src={useBaseUrl('img/send-data/add-source.png')} alt="Add source button" style={{border: '1px solid gray'}} width="800" />
+1. Select **Local File** for the Source type.<br/><img src={useBaseUrl('img/send-data/local-file-source-icon.png')} alt="Local file source icon" style={{border: '1px solid gray'}} width="100" />
+1. Set the following choices:<br/><img src={useBaseUrl('img/send-data/local-file-source.png')} alt="Local file source" style={{border: '1px solid gray'}} width="600" />
 
    * **Name**. Type the name you'd like to display for the new Source. Description is optional.
 

docs/send-data/installed-collectors/sources/local-windows-event-log-source.md

@@ -19,18 +19,9 @@ To configure a Local Windows Event Log Source:
 
 1. [**New UI**](/docs/get-started/sumo-logic-ui). In the Sumo Logic main menu select **Data Management**, and then under **Data Collection** select **Collection**. You can also click the **Go To...** menu at the top of the screen and select **Collection**. <br/>[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. 
 
-1. Find the name of the installed collector to which you'd like to add a Source. Click **Add** and then choose **Add Source** from the pop-up menu.
-
-    ![add source from collection page.png](/img/send-data/add-source-from-collection-page.png)
-
-1. Click **Windows Event Log**.
-
-    ![windows event log source icon.png](/img/send-data/windows-event-log-source-icon.png)
-
-1. Choose **Local** for **Type of Windows Source**.
-
-    ![type of windows event log source.png](/img/send-data/type-windows-event-log-source.png)
-
+1. Find the name of the installed collector to which you'd like to add a Source. Click **Add** and then choose **Add Source** from the pop-up menu.<br/><img src={useBaseUrl('img/send-data/add-source-from-collection-page.png')} alt="Add source from collection page" style={{border: '1px solid gray'}} width="800" />
+1. Click **Windows Event Log**.<br/><img src={useBaseUrl('img/send-data/windows-event-log-source-icon.png')} alt="Windows event log source icon" style={{border: '1px solid gray'}} width="100" />
+1. Choose **Local** for **Type of Windows Source**.<br/><img src={useBaseUrl('img/send-data/type-windows-event-log-source.png')} alt="Type of windows event log source" style={{border: '1px solid gray'}} width="300" />
 1. Set the following:
    * **Name.** Type the name you'd like to display for the new Source. 
      :::note
@@ -42,39 +33,25 @@ To configure a Local Windows Event Log Source:
 
       * <img src={useBaseUrl('img/reuse/green-check-circle.png')} alt="green check circle.png" width="20"/> A green circle with a check mark is shown when the field exists and is enabled in the Fields table schema.
       * <img src={useBaseUrl('img/reuse/orange-exclamation-point.png')} alt="orange exclamation point.png" width="20"/> An orange triangle with an exclamation point is shown when the field doesn't exist in the Fields table schema. In this case, you'll see an option to automatically add or enable the nonexistent fields to the Fields table schema. If a field is sent to Sumo Logic but isn’t present or enabled in the schema, it’s ignored and marked as **Dropped**.
-   * **Event Format**. Select how you want your event logs formatted:
-        ![JSON format name update.png](/img/send-data/JSON-format-name-update.png)
+   * **Event Format**. Select how you want your event logs formatted:<br/><img src={useBaseUrl('img/send-data/JSON-format-name-update.png')} alt="JSON format name update" style={{border: '1px solid gray'}} width="500" />
      * **Collect using legacy format**. Events retain their default text format from Windows.
      * **Collect using JSON format**. Events are formatted into JSON that is designed to work with Sumo Logic features, making it easier for you to reference your data.
 
      :::note
      To **Collect using JSON format** the Collector must have version 19.319.2 or later installed. The Windows JSON App requires **JSON format**.
      :::
 
-   * **Windows Event Types.** Select the event types you want to collect:
-
-        ![windows events types 2021 June.png](/img/send-data/windows-events-types.png)
-
+   * **Windows Event Types.** Select the event types you want to collect:<br/><img src={useBaseUrl('img/send-data/windows-events-types.png')} alt="Windows events types 2021 June" style={{border: '1px solid gray'}} width="500" />
      * **Standard Event Channels**. Select the main check box for all types, or individual check boxes for specific types (Security, Application, and/or System).
      * **Forwarded Events**. See how to [Collect Forwarded Events from a Windows Event Collector](collect-forwarded-events-windows-event-collector.md). Note that this box is not selectable when **Standard Event Channels** is checked.
      * **Custom Event Channels** to specify, in a comma-separated list, the channels you'd like to collect from. If you need help finding channels on the machine where the Source is installed, see [Windows Event Source Custom Channels](local-windows-event-log-source.md).  To collect from custom event channels in a Local Event Source, the Collector must have version 19.118 or later installed.
-
    * Depending on the **Event Format** selected, you'll have different options.
-     * **Event Collection Level**. When JSON format is selected you have the option to select:
-
-        ![event levels.png](/img/send-data/event-levels.png)
-
+     * **Event Collection Level**. When JSON format is selected you have the option to select:<br/><img src={useBaseUrl('img/send-data/event-levels.png')} alt="Event levels" style={{border: '1px solid gray'}} width="500" />
      * **Complete Message** will ingest the entire event content along with metadata.
      * **Concise Message** will ingest the first line of event messages along with all of the metadata.
      * **Metadata Only** will ingest metadata fields from each event, including event ID and timestamp. The Windows JSON App requires **Complete Message**.
-     * **Event IDs.** (Available in Collector version 19.351-4 and later.) You can set allow and deny Windows Event ID filters to only collect important events. Select the checkbox next to the type of filter you want to set, we recommend only using one at a time. Your list needs to be a comma-separated list of event IDs.
-
-        ![windows event ID filter example.png](/img/send-data/windows-event-ID-filter-example.png)
-
-     * **Metadata.** When the legacy format is selected choose whether you would like the collector to minimize the amount of data collected by omitting the full message text of each event. Core metadata fields such as event ID, timestamp, user name, as well as the unformatted event data will still be present. This can reduce data usage and increase event throughput, but will prevent many dashboards and apps from correctly extracting data. To omit full event text and only collect event metadata, the collector must have version 19.155 or later installed.
-
-    ![legacy metadata option.png](/img/send-data/legacy-metadata-option.png)
-
+     * **Event IDs.** (Available in Collector version 19.351-4 and later.) You can set allow and deny Windows Event ID filters to only collect important events. Select the checkbox next to the type of filter you want to set, we recommend only using one at a time. Your list needs to be a comma-separated list of event IDs.<br/><img src={useBaseUrl('img/send-data/windows-event-ID-filter-example.png')} alt="Windows event ID filter example" style={{border: '1px solid gray'}} width="500" />
+     * **Metadata.** When the legacy format is selected choose whether you would like the collector to minimize the amount of data collected by omitting the full message text of each event. Core metadata fields such as event ID, timestamp, user name, as well as the unformatted event data will still be present. This can reduce data usage and increase event throughput, but will prevent many dashboards and apps from correctly extracting data. To omit full event text and only collect event metadata, the collector must have version 19.155 or later installed.<br/><img src={useBaseUrl('img/send-data/legacy-metadata-option.png')} alt="Legacy metadata option" style={{border: '1px solid gray'}} width="500" />
    * **Collection should begin**. Choose or enter how far back you'd like to begin collecting historical logs. You can either:
 
      * Choose a predefined value from dropdown list, ranging from “Now” to “24 hours ago” to “All Time”.
@@ -138,7 +115,7 @@ You can use multiple variables, for example:
 {{sys.PATH}}-{{sys.YourEnvVar}}
 ```
 
-![img](/img/send-data/environment-variable-usage.png)
+<img src={useBaseUrl('img/send-data/environment-variable-usage.png')} alt="Multiple variables" style={{border: '1px solid gray'}} width="500" />
 
 :::tip
 The example above uses a hyphen - character to separate variable components. Separator characters are not required. Curly brackets and spaces are not allowed. Underscores and hyphens are recommended.

docs/send-data/installed-collectors/sources/local-windows-performance-monitor-log-source.md

@@ -31,10 +31,7 @@ To configure a Local Windows Performance Monitor Log Source:
       * <img src={useBaseUrl('img/reuse/green-check-circle.png')} alt="green check circle.png" width="20"/> A green circle with a check mark is shown when the field exists and is enabled in the Fields table schema.
       * <img src={useBaseUrl('img/reuse/orange-exclamation-point.png')} alt="orange exclamation point.png" width="20"/> An orange triangle with an exclamation point is shown when the field doesn't exist in the Fields table schema. In this case, you'll see an option to automatically add or enable the nonexistent fields to the Fields table schema. If a field is sent to Sumo Logic but isn’t present or enabled in the schema, it’s ignored and marked as **Dropped**.
 1. **Processing Rules.** (Optional.) To add rules or filters click **Add Rule**. Enter a name, a filter, and select the type. Then click **Apply**.
-1. **Perfmon Queries.** Select from the provided default Perfmon Queries, or create your own custom query.
-
-    ![windows performance source.png](/img/send-data/windows-performance-source.png)
-
+1. **Perfmon Queries.** Select from the provided default Perfmon Queries, or create your own custom query.<br/><img src={useBaseUrl('img/send-data/windows-performance-source.png')} alt="Windows performance source" style={{border: '1px solid gray'}} width="600" />
       * Click the query's check box to select it.
       * To add a custom query, click **Add Query**, enter a name and the query. Then click **Add**.
 1. When you are finished configuring the Source, click **Save**.
@@ -68,7 +65,7 @@ You can use multiple variables, for example:
 {{sys.PATH}}-{{sys.YourEnvVar}}
 ```
 
-![img](/img/send-data/environment-variable-usage.png)
+<img src={useBaseUrl('img/send-data/environment-variable-usage.png')} alt="Multiple variables" style={{border: '1px solid gray'}} width="500" />
 
 :::tip
 The example above uses a hyphen - character to separate variable components. Separator characters are not required. Curly brackets and spaces are not allowed. Underscores and hyphens are recommended.