Images in manage

Author: jpipkin1

docs/manage/content-sharing/changing-alerts.md

@@ -21,32 +21,18 @@ If you're using a search template with your saved search, you cannot modify the
 To edit an alert:
 
 1. Go to the Sumo Logic library by clicking the folder icon in the main Sumo Logic menu: <img src={useBaseUrl('img/reuse/library-icon.png')} alt="Library icon" style={{border: '1px solid gray'}} width="30" />
-
 1. Click in the search area to display a list of library object types, and choose **Scheduled Searches**. 
-
-1. Select the edit icon in the library for the scheduled search you'd like to edit. 
-
-    ![EditAlert.png](/img/content-sharing/EditAlert.png)
-
-1. Click **Edit this search's schedule**.
-
-    ![edit-search-schedule](/img/content-sharing/edit-search-schedule.png)
-
-1. Modify the frequency, time range, and alert type as needed.
-
-    ![EditAlert3.png](/img/content-sharing/EditAlert3.png)
-
+1. Select the edit icon in the library for the scheduled search you'd like to edit.<br/><img src={useBaseUrl('img/content-sharing/EditAlert.png')} alt="Select the edit icon in the library" style={{border: '1px solid gray'}} width="800" />
+1. Click **Edit this search's schedule**.<br/><img src={useBaseUrl('img/content-sharing/edit-search-schedule.png')} alt="Edit search schedule" style={{border: '1px solid gray'}} width="600" />
+1. Modify the frequency, time range, and alert type as needed.<br/><img src={useBaseUrl('img/content-sharing/EditAlert3.png')} alt="Modify the alert" style={{border: '1px solid gray'}} width="600" />
 1. Click **Update** to save your changes.
 
 ## Cancel alerts on a shared search
 
 If you have Edit permissions on the shared search, you can stop recipients from receiving alerts by setting the run frequency to **Never**. We recommend doing this when a search is no longer relevant rather than deleting the search so that it can be available to you later if you need it. Deleting the shared search is possible, if you have Manage permissions, but does not allow you the ability to restore a scheduled search later if you need it.
 
 1. Navigate to the scheduled search you want to edit, as described above in [Edit an alert](#edit-an-alert).
-1. Select the edit icon in the library for the scheduled search.
-
-    ![EditAlert.png](/img/content-sharing/EditAlert.png)
-
+1. Select the edit icon in the library for the scheduled search.<br/><img src={useBaseUrl('img/content-sharing/EditAlert.png')} alt="Select the edit icon in the library" style={{border: '1px solid gray'}} width="800" />
 1. In the **Edit Search** dialog, click **Edit this search's schedule**.
 1. From the **Run Frequency** menu, choose **Never** to cancel the scheduled search.
 1. Click **Update** to save your changes.

docs/manage/content-sharing/index.md

@@ -41,10 +41,8 @@ To find content in the library that has been shared with you, click the clock i
 
 To share content from the left navigation bar or the library:
 
-1. Click the details icon ![details](/img/content-sharing/details.png) for the content you want to share.
-1. Select **Share** from the dropdown menu.
-
-    <img src={useBaseUrl('img/content-sharing/share-search.png')} alt="Share search" width="150"/>
+1. Click the details icon <img src={useBaseUrl('img/content-sharing/details.png')} alt="Details icon" style={{border: '1px solid gray'}} width="20" /> for the content you want to share.
+1. Select **Share** from the dropdown menu.<br/><img src={useBaseUrl('img/content-sharing/share-search.png')} alt="Share search" width="150"/>
 
     :::note
     * The **Share** option appears on the dropdown menu only if you have permissions to grant access. See [Available permission levels](#available-permission-levels).

docs/manage/data-archiving/archive.md

@@ -184,7 +184,7 @@ Click on a table row to view the Source details. This includes:
 * **Description**
 * **AWS S3 bucket**
 * All **Ingestion jobs** that are and have been created on the Source.
-    * Each ingestion job shows the name, time window, and volume of data processed by the job. Click the icon ![open in search icon.png](/img/archive/open-search-icon.png) to the right of the job name to start a Search against the data that was ingested by the job.
+    * Each ingestion job shows the name, time window, and volume of data processed by the job. Click the icon <img src={useBaseUrl('img/archive/open-search-icon.png')} alt="Open in search icon" width="30" /> to the right of the job name to start a Search against the data that was ingested by the job.
     * Hover your mouse over the information icon to view who created the job and when.<br/><img src={useBaseUrl('img/archive/archive-details-pane.png')} alt="Archive details pane" width="325"/>
 
 ## Create an ingestion job

docs/manage/field-extractions/create-field-extraction-rule.md

@@ -4,6 +4,7 @@ title: Create a Field Extraction Rule
 description: Field Extraction Rules (FER) tell Sumo Logic which fields to parse out automatically.
 ---
 
+import useBaseUrl from '@docusaurus/useBaseUrl';
 import Iframe from 'react-iframe';
 import FerLimit from '../../reuse/fer-limitations.md';
 
@@ -47,7 +48,7 @@ To create a Field Extraction Rule:
 
 1. [**New UI**](/docs/get-started/sumo-logic-ui). To access the Field Extraction Rules page, in the main Sumo Logic menu select **Data Management**, and then under **Logs** select **Field Extraction Rules**. You can also click the **Go To...** menu at the top of the screen and select **Field Extraction Rules**. <br/>[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Logs > Field Extraction Rules**. 
 1. Click the **+ Add** button on the top right of the table.
-1. The **Add Field Extraction Rule** form will appear:<br/> ![Create Field extraction rule with dynamic parsing.png](/img/field-extraction-rules/create-fer.png)
+1. The **Add Field Extraction Rule** form will appear:<br/><img src={useBaseUrl('img/field-extraction-rules/create-fer.png')} alt="Create Field extraction rule with dynamic parsing" style={{border: '1px solid gray'}} width="400" />
 1. Enter the following options:
     * **Rule Name**. Type a name that makes it easy to identify the rule.
     * **Applied At**. There are two types available, Ingest Time and Run Time. The main differences are Run Time only supports JSON data and the time that Sumo parses the fields. The following is an overview of the differences:

docs/manage/field-extractions/index.md

@@ -33,7 +33,7 @@ The Field Extraction Rules page displays the following information: 
 
 When hovering over a row in the table there are icons that appear on the far right for editing, disabling and deleting the rule.
 
-* **Status** shows a checkmark in a green circle ![check in green circle.png](/img/reuse/green-check-circle.png) to indicate if the Rule is actively being applied or an exclamation mark in a red circle ![exclamation in red circle.png](/img/reuse/exclamation-red-circle.png) to indicate if the Rule is disabled.
+* **Status** shows a checkmark in a green circle <img src={useBaseUrl('img/reuse/green-check-circle.png')} alt="Check in green circle" width="20" /> to indicate if the Rule is actively being applied or an exclamation mark in a red circle <img src={useBaseUrl('img/reuse/exclamation-red-circle.png')} alt="Exclamation in red circl" width="20" /> to indicate if the Rule is disabled.
 * **Rule Name**
 * **Applied At** indicates when the field extraction process occurs, either at Ingest or Run time.
 * **Scope** 

docs/manage/fields.md

@@ -86,13 +86,13 @@ Fields can be assigned to a Collector and Source using the **Fields** input ta
 
 1. Click **Save**.
 
-![edit collector fields name.png](/img/fields/edit-collector-fields-name.png)
+<img src={useBaseUrl('img/fields/edit-collector-fields-name.png')} alt="Edit collector fields name" style={{border: '1px solid gray'}} width="600" />
 
 In the above example, we have created a new field called `cluster` and set the value to `k8s.dev`. With this configuration, any logs sent to this Collector will now have this key-value pair associated with it.
 
 With this association, you can search for `cluster=k8s.dev` to return your logs.
 
-![collector field search results.png](/img/fields/collector-field-search-results.png)
+<img src={useBaseUrl('img/fields/collector-field-search-results.png')} alt="Collector field search results" style={{border: '1px solid gray'}} width="800" />
 
 ### Using Collector API
 
@@ -181,7 +181,7 @@ curl -v -X POST -H 'X-Sumo-Fields:environment=dev,cluster=k8s' -T /file.txt <HTT
 
 When creating or editing your HTTP Source that will receive log data add the field `_convertHeadersToFields` with a value of `true`. This field needs to be added to your Fields schema to work.
 
-![convertHeadersToFields.png](/img/fields/convertHeadersToFields.png)
+<img src={useBaseUrl('img/fields/convertHeadersToFields.png')} alt="Convert headers to fields" style={{border: '1px solid gray'}} width="500" />
 
 With this field set on your Source, headers are processed as metadata fields. For example, a cURL command posting data with custom fields would look like:
 
@@ -235,7 +235,7 @@ You need the **Manage Fields** [role capability](users-roles/roles/role-capab
 
 The Fields page displays the following information: 
 
-* **Status** shows a checkmark in a green circle <img src={useBaseUrl('img/reuse/green-check-circle.png')} alt="green check circle.png" width="20"/> to indicate if the field is actively being applied or an exclamation mark in a red circle ![red-exclamation-circle.png](/img/fields/red-exclamation-circle.png) to indicate if the field is disabled and being dropped.
+* **Status** shows a checkmark in a green circle <img src={useBaseUrl('img/reuse/green-check-circle.png')} alt="green check circle.png" width="20"/> to indicate if the field is actively being applied or an exclamation mark in a red circle <img src={useBaseUrl('img/fields/red-exclamation-circle.png')} alt="Red exclamation circle" width="20" /> to indicate if the field is disabled and being dropped.
 * **Field Name** is the name of the field, known as the key in the key-value pair.
 * **Data Type** shows the data type of the field.
 * **Field Extraction Rules** shows the number of Field Extraction Rules that reference the field.
@@ -263,16 +263,14 @@ When hovering over a row in the table there are icons that appear on the far ri
 
 For the fields listed, select a row to view its details. A details pane appears to the right of the table where you can disable and delete the field.<br/><img src={useBaseUrl('/img/fields/selected-field-details-pane.png')} alt="Manage Fields" style={{border:'1px solid gray'}} width="450"/>
 
-![selected field details pane.png](/img/fields/selected-field-details-pane.png)
-
 #### Add field
 
 Adding a field will define it in the Fields schema allowing it to be assigned as metadata to your logs.
 
 1. Click the **+ Add** button on the top right of the table. A panel named **Add Field** appears to the right of the fields table.
 1. Input a field name and click **Save**.
 
-![add field input.png](/img/fields/add-field-input.png)
+<img src={useBaseUrl('img/fields/add-field-input.png')} alt="Add field input" style={{border: '1px solid gray'}} width="400" />
 
 #### Disable field
 
@@ -290,15 +288,15 @@ In the details pane of the field, click the **Disable** button.<br/><img src={u
 Deleting a field does not delete historical data assigned with that field. If you delete a field by mistake and one or more of those dependencies break, you can re-add the field to get things working properly again. You should always disable a field and ensure things are behaving as expected before deleting a field.
 :::
 
-Select the **Delete** button in the details pane of the field. To delete a field you need to remove any references to it from some features. If the field is used by any of the following
+Select the **Delete** button in the details pane of the field. To delete a field you need to remove any references to it from some features if the field is used by any of the following:
 
 * Field Extraction Rule
 * Role
 * Partition
 * Collector
 * Source
 
-<br/><img src={useBaseUrl('/img/fields/delete-icon.png')} alt="delete-icon" style={{border:'1px solid gray'}} width="450"/>
+<img src={useBaseUrl('/img/fields/delete-icon.png')} alt="delete-icon" style={{border:'1px solid gray'}} width="300"/>
 
 You will see the following prompt and you must remove the field reference before you can delete it.
 
@@ -308,11 +306,11 @@ Built-in fields cannot be deleted.
 
 For example, if the field is used by a Field Extraction Rule, you must first delete the Field Extraction Rule before you can delete the field.
 
-![field cannot delete.png](/img/fields/field-cannot-delete.png)
+<img src={useBaseUrl('img/fields/field-cannot-delete.png')} alt="Field cannot delete" style={{border: '1px solid gray'}} width="400>" />
 
 If the field is not used by those features you will see the following prompt.
 
-![delete field confirm.png](/img/fields/delete-field-confirm.png)
+<img src={useBaseUrl('img/fields/delete-field-confirm.png')} alt="Delete field confirm" style={{border: '1px solid gray'}} width="400" />
 
 #### View dropped fields
 

docs/manage/health-events.md

@@ -4,6 +4,8 @@ title: Health Events
 description: Monitor the health of your Collectors and Sources.
 ---
 
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
 ## Availability
 
 | Account Type | Account Level |
@@ -40,11 +42,11 @@ On the health events table, you can search, filter, and sort incidents by ke
 
 [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). To access the health events table, in the main Sumo Logic menu select **Manage Data > Monitoring > Health Events**. 
 
-![health events table.png](/img/health-events/health-events-table.png)
+<img src={useBaseUrl('img/health-events/health-events-table.png')} alt="Health events tabl" style={{border: '1px solid gray'}} width="800" />
 
 Click on a row to view the details of a health event.
 
-![health event detail.png](/img/health-events/health-event-detail.png)
+<img src={useBaseUrl('img/health-events/health-event-detail.png')} alt="Health event detail" style={{border: '1px solid gray'}} width="400" />
 
 Click the **Create Scheduled Search** button on the details pane to get alerts for specific health events. The unique identifier of the resource, such as the Source or Collector, is used in the query. See [Schedule a Search](../alerts/scheduled-searches/schedule-search.md) for details.
 
@@ -57,8 +59,8 @@ Under the **More Actions** menu you can select:
 
 Events are categorized by two severity levels, warning and error. The severity column has color-coded error and warning events so you can quickly determine the severity of a given issue.
 
-* ![warning label.png](/img/health-events/warning-label.png) A warning indicates the Collector or Source has a configuration issue or is operating in a degraded state.
-* ![Error label.png](/img/health-events/Error-label.png) An error indicates the Collector or Source is unable to collect data as expected.
+* <img src={useBaseUrl('img/health-events/warning-label.png')} alt="Warning label" style={{border: '1px solid gray'}} width="75" /> A warning indicates the Collector or Source has a configuration issue or is operating in a degraded state.
+* <img src={useBaseUrl('img/health-events/Error-label.png')} alt="Error label" style={{border: '1px solid gray'}} width="50" /> An error indicates the Collector or Source is unable to collect data as expected.
 
 ### Common parameters
 
@@ -138,12 +140,7 @@ A **Health** column on the Collection page shows color-coded healthy, error, a
 
 The **status** column now shows the status of Sources manually paused by users.
 
-![Collection health column.png](/img/health-events/Collection-health-column.png)
-
-* Hover your mouse over a Collector or Source to view a tooltip that provides the number of health events detected on the Collector or Source.
-
-    ![health tooltip.png](/img/health-events/health_tooltip.png)
-
-* Click on the **Health** status in a row to view a pop-up displaying a list of related events.
+<img src={useBaseUrl('img/health-events/Collection-health-column.png')} alt="Collection health column" style={{border: '1px solid gray'}} width="800" />
 
-    ![object event details.png](/img/health-events/object_event_details.png)
+* Hover your mouse over a Collector or Source to view a tooltip that provides the number of health events detected on the Collector or Source.<br/><img src={useBaseUrl('img/health-events/health_tooltip.png')} alt="Health tooltip" style={{border: '1px solid gray'}} width="150" />
+* Click on the **Health** status in a row to view a pop-up displaying a list of related events.<br/><img src={useBaseUrl('img/health-events/object_event_details.png')} alt="Object event details" style={{border: '1px solid gray'}} width="500" />

docs/manage/ingestion-volume/collection-status-page.md

@@ -4,12 +4,13 @@ title: Collection Status Page
 description: Provides a visual snapshot of the message history for your deployment, and a message volume histogram for each Collector.
 ---
 
+import useBaseUrl from '@docusaurus/useBaseUrl';
 
 The Status page provides a message volume history for your account, as well as a message volume histogram for each Collector, giving you immediate visual feedback about traffic spikes or collection issues. To see statistics for any bar in the histogram, hover your mouse pointer over the area of interest.
 
 When you first install a Collector it is common to configure Sources to collect some historical data, rather than from the moment of installation. In this case, the status page shows a spike in message volume and then levels out as collection reaches a steady state. For example, a local log file can contain millions of log messages. When the Collector is initialized, it quickly gathers all those logs and sends them to Sumo Logic resulting in a traffic spike. After the initial collection, the Collector continues to tail the file, reading from the end of the file as new entries are created, and sends a smaller number of new log messages.
 
-![Status tab](/img/manage/ingestion-volume/collection-status.png)
+<img src={useBaseUrl('img/manage/ingestion-volume/collection-status.png')} alt="Status tab" style={{border: '1px solid gray'}} width="800" />
 
 * **A.** Select to show all, running, or stopped Collectors.  
 * **B.** Select how many columns of Collectors are displayed.  

docs/manage/ingestion-volume/data-volume-index/log-tracing-data-volume-index.md

@@ -4,6 +4,8 @@ title: Log and Tracing Data Volume Index
 description: The Data Volume Index is populated with a set of log messages that contain information on how much data (by bytes and messages count) your account is ingesting.
 ---
 
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
 The data volume index is populated with a set of log messages every five minutes. The messages contain information on how much data (by bytes and messages count) your account is ingesting. Your data volume is calculated based on when your logs were received, in Sumo this timestamp is stored with the `_receiptTime` [metadata](/docs/search/get-started-with-search/search-basics/built-in-metadata) field. Each log message includes information based on one of the following index source categories.
 
 | Index Log Type | Index Source Category |
@@ -97,7 +99,7 @@ _index=sumologic_volume _sourceCategory = "sourcecategory_and_tier_volume"
 
 would produce results such as:
 
-![clipboard_e08593bedbf920dea82726b15964e56f6.png](/img/manage/ingestion-volume/volume-each-category.png)
+<img src={useBaseUrl('img/manage/ingestion-volume/volume-each-category.png')} alt="Volume for each category" style={{border: '1px solid gray'}} width="500" />
 
 **Volume for Each Collector by Tier**
 
@@ -223,7 +225,7 @@ _index=sumologic_volume _sourceCategory="sourcecategory_tracing_volume"
 
 This query produces results like these: 
 
-![tracing-volume-source-category](/img/manage/ingestion-volume/tracing-volume-source-category.png)
+<img src={useBaseUrl('img/manage/ingestion-volume/tracing-volume-source-category.png')} alt="Tracing volume source category" style={{border: '1px solid gray'}} width="400" />
 
 #### Tracing volume by collector
 
@@ -238,7 +240,7 @@ _index=sumologic_volume _sourceCategory="collector_tracing_volume"
 
 This query produces results like these:
 
-![image](/img/manage/ingestion-volume/tracing-volume-source-category.png)
+<img src={useBaseUrl('img/manage/ingestion-volume/tracing-volume-source-category.png')} alt="Tracing volume by collector" style={{border: '1px solid gray'}} width="400" />
 
 #### Tracing volume for a specific collector