[AZINTS-3246] replace the old blob forwarder with the new one #28536
Conversation
Preview links (active after the
|
|
|
||
| ##### Add a new function to your Function App using the Azure Blob Storage trigger template | ||
| For each resource which you would like to [forward resource logs][304], when viewing the resource in the Azure portal, under **Monitoring**, select **Diagnostic settings**. Create a new diagnostic setting, select all the categories you would like to forward, and under **Destination details**, select **Archive to a storage account**, and enter the details of the storage account just created. |
There was a problem hiding this comment.
| For each resource which you would like to [forward resource logs][304], when viewing the resource in the Azure portal, under **Monitoring**, select **Diagnostic settings**. Create a new diagnostic setting, select all the categories you would like to forward, and under **Destination details**, select **Archive to a storage account**, and enter the details of the storage account just created. | |
| To [forward resource logs][304] for a resource, open the resource in the Azure portal. Under **Monitoring**, select **Diagnostic settings**. Create a new diagnostic setting, select the categories you want to forward, and under **Destination details**, select **Archive to a storage account**. Then enter the details of the storage account you just created. |
Co-authored-by: Esther Kim <esther.kim@datadoghq.com>
|
|
||
| Datadog recommends using the Event Hub setup for Azure log collection. However, you can also follow the steps in this section to forward all of your Azure App Services logs from Azure Blob Storage: | ||
| **Note**: Resources can only send logs to storage accounts in the same Azure region. |
There was a problem hiding this comment.
This note should be closer to the diagnostic settings setup
There was a problem hiding this comment.
I thought about that at first, but it matters when they are deploying, since otherwise a customer could deploy and then realize that it isnt in the correct region. Maybe it makes sense to add that info to the diagnostic setting section as well?
There was a problem hiding this comment.
Event Hub forwarder has this same restriction. In the docs, this is at the end of the deployment section immediately before discussing adding diagnostic settings. Maybe just moving lower so it is still near deployment but also near diagnostic settings.
There was a problem hiding this comment.
Could also just swap the places of the two notes
|
Caution DO NOT MERGE We're holding off on merging these changes until we have a good idea of what the whole azure logging docs page should look like. |
What does this PR do? What is the motivation?
We've created a v2 of the Blob Storage-based log forwarder, which is strictly better than the old one. This PR updates the docs to point to that one, and improves the installation instructions.
Merge instructions
Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes