chore: include missing new lines

newrelic · Feb 24, 2022 · 9fad958 · 9fad958
1 parent 1a85557
commit 9fad958
Show file tree

Hide file tree

Showing 6 changed files with 129 additions and 0 deletions.
diff --git a/.idea/aws.xml b/.idea/aws.xml
diff --git a/.idea/codeStyles/Project.xml b/.idea/codeStyles/Project.xml
diff --git a/.idea/codeStyles/codeStyleConfig.xml b/.idea/codeStyles/codeStyleConfig.xml
diff --git a/.idea/runConfigurations.xml b/.idea/runConfigurations.xml
diff --git a/.idea/sonarlint/issuestore/index.pb b/.idea/sonarlint/issuestore/index.pb
diff --git a/src/content/docs/logs/forward-logs/azure-log-forwarding.mdx b/src/content/docs/logs/forward-logs/azure-log-forwarding.mdx
@@ -37,7 +37,9 @@ Follow these steps:
 1. Make sure you have a [New Relic license key](/docs/apis/intro-apis/new-relic-api-keys/#ingest-license-key).
 2. Log in to [New Relic Logs](https://one.newrelic.com/launcher/logger.log-launcher) and click **Add more data sources** on the top right of the page.
 3. Under **Log ingestion**, click the `Microsoft Azure Event Hub` tile:
+
 ![Microsoft Azure Event Hub data sources button](./images/azure-eventhub-tile.png)
+
 4. Select the account you want to send the logs, and click **Continue**.
 5. Click **Generate API Key** and copy the generated **API Key**.
 6. Click **Deploy to Azure** and a new tab will be open with the ARM template loaded in Azure.
@@ -84,18 +86,31 @@ In the following example, we will demonstrate how to forward the Activity Logs f
 
 1. [Deploy the New Relic Event Hub ARM template](#eventhub-arm-setup)
 2. Navigate to your Kubernetes Service:
+
 ![Kubernetes Service Button](./images/azure-eventhub-k8s-service.png)
+
 3. In the left-hand menu, select `Monitoring` > `Diagnostic Settings`:
+
 ![Diagnostic Settings menu](./images/azure-eventhub-diagnosticsettings.png)
+
 4. Click on `Add diagnostic setting`:
+
 ![Add Diagnostic Setting button](./images/azure-eventhub-add-diagnostic-setting.png)
+
 5. Give your new setting a meaningful name:
+
 ![Diagnostic setting name](./images/azure-eventhub-diagnosticsetting-name.png)
+
 6. Select the Kubernetes (control pane) logs you want to collect:
+
 ![Kubernetes logs](./images/azure-eventhub-diagnostic-logs.png)
+
 7. On the `Destination details`, select `Stream to an event hub`, and configure the `Event hub namespace`, `Event hub name` and `Event hub policy name`. If you opted to create a new Event Hub and a namespace during the [ARM template deployment](#eventhub-arm-setup), select the following automatically created settings (the namespace name will have a different suffix):
+
 ![Destination details settings](./images/azure-eventhub-destination-details-settings.png)
+
 8. Click on `Save` to start forwarding your Kubernetes logs to New Relic:
+
 ![Diagnostic setting save button](./images/azure-eventhub-save-button.png)
 
 ## Send logs from Azure Blob storage
@@ -117,7 +132,9 @@ Follow these steps:
 1. Make sure you have a [New Relic license key](/docs/apis/intro-apis/new-relic-api-keys/#ingest-license-key).
 2. Log in to [New Relic Logs](https://one.newrelic.com/launcher/logger.log-launcher) and click **Add more data sources** on the top right of the page.
 3. Under **Log ingestion**, click the `Microsoft Azure Blob Storage` tile.
+
 ![Microsoft Azure Blob Storage data sources button](./images/azure-blobstorage-tile.png)
+
 4. Select the account you want to send the logs, and click **Continue**.
 5. Click **Generate API Key** and copy the generated **API Key**.
 6. Click **Deploy to Azure** and a new tab will be open with the ARM template loaded in Azure.