Skip to content

Commit

Permalink
chore: small update
Browse files Browse the repository at this point in the history
  • Loading branch information
jsubirat committed Feb 25, 2022
1 parent cd555e8 commit 3db3255
Showing 1 changed file with 4 additions and 5 deletions.
9 changes: 4 additions & 5 deletions src/content/docs/logs/forward-logs/azure-log-forwarding.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -115,16 +115,15 @@ In the following example, we will demonstrate how to forward the Activity Logs f

## Send logs from Azure Blob storage

[Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction) allows to store massive amounts of unstructured data, including log files. Using the [New Relic Blob Storage ARM template](https://github.com/newrelic/newrelic-azure-functions/blob/master/armTemplates/azuredeploy-blobforwarder.json), you will be able to create a [Storage Account with a single container](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction#blob-storage-resources). Any log files placed in the aforementioned container will be automatically forwarded to New Relic.
[Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction) allows to store massive amounts of unstructured data, including log files. Using the [New Relic Blob Storage ARM template](https://github.com/newrelic/newrelic-azure-functions/blob/master/armTemplates/azuredeploy-blobforwarder.json), you will be able to create a function that forwards the contents of a [container placed in a Storage Account](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction#blob-storage-resources).

<Callout variant="important">
New Relic Blob Storage ARM template deploys a function that forwards all the blob files within the specified container **at their current state**. If any of these blobs is modified thereafter, the **complete** contents of the file will be resent. The provided solution is aimed at forwarding static blob files to New Relic and it does not support file tailing. If you need to forward a stream of logs, we recommend to send your application logs to an `Event Hub` and use the [Event Hub based template](#azure-eventhub) instead.
</Callout>

To send the blobs from a container in your Storage Account, follow these steps:
1. [Deploy](#blobstorage-arm-setup) the New Relic Blob Storage ARM template.
2. Upload files to the newly created container.
3. [Explore your log data](#find-data).
2. [Explore your log data](#find-data).

### Deploy the New Relic Blob Storage ARM template [#blobstorage-arm-setup]

Expand All @@ -141,8 +140,8 @@ Follow these steps:
6. Click **Deploy to Azure** and a new tab will be open with the ARM template loaded in Azure.
7. Select the **Resource Group** where you want to create the necessary resources, and a **Region**. Despite not being mandatory, we recommend installing the template in a new resource group, to avoid deleting any of the components it creates accidentally.
8. In the **New Relic License Key** field, paste the previously copied **API Key**.
9. Ensure the [New Relic One endpoint](/docs/logs/log-api/introduction-log-api/#endpoint) is set to the one corresponding to your account.
10. Introduce the names for the storage account and the container that you wish to be created.
9. Introduce the names for the storage account and the container that you wish to forward.
10. Ensure the [New Relic One endpoint](/docs/logs/log-api/introduction-log-api/#endpoint) is set to the one corresponding to your account.
11. Click **Review + create**, review the data you've inserted, and click **Create**.

## View log data [#find-data]
Expand Down

0 comments on commit 3db3255

Please sign in to comment.