Continue with send-data images

Author: jpipkin1

.vscode/settings.json

@@ -0,0 +1,3 @@
+{
+    "editor.hover.enabled": false
+}

docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/aws-cost-explorer-source.md

@@ -35,7 +35,7 @@ To configure an AWS Cost Explorer Source:
 1. (Optional) For **Source Category**, enter any string to tag the output collected from the Source. Category [metadata](/docs/search/get-started-with-search/search-basics/built-in-metadata) is stored in a searchable field called `_sourceCategory`.
 1. For [Fields](/docs/manage/fields), click the **+Add** link to add custom log metadata. Define the fields you want to associate. Each field needs a name (key) and value.
    * <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, or is disabled 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**.<br/><br/>It is preferable to add an **account** field (for the dashboards) and assign it a friendly name to identify the corresponding AWS account.<br/> ![accountField.png](/img/send-data/accountField.png)
+   * <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, or is disabled 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**.<br/><br/>It is preferable to add an **account** field (for the dashboards) and assign it a friendly name to identify the corresponding AWS account.<br/><img src={useBaseUrl('img/send-data/accountField.png')} alt="Account field" style={{border: '1px solid gray'}} width="400" />
 1. For the **AWS Access Key** and **AWS Secret Key**, provide the IAM User access key and secret key you want to use to authenticate collection requests.
 Make sure your IAM user has the following IAM policy attached with it.
      ```json

docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source.md

@@ -41,16 +41,13 @@ Third party apps or services can be configured to send event data to Event Hubs
 
 The Event Hub doesn't have to be in the same subscription as the resource sending logs if the user who configures the setting has appropriate Azure role-based access control access to both subscriptions. By using Azure Lighthouse, it's also possible to have diagnostic settings sent to a event hub in another Azure Active Directory tenant. The event hub namespace needs to be in the same region as the resource being monitored if the resource is regional so you may have to configure multiple Azure Event Hubs Sources. More details about destination limitations and permissions are described [here](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/diagnostic-settings?tabs=portal#destination-limitations).
 
-1. [Create an Event Hub using the Azure portal](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create) by navigating to Event Hubs in the Azure Portal.<br/> ![AzureEventHubstep1.png](/img/send-data/AzureEventHubstep1.png)
-1. Create an Event Hubs namespace. In this example, Namespace is set to **cnctest**:<br/>![AzureEventHubstep2.png](/img/send-data/AzureEventHubstep2.png)<br/> ![AzureEventHubstep3.png](/img/send-data/AzureEventHubstep3.png)
-1. Create an Event Hub Instance.<br/> ![AzureEventHubstep4.png](/img/send-data/AzureEventHubstep4.png)
-    * Shared Access Policies can be set up for the entire namespace. These policies can be used to access/manage all hubs in the namespace. A policy for the namespace is created by default: **RootManageSharedAccessKey** <br/>![AzureEventHubstep5.png](/img/send-data/AzureEventHubstep5.png)
+1. [Create an Event Hub using the Azure portal](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create) by navigating to Event Hubs in the Azure Portal.<br/><img src={useBaseUrl('img/send-data/AzureEventHubstep1.png')} alt="Select Azure Event Hubs" style={{border: '1px solid gray'}} width="800" />
+1. Create an Event Hubs namespace. In this example, Namespace is set to **cnctest**:<br/><img src={useBaseUrl('img/send-data/AzureEventHubstep2.png')} alt="Select Add" style={{border: '1px solid gray'}} width="300" /><br/><img src={useBaseUrl('img/send-data/AzureEventHubstep3.png')} alt="Select Review and Create" style={{border: '1px solid gray'}} width="600" />
+1. Create an Event Hub Instance.<br/><img src={useBaseUrl('img/send-data/AzureEventHubstep4.png')} alt="Create Event Hubs instance" style={{border: '1px solid gray'}} width="800" />
+    * Shared Access Policies can be set up for the entire namespace. These policies can be used to access/manage all hubs in the namespace. A policy for the namespace is created by default: **RootManageSharedAccessKey** <br/><img src={useBaseUrl('img/send-data/AzureEventHubstep5.png')} alt="Shared access policies" style={{border: '1px solid gray'}} width="500" />
     <br/>In this example, Event Hub Instance is set to <strong>my-hub</strong>.
-1. Create a [Shared Access Policy](https://docs.microsoft.com/en-us/azure/governance/policy/overview) with the **Listen** claim to the newly created Event Hub Instance:<br/>  ![AzureEventHubstep6.png](/img/send-data/AzureEventHubstep6.png)<br/>
-    ![AzureEventHubstep7.png](/img/send-data/AzureEventHubstep7.png)<br/>
-    ![AzureEventHubstep8.png](/img/send-data/AzureEventHubstep8.png)<br/>
-    In this example, Event Hub Instance is set to **SumoCollectionPolicy**.
-1. Copy the Shared Access Policy Key.<br/>  ![AzureEventHubstep9.png](/img/send-data/AzureEventHubstep9.png)
+1. Create a [Shared Access Policy](https://docs.microsoft.com/en-us/azure/governance/policy/overview) with the **Listen** claim to the newly created Event Hub Instance:<br/><img src={useBaseUrl('img/send-data/AzureEventHubstep6.png')} alt="Listen claim" style={{border: '1px solid gray'}} width="800" /><br/><img src={useBaseUrl('img/send-data/AzureEventHubstep7.png')} alt="Shared access policies" style={{border: '1px solid gray'}} width="500" /><br/><img src={useBaseUrl('img/send-data/AzureEventHubstep8.png')} alt="SumoCollectionPolicy" style={{border: '1px solid gray'}} width="800" /><br/>In this example, Event Hub Instance is set to **SumoCollectionPolicy**.
+1. Copy the Shared Access Policy Key.<br/><img src={useBaseUrl('img/send-data/AzureEventHubstep9.png')} alt="Copy access key" style={{border: '1px solid gray'}} width="800" />
     Copy the Primary/Secondary key associated with this policy.
 1. When [configuring the Azure Event Hubs Source](#vendor-configuration) in Sumo Logic, our input fields might be:
 

docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/cloud-to-cloud-source-versions.md

@@ -25,19 +25,19 @@ Additional labels for pre-release and build metadata are available as extensions
 
 There is an **Upgrade Sources** link on the Collection page that shows a table of major upgrades available.
 
-![upgrade collectors button.png](/img/send-data/upgrade-collectors-button.png)
+<img src={useBaseUrl('img/send-data/upgrade-collectors-button.png')} alt="Upgrade collectors button" style={{border: '1px solid gray'}} width="800" />
 
 A table with Sources available to upgrade is displayed when you click **Upgrade Sources** on the Collection page.
 
-![versions table.png](/img/send-data/versions-table.png)
+<img src={useBaseUrl('img/send-data/versions-table.png')} alt="Sources available" style={{border: '1px solid gray'}} width="800" />
 
 Since these are major versions they do require you to take some action. You can hover and select the upgrade icon to open the Source in edit mode and provide the required information for the upgrade.
 
-![upgrade button.png](/img/send-data/upgrade-button.png)
+<img src={useBaseUrl('img/send-data/upgrade-button.png')} alt="Upgrade button" style={{border: '1px solid gray'}} width="400" />
 
 The Source will show the required upgrade instructions at the top of the panel. The following screenshot shows that the Source requires you to fill out a new field called **format**.
 
-![major version upgrade requirements.png](/img/send-data/major-version-upgrade-requirements.png)
+<img src={useBaseUrl('img/send-data/major-version-upgrade-requirements.png')} alt="Major version upgrade requirements" style={{border: '1px solid gray'}} width="400" />
 
 Once you complete the upgrade instructions you can select the **Upgrade** button to initiate the version upgrade.
 

docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/google-workspace-source.md

@@ -33,7 +33,7 @@ To create service account credentials, follow the steps below:
 1. Navigate to the [Google Console service account](https://console.cloud.google.com/projectselector2/iam-admin/serviceaccounts?pli=1&supportedpurview=project) page.
 1. Log in with your credentials.
 1. Create a new project or select from the existing projects.<br/> <img src={useBaseUrl('img/send-data/workspace-setup1.png')} alt="workspace-setup1.png" width="600" />
-1. Enable **Admin SDK API** to have an administrator access. To locate this setting, you can search for **Admin SDK** in the search bar. Then select the **Enable** button.<br/> <img src={useBaseUrl('img/send-data/workspace-setup2.png')} alt="workspace-setup2.png" width="500" />
+1. Enable **Admin SDK API** to have an administrator access. To locate this setting, you can search for **Admin SDK** in the search bar. Then select the **Enable** button.<br/> <img src={useBaseUrl('img/send-data/workspace-setup2.png')} alt="workspace-setup2.png" width="400" />
 1. You will be redirected to the Admin dashboard page. Select the **Credentials** option from the left navigation. <br/> <img src={useBaseUrl('img/send-data/select-credentials.png')} alt="select-credentials.png" width="700" />
 1. Click the <img src={useBaseUrl('img/send-data/create-cred-button.png')} alt="create-cred-button.png" width="150" /> button at the menu bar of the Google Console page, and select Service account from the options that appear.<br/> <img src={useBaseUrl('img/send-data/create-credentials-service.png')} alt="create-credentials-service.png" width="600" />
 1. After entering the service account details, you may leave the **Optional** fields and continue to click **Done**. <br/> <img src={useBaseUrl('img/send-data/service-account-details.png')} alt="login-service-account-details.png" width="500" />
@@ -48,7 +48,7 @@ To add domain-wide delegation to your service account using the client ID or Key
 1. Navigate to the [Google Console service account](https://console.cloud.google.com/projectselector2/iam-admin/serviceaccounts?pli=1&supportedpurview=project) page.
 1. Select your service account.
 1. Go to **Advanced** settings section.
-1. Under **Domain-wide delegation**, find your service account's **Client ID**. Click ![Copy](/img/send-data/copy-button.png) to copy the client ID value to your clipboard.<br/><img src={useBaseUrl('img/send-data/domain-delegation.png')} alt="domain-delegation.png" width="600" />
+1. Under **Domain-wide delegation**, find your service account's **Client ID**. Click <img src={useBaseUrl('img/send-data/copy-button.png')} alt="Copy button" style={{border: '1px solid gray'}} width="30" /> to copy the client ID value to your clipboard.<br/><img src={useBaseUrl('img/send-data/domain-delegation.png')} alt="Domain-wide delegation" width="600" />
 1. If you have super administrator access to the relevant Google Workspace account, click **View Google Workspace Admin Console**, then sign in using a super administrator user account and continue following the steps in the section below.
  :::note
  If you do not have super administrator access to the relevant Google Workspace account, contact a super administrator for that account and send them your service account's Client ID and list of OAuth Scopes so they can complete the following steps in the Admin console.

docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/microsoft-azure-ad-inventory-source.md

@@ -35,18 +35,12 @@ The user creating the service application does not need to be an administrator.
 Use the following steps to create a service application:
 
 1. Sign in to the [Azure Active Directory Portal](https://aad.portal.azure.com/)
-1. Then select **Azure Active Directory** in the left menu.
-    ![Azure AD step 2.png](/img/send-data/Azure-AD-step-2.png)
-1. Then select **App Registrations**.<br/>
-    ![Azure AD step 3 red box.png](/img/send-data/Azure-AD-step-3-red-box.png)
-1. Then select **New Registration**. Go through the registration process, providing a name for the application. Selecting **Accounts in this organizational directory only** is sufficient.
-    ![Azure new registration in step 4.png](/img/send-data/Azure-new-registration-in-step-4.png)
-1. After the Application is registered (created), be sure to copy the **Application (client) ID** and the **Directory (tenant) ID**. These are used later as configuration parameters in Sumo Logic when creating the Microsoft Azure AD Inventory Source.
-    ![Azure created app in step 5.png](/img/send-data/Azure-created-app-in-step-5.png)
-1. Within the Application configuration page, select **Certificates and Secrets** to create an Application Client Secret Key.
-    ![Azure AD step 6.png](/img/send-data/Azure-AD-step-6.png)
-1. Copy the **Client Secret Value** (pictured below). It's needed later in Sumo Logic when creating the Microsoft Azure AD Inventory Source.
-    ![Azure AD step 7.png](/img/send-data/Azure-AD-step-7.png)
+1. Then select **Azure Active Directory** in the left menu.<br/><img src={useBaseUrl('img/send-data/Azure-AD-step-2.png')} alt="Select Azure Active Directory" style={{border: '1px solid gray'}} width="800" />
+1. Then select **App Registrations**.<br/><img src={useBaseUrl('img/send-data/Azure-AD-step-3-red-box.png')} alt="Select App Registrations" style={{border: '1px solid gray'}} width="300" />
+1. Then select **New Registration**. Go through the registration process, providing a name for the application. Selecting **Accounts in this organizational directory only** is sufficient.<br/><img src={useBaseUrl('img/send-data/Azure-new-registration-in-step-4.png')} alt="Select new registration" style={{border: '1px solid gray'}} width="800" />
+1. After the Application is registered (created), be sure to copy the **Application (client) ID** and the **Directory (tenant) ID**. These are used later as configuration parameters in Sumo Logic when creating the Microsoft Azure AD Inventory Source.<br/><img src={useBaseUrl('img/send-data/Azure-created-app-in-step-5.png')} alt="Copy IDs" style={{border: '1px solid gray'}} width="800" />
+1. Within the Application configuration page, select **Certificates and Secrets** to create an Application Client Secret Key.<br/><img src={useBaseUrl('img/send-data/Azure-AD-step-6.png')} alt="Cerfifications and secrets" style={{border: '1px solid gray'}} width="800" />
+1. Copy the **Client Secret Value** (pictured below). It's needed later in Sumo Logic when creating the Microsoft Azure AD Inventory Source.<br/><img src={useBaseUrl('img/send-data/Azure-AD-step-7.png')} alt="Client secret value" style={{border: '1px solid gray'}} width="800>" />
 1. Request the appropriate permissions for the application. Click on **API Permissions**, then **Add a permission** and select **Microsoft Graph**.
 
 From there, select (or search for) the following permissions under type **Application permissions**. An Administrator must approve (grant) these permissions before the integration will function.
@@ -64,7 +58,7 @@ You require additional permission to collect `signInActivityData` for User.
 
 Personal Microsoft accounts are not supported.
 
-![azure ad step 8.png](/img/send-data/azure-ad-step-8.png)
+<img src={useBaseUrl('img/send-data/azure-ad-step-8.png')} alt="Request API permissions" style={{border: '1px solid gray'}} width="800" />
 
 ### Source configuration