Continue with send-data images

Author: jpipkin1

docs/send-data/collect-from-other-data-sources/amazon-cloudwatch-logs/collect-with-cloudformation-template-with-secured-sumo-endpoint.md

@@ -5,6 +5,8 @@ sidebar_label: Collect Logs using CloudFormation with Secured Endpoint
 description: Learn how to collect Amazon CloudWatch Logs using a CloudFormation template with secured Sumo Logic endPoint.
 ---
 
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
 :::note
 We strongly recommend the alternative collection process described on [AWS Kinesis Firehose for Logs Source](/docs/send-data/hosted-collectors/amazon-aws/aws-kinesis-firehose-logs-source/), which is more robust and reliable, where you do not need to manage resources. Lambda based collection methods are limited by time out, concurrency, and memory limits.
 :::
@@ -48,7 +50,7 @@ If you're using the AWS Console, do the following:
    * **Type**. Select SecureString.
    * **KMS Key Source**. Select the KMS Key ID or use the default KMS key.
    * **Value**. Paste the value of the SUMO_ENDPOINT_URL copied while creating the HTTP source.
-1. Click **Create Parameter**.<br/> ![Create_SecureString_Parameter.png](/img/send-data/Create_SecureString_Parameter.png)
+1. Click **Create Parameter**.<br/><img src={useBaseUrl('img/send-data/Create_SecureString_Parameter.png')} alt="Create Parameter" style={{border: '1px solid gray'}} width="800" />
 
 :::note
 You can verify whether the parameter is created successfully by going to https://console.aws.amazon.com/systems-manager/parameters/?region=us-east-1&tab=Table and looking for parameter `SUMO_ENDPOINT`.
@@ -71,16 +73,12 @@ For instructions, follow [Step 3](/docs/send-data/collect-from-other-data-source
 
 1. Log in to the [AWS Management Console](https://s3.console.aws.amazon.com/).
 1. Under **Management Tools**, select **CloudFormation**.
-1. Create a new stack by clicking **Create Stack**, then select **With new resources (standard).** <br/> ![Create_Stack_on_AWS_1.gif](/img/send-data/Create_Stack_on_AWS_1.gif)
+1. Create a new stack by clicking **Create Stack**, then select **With new resources (standard).** <br/><img src={useBaseUrl('img/send-data/Create_Stack_on_AWS_1.gif')} alt="Create stack on AWS" style={{border: '1px solid gray'}} width="600" />
 1. On the **Specify Template** window, do one of the following:
 
-   * If you have downloaded and optionally modified the CloudFormation template, choose to **Upload a template file**, upload the `DLQLambdaCloudFormationWithSecuredEndpoint.json` file, and then click **Next**.
-
-    ![Create_Stack_on_AWS_2.png](/img/send-data/Create_Stack_on_AWS_2.png)
+   * If you have downloaded and optionally modified the CloudFormation template, choose to **Upload a template file**, upload the `DLQLambdaCloudFormationWithSecuredEndpoint.json` file, and then click **Next**.<br/><img src={useBaseUrl('img/send-data/Create_Stack_on_AWS_2.png')} alt="Upload a template file" style={{border: '1px solid gray'}} width="500" />
 
-   * Otherwise, if you did not modify the CloudFormation template, select **Specify an Amazon S3 template URL** and enter: `https://s3.amazonaws.com/appdev-cloudformation-templates/DLQLambdaCloudFormationWithSecuredEndpoint.json`        
-
-    ![Create_Stack_on_AWS_3.png](/img/send-data/Create_Stack_on_AWS_3.png)
+   * Otherwise, if you did not modify the CloudFormation template, select **Specify an Amazon S3 template URL** and enter: `https://s3.amazonaws.com/appdev-cloudformation-templates/DLQLambdaCloudFormationWithSecuredEndpoint.json`<br/><img src={useBaseUrl('img/send-data/Create_Stack_on_AWS_3.png')} alt="Specify an Amazon S3 template URL" style={{border: '1px solid gray'}} width="500" />
 
 1. Select **Next** and the **Specify Stack Details** window appears. Enter the following:
    * **Stack Name**.
@@ -94,9 +92,7 @@ For instructions, follow [Step 3](/docs/send-data/collect-from-other-data-source
     :::
 
    * **NumOfWorkers.** (Optional) Increase this value to speed up the dead letter queue (DLQ) processing.
-   * **SumoURLDecryptKeyID.** (Required) Enter the Key ID copied from “Get the KMS Key ID” step.
-
-    ![Create_Stack_on_AWS_4.png](/img/send-data/Create_Stack_on_AWS_4.png)
+   * **SumoURLDecryptKeyID.** (Required) Enter the Key ID copied from “Get the KMS Key ID” step.<br/><img src={useBaseUrl('img/send-data/Create_Stack_on_AWS_4.png')} alt="Specify stack details" style={{border: '1px solid gray'}} width="800" />
 
 1. Click **Next**. The **Configure Stack Options** screen will appear. You can optionally add AWS tags to tag the resources created by this Cloudformation stack. Click **Next** to get to the final **Review** window.
 

docs/send-data/collect-from-other-data-sources/amazon-cloudwatch-logs/collect-with-cloudformation-template.md

@@ -164,10 +164,10 @@ If you do not want the `SumoCWSpilloverAlarm` alarm to be created, remove the de
 
 1. Sign in to the [AWS Management Console](https://s3.console.aws.amazon.com).
 1. In the **Management Tools** menu, select **CloudFormation**.
-1. Create a new stack by clicking **Create Stack**, then select **With new resources (standard)**.<br/>  ![CF_animated.gif](/img/send-data/CF_animated.gif)
+1. Create a new stack by clicking **Create Stack**, then select **With new resources (standard)**.<br/><img src={useBaseUrl('img/send-data/CF_animated.gif')} alt="Create a new stack" style={{border: '1px solid gray'}} width="600" />
 1. On the **Specify Template** window, do one of the following:
-   * If you have downloaded and optionally modified the CloudFormation template, choose to **Upload a template file**, upload the `DLQLambdaCloudFormation.json` file, and then click **Next**.<br/>  ![Create_Stack_dialog.png](/img/send-data/Create_Stack_dialog.png)
-   * Otherwise, if you did not modify the CloudFormation template, select **Specify an Amazon S3 template URL** and enter: `https://s3.amazonaws.com/appdev-cloudformation-templates/DLQLambdaCloudFormation.json`<br/>  ![Create_Stack_dialog_2.png](/img/send-data/Create_Stack_dialog_2.png)
+   * If you have downloaded and optionally modified the CloudFormation template, choose to **Upload a template file**, upload the `DLQLambdaCloudFormation.json` file, and then click **Next**.<br/><img src={useBaseUrl('img/send-data/Create_Stack_dialog.png')} alt="Upload a template file" style={{border: '1px solid gray'}} width="500" />
+   * Otherwise, if you did not modify the CloudFormation template, select **Specify an Amazon S3 template URL** and enter: `https://s3.amazonaws.com/appdev-cloudformation-templates/DLQLambdaCloudFormation.json`<br/><img src={useBaseUrl('img/send-data/Create_Stack_dialog_2.png')} alt="Specify an Amazon S3 URL" style={{border: '1px solid gray'}} width="500" />
 1. Select **Next** and the **Specify Stack Details** window appears. Enter the following:
    * **Stack Name**.
    * **EmailID** (Optional) Used for alerts.
@@ -179,7 +179,7 @@ If you do not want the `SumoCWSpilloverAlarm` alarm to be created, remove the de
     LogStreamPrefix field does not accept special characters (`[|\\{}()[\]^$+*?.-]`). For example, you can use the comma-separated list like test-name, test-logs as the LogStream name prefixes.
     :::
     * **NumOfWorkers.** (Optional) Increase this value to speed up dead letter queue (DLQ) processing.
-    * **SumoEndPointURL** (Required). Enter the HTTP Source Address URL from [Add a Hosted Collector and HTTP Source](#step-1-add-a-hosted-collector-and-http-source).<br/>  ![Specify_Stack_Details.png](/img/send-data/Specify_Stack_Details.png)
+    * **SumoEndPointURL** (Required). Enter the HTTP Source Address URL from [Add a Hosted Collector and HTTP Source](#step-1-add-a-hosted-collector-and-http-source).<br/><img src={useBaseUrl('img/send-data/Specify_Stack_Details.png')} alt="Specify stack details" style={{border: '1px solid gray'}} width="700" />
 1. Click **Next**. The **Configure Stack Options** screen will appear. You can optionally add AWS tags to tag the resources created by this CloudFormation stack. Click **Next** to get to the final **Review** window.
 1. In the **Review** window, click the checkbox acknowledging that you understand the the template creates IAM resources, and click **Create**.
 
@@ -205,7 +205,7 @@ If alarm resources in [Step 3](#remove-alarm-resources-optional) is not removed,
 
 Sign in to the email account whose address you provided when performing the configuration described in [Create a stack on the AWS CloudFormation console](#step-4-create-a-stack-on-the-aws-cloudformation-console) above. Look for an email with subject `AWS Notification - Subscription Confirmation`, like the example shown below.
 
-![aws-notification.png](/img/send-data/aws-notification.png)  
+<img src={useBaseUrl('img/send-data/aws-notification.png')} alt="AWS notification" style={{border: '1px solid gray'}} width="800" />
 
 To validate the email address, click **Confirm subscription** in the email.
 

docs/send-data/collect-from-other-data-sources/azure-blob-storage/append-blob/collect-logs.md

@@ -106,13 +106,9 @@ This section provides instructions on authorizing the App Service to list the st
 
 To authorize the App Service to list the storage account key, do the following:
 
-1. Go to **Storage accounts** and click **Access control (IAM)**.
+1. Go to **Storage accounts** and click **Access control (IAM)**.<br/><img src={useBaseUrl('img/send-data/AzureBlob_AccessControl_IAM.png')} alt="Azure Blob Access Control IAM" style={{border: '1px solid gray'}} width="400" />
 
-    ![AzureBlob_AccessControl_IAM.png](/img/send-data/AzureBlob_AccessControl_IAM.png)
-
-1. Click the **Add** **+** at the top of the page.
-
-    ![AzureBlob_IAM_Add.png](/img/send-data/AzureBlob_IAM_Add.png)
+1. Click the **Add** **+** at the top of the page.<br/><img src={useBaseUrl('img/send-data/AzureBlob_IAM_Add.png')} alt="Azure Blob IAM add" style={{border: '1px solid gray'}} width="800" />
 
 1. Select **Add role assignment** from dropdown.
 1. In the **Add role assignment** window, go to **Role** tab and choose **Storage Blob Data Reader**. Click **Next**. <br/><img src={useBaseUrl('/img/send-data/storage-blob-data-reader.png')} alt="storage-blob-data-reader" width="800"/>
@@ -131,17 +127,11 @@ This section provides instructions for creating an event grid subscription that
 
 To create an event grid subscription, do the following:
 
-1. In the left pane of the Azure portal click **All Services**, then search for and click **Event Grid Subscriptions**.
-
-    ![AzureBlob_EventGridSubscriptions.png](/img/send-data/AzureBlob_EventGridSubscriptions.png)
-
-1. At the top of the **Event Subscriptions** page, click **+Event Subscription**.
+1. In the left pane of the Azure portal click **All Services**, then search for and click **Event Grid Subscriptions**.<br/><img src={useBaseUrl('img/send-data/AzureBlob_EventGridSubscriptions.png')} alt="Azure Blob Event Grid Subscriptions" style={{border: '1px solid gray'}} width="600" />
 
-    ![AzureBlob_EventSubscriptionsPage.png](/img/send-data/AzureBlob_EventSubscriptionsPage.png)
+1. At the top of the **Event Subscriptions** page, click **+Event Subscription**.<br/><img src={useBaseUrl('img/send-data/AzureBlob_EventSubscriptionsPage.png')} alt="Azure Blob Event Subscription" style={{border: '1px solid gray'}} width="700" />
 
-    The Create Event Subscription dialog appears.
-
-    ![AzureBlob_CreatEventSubscription_dialog.png](/img/send-data/AzureBlob_CreatEventSubscription_dialog.png)
+    The Create Event Subscription dialog appears.<br/><img src={useBaseUrl('img/send-data/AzureBlob_CreatEventSubscription_dialog.png')} alt="Azure Blob Create Event Subscription dialog" style={{border: '1px solid gray'}} width="800" />
 
 1. Specify the following values for **Event Subscription Details**:
 
@@ -169,9 +159,7 @@ To create an event grid subscription, do the following:
    * **Endpoint Type**. Select **Event Hubs** from the dropdown.
    * **Endpoint.**  Click on **Select an endpoint.**
 
-    The Select Event Hub dialog appears.
-
-    ![AzureBlob_SelectEventHub-EventGrid.png](/img/send-data/AzureBlob_SelectEventHub-EventGrid.png)
+    The Select Event Hub dialog appears.<br/><img src={useBaseUrl('img/send-data/AzureBlob_SelectEventHub-EventGrid.png')} alt="Select Event Hub dialog" style={{border: '1px solid gray'}} width="400" />
 
 1. Specify the following Select Event Hub parameters, then click **Confirm Selection.**
 
@@ -182,9 +170,7 @@ To create an event grid subscription, do the following:
 1. Specify the following Filters tab options(Optional):
 
    * Check **Enable subject filtering**.
-   * To filter events by a container name, enter the following in the **Subject Begins With** field, replacing `<container_name>` with the name of the container from where you want to export logs: `/blobServices/default/containers/<container_name>/`
-
-   ![img](/img/send-data/AzureBlob_FiltersDialog.png)
+   * To filter events by a container name, enter the following in the **Subject Begins With** field, replacing `<container_name>` with the name of the container from where you want to export logs: `/blobServices/default/containers/<container_name>/`<br/><img src={useBaseUrl('img/send-data/AzureBlob_FiltersDialog.png')} alt="Create Event Subscription dialog" style={{border: '1px solid gray'}} width="800" />
 
 1. Click **Create**.
 
@@ -197,21 +183,18 @@ This assumes that your storage account access is enabled for selected networks.
 1. Create a subnet in a virtual network using the instructions in the [Azure documentation](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-manage-subnet#add-a-subnet). If you have multiple accounts in the same region, you can skip step 2 given below and use the same subnet and add it to the storage account as mentioned in step 3.
 1. Perform the steps below for BlobTaskConsumer function app:
    1. Go to **Function App > Settings > Networking**.
-   1. Under Outbound traffic, click on Vnet Integration. <br/>![azureblob-outbound](/img/send-data/appendblob/azureappendblob-outbound.png)
-   1. Add the Vnet and subnet created in Step 1. <br/>![azureblob-vnet](/img/send-data/azureblob-vnet.png)
-   1. Also copy the outbound IP addresses you’ll need to add in the firewall configuration of your storage account. <br/> ![azureblob-outboundip](/img/send-data/azureblob-outboundip.png)
-1. Go to your storage account from where you want to collect logs from. Go to Networking and add the same Vnet and subnet. <br/>![azureblob-storageacct](/img/send-data/azureblob-storageacct.png)
+   1. Under Outbound traffic, click on Vnet Integration. <br/><img src={useBaseUrl('img/send-data/appendblob/azureappendblob-outbound.png')} alt="Azure blob outbound" style={{border: '1px solid gray'}} width="600" />
+   1. Add the Vnet and subnet created in Step 1. <br/><img src={useBaseUrl('img/send-data/azureblob-vnet.png')} alt="Azure Blob Vnet" style={{border: '1px solid gray'}} width="800" />
+   1. Also copy the outbound IP addresses you’ll need to add in the firewall configuration of your storage account. <br/><img src={useBaseUrl('img/send-data/azureblob-outboundip.png')} alt="Azure Blob outbound" style={{border: '1px solid gray'}} width="800" />
+1. Go to your storage account from where you want to collect logs from. Go to Networking and add the same Vnet and subnet. <br/><img src={useBaseUrl('img/send-data/azureblob-storageacct.png')} alt="Azure Blob Storage account" style={{border: '1px solid gray'}} width="800" />
 1. Add the outbound IP addresses (copied in step 2.iv) from both BlobTaskConsumer functions under Firewall with each IP in a single row of Address range column.
-1. Verify by going to the subnet. You should see Subnet delegation and service endpoints as shown in the screenshot below. <br/>![azureblob-subnet](/img/send-data/azureblob-subnet.png)
+1. Verify by going to the subnet. You should see Subnet delegation and service endpoints as shown in the screenshot below. <br/><img src={useBaseUrl('img/send-data/azureblob-subnet.png')} alt="Azure Blob subnet" style={{border: '1px solid gray'}} width="800" />
 
 ## Upgrading Azure Functions
 
-1. Go to the resource group where the ARM template was deployed and go to each of the function apps.
-    ![azurefunctionapp-list](/img/send-data/azure_functionapp.png)
-1. Go to `Deployment -> Deployment Center` and click on `Sync`.
-    ![azurefunctionapp-sync](/img/send-data/azure_upgrade_sync.png)
-1. Go to `Logs` tab and check the `Status` column, it should show `Success`.
-    ![azurefunctionapp-status](/img/send-data/azure_upgrade_status.png)
+1. Go to the resource group where the ARM template was deployed and go to each of the function apps.<br/><img src={useBaseUrl('img/send-data/azure_functionapp.png')} alt="Azure function apps" style={{border: '1px solid gray'}} width="800" />
+1. Go to `Deployment -> Deployment Center` and click on `Sync`.<br/><img src={useBaseUrl('img/send-data/azure_upgrade_sync.png')} alt="Azure function app sync" style={{border: '1px solid gray'}} width="800" />
+1. Go to `Logs` tab and check the `Status` column, it should show `Success`.<br/><img src={useBaseUrl('img/send-data/azure_upgrade_status.png')} alt="Azure function app status" style={{border: '1px solid gray'}} width="800" />
 
 ## Azure Append Blob Limitations