Repository: DataDog/documentation
Pull request #27856: Docs10170/azure automated logs architecture
Author: login: buraizu
Labels: name: Images
description: Images are added/removed with this PR
name: Guide
description: Content impacting a guide
name: mergequeue-status: done
Created: 2025-02-26T23:38:16Z | Merged: 2025-03-26T20:13:56Z

<!-- *Note: Please remember to review the Datadog Documentation [Contribution Guidelines](https://github.com/DataDog/documentation/blob/master/CONTRIBUTING.md) if you have not yet done so.* -->

### What does this PR do? What is the motivation?
Add an Azure logs architecture and configuration guide.

### Merge instructions

<!-- 
If you're waiting for a release or there are other considerations that you want us to be aware of, list them here. 
If the PR is ready to be merged once it receives the required reviews, check the box below after you've created the PR.
-->

Merge readiness:
- [ ] Ready for merge

Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the `<yourname>/description` naming convention) and then add the following PR comment:

```
/merge
```

### Additional notes
<!-- Anything else we should know when reviewing?-->

<!-- Previewing the PR: Assuming you are a Datadog employee and named your branch `<yourname>/<description>`, a preview build will run and links to the preview output will be auto-generated and posted in the PR comments. The links will 404 until the preview build is finished running. -->



Diff:
diff --git a/content/en/logs/guide/azure-automated-logs-architecture.md b/content/en/logs/guide/azure-automated-logs-architecture.md
new file mode 100644
index 00000000000..50c77439ae8
--- /dev/null
+++ b/content/en/logs/guide/azure-automated-logs-architecture.md
@@ -0,0 +1,106 @@
+---
+title: Azure Automated Log Forwarding Architecture and Configuration
+description: "Guide to architecture and configuration of the Datadog Azure integration automated log forwarding setup"
+private: true
+further_reading:
+- link: "https://docs.datadoghq.com/integrations/azure/"
+  tag: "Documentation"
+  text: "Azure Integration"
+---
+
+## Overview
+
+Datadog's automated log forwarding setup for the Azure integration offers several benefits over other setup methods:
+
+- **Simplified setup** of the required Azure infrastructure across all of your subscriptions and regions, allowing you to start forwarding logs from across your Azure environment in minutes. New resources added to your environment in the future are automatically set up to forward logs to Datadog.
+
+- **Automatic scaling** to match the volume of logs in your Azure environment. New log forwarders are spun up as needed to meet the demand, and are automatically removed as demand subsides.
+
+- **Reduced Azure costs** by using more cost-effective Azure services, and by scaling down in periods of low volume. 
+
+This log forwarding method is available to all [Datadog sites][5] and most Azure regions (any region that supports Container Apps). Datadog recommends this method to set up log forwarding from your Azure environment.
+
+### Supported logs
+
+This setup supports forwarding of any logs available through diagnostic settings, including activity logs and resource logs. For non-platform logs, Datadog recommends using the [Datadog Agent][6] to forward logs.
+
+## Architecture
+
+### Services used
+
+1. [Azure Function][7] apps are used to discover resources in your Azure subscriptions, scale log forwarders, and configure diagnostic settings on the detected resources. 
+2. [Azure Container Apps][8] are used to collect resource logs generated by diagnostic settings, track which logs have been processed already, and submit them to Datadog.
+3. [Azure Storage Accounts][9] are used to store logs generated by your resources, as well as a small cache of metadata such as subscription IDs, resource IDs, and regions.
+
+### High-level architecture
+
+{{<img src="/logs/guide/azure_automated_logs_architecture/high_level_architecture.png" alt="A high-level representation of the automated log forwarding setup" style="width:100%">}}
+
+The deployment template sets up a [control plane](#control-plane) and [log forwarders](#log-forwarders) in your selected subscriptions.
+
+#### Control plane 
+
+The control plane is a set of Azure Function apps and a storage account for caching. One control plane is deployed in your chosen subscription and performs the following tasks:
+- Discovery of resources in your chosen subscriptions that are able to log through diagnostic settings.
+- Automatic configuration of diagnostic settings on discovered resources to flow logs into a storage account that the log forwarders are tracking.
+- Scaling of log forwarders in regions where your resources are located, enabling them to match log volume dynamically.
+
+#### Log forwarders 
+
+Log forwarders consist of an Azure Container Apps job and storage account for logs. They are deployed by the control plane in each subscription you select for log forwarding. The number of log forwarders deployed per subscription scales according to the volume of logs generated by your resources. Log forwarders perform the following tasks:
+- Temporarily store logs generated from your resources' diagnostic settings in a storage account.
+- Process the stored logs and forward them to Datadog. 
+	
+In Azure, a resource's diagnostic settings can only target storage accounts within the same region. As such, the forwarders are spun up in each region where resources with diagnostic settings exist.
+
+See Azure's [Diagnostic settings in Azure Monitor][13] page for more information.
+
+### Detailed architecture
+
+{{<img src="/logs/guide/azure_automated_logs_architecture/detailed_architecture.png" alt="A detailed representation of the automated log forwarding setup" style="width:100%">}}
+
+## Setup
+
+Setup is completed through an [Azure Resource Manager][1] (ARM) template. This allows you to update configuration options such as the API Key, Datadog Site, or monitored subscriptions through redeployments with the same template.
+
+Upon accessing the ARM template, you select the management group, region, and subscriptions where you would like to automate log forwarding. The template then deploys a control plane, which in turn deploys log forwarders in each of the subscriptions you selected.
+
+See the [Azure Automated Log Forwarding Setup guide][2] for a step-by-step walkthrough of deploying the [ARM template][3] through the Azure Portal.
+
+## Security and permissions
+
+The ARM template grants the control plane only the permissions needed to manage the forwarders and place diagnostic settings on your resources. To achieve this, resource groups are created and permissions are granted during the ARM template deployment. After this, you can add permissions for more subscriptions by redeploying the ARM template.
+
+### Permissions used
+
+- [Monitoring Contributor][10] role at the **subscription** level for the selected subscriptions.
+   - This is needed to discover resources with available diagnostic settings and enable log output to storage.
+
+- [Contributor][11] role at the **resource group** level, for the log-forwarding resource groups in the selected subscriptions.
+   - This is needed to manage (create and delete) forwarder storage accounts and Container Apps jobs.
+   
+- [Website Contributor][12] role at the **control plane resource group** level, for updating the control plane function apps.
+
+No information about your resources is exported. Datadog only requests the information required to enable log output, and the only output of this architecture is the logs sent to Datadog.
+
+**Note**: Optionally, you can generate metrics, logs, and events about the health of the control plane and send them to Datadog for debugging purposes. This is enabled through a feature flag.
+
+## Help and feedback
+
+To get help or provide feedback, email [azure-log-forwarding@datadoghq.com][4].
+
+{{< partial name="whats-next/whats-next.html" >}}
+
+[1]: https://learn.microsoft.com/azure/azure-resource-manager/management/overview
+[2]: /logs/guide/azure-automated-log-forwarding/
+[3]: https://portal.azure.com/#create/Microsoft.Template/uri/CustomDeploymentBlade/uri/https%3A%2F%2Fddazurelfo.blob.core.windows.net%2Ftemplates%2Fazuredeploy.json/createUIDefinitionUri/https%3A%2F%2Fddazurelfo.blob.core.windows.net%2Ftemplates%2FcreateUiDefinition.json
+[4]: mailto:azure-log-forwarding@datadoghq.com
+[5]: /getting_started/site/
+[6]: /agent/logs/
+[7]: https://learn.microsoft.com/azure/azure-functions/
+[8]: https://azure.microsoft.com/products/container-apps
+[9]: https://learn.microsoft.com/azure/storage/common/storage-account-overview
+[10]: https://learn.microsoft.com/azure/azure-monitor/roles-permissions-security#monitoring-contributor
+[11]: https://learn.microsoft.com/azure/role-based-access-control/built-in-roles/privileged#contributor
+[12]: https://learn.microsoft.com/azure/role-based-access-control/built-in-roles/web-and-mobile#website-contributor
+[13]: https://learn.microsoft.com/azure/azure-monitor/essentials/diagnostic-settings
diff --git a/static/images/logs/guide/azure_automated_logs_architecture/detailed_architecture.png b/static/images/logs/guide/azure_automated_logs_architecture/detailed_architecture.png
new file mode 100644
index 00000000000..07472460179
Binary files /dev/null and b/static/images/logs/guide/azure_automated_logs_architecture/detailed_architecture.png differ
diff --git a/static/images/logs/guide/azure_automated_logs_architecture/high_level_architecture.png b/static/images/logs/guide/azure_automated_logs_architecture/high_level_architecture.png
new file mode 100644
index 00000000000..6a43e1c1750
Binary files /dev/null and b/static/images/logs/guide/azure_automated_logs_architecture/high_level_architecture.png differ


Reviews:
user: login: jhgilbert
body: Approved with very minor suggestions, thanks!
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-03-06T19:28:30Z

Review comments:
diff_hunk: @@ -0,0 +1,103 @@
+---
+title: Azure Automated Log Forwarding Architecture and Configuration
+description: "Guide to architecture and configuration of the Datadog Azure integration automated log forwarding setup"
+private: true
+further_reading:
+- link: "https://docs.datadoghq.com/integrations/azure/"
+  tag: "Documentation"
+  text: "Azure Integration"
+---
+
+## Overview
+
+Datadog's automated log forwarding setup for the Azure integration offers several benefits over other setup methods:
+
+- **Simplified setup** of the required Azure infrastructure across all of your subscriptions and regions, allowing you to start forwarding logs from across your Azure environment in minutes. New resources added to your environment in the future are automatically set up to forward logs to Datadog.
+
+- **Automatic scaling** to match the volume of logs in your Azure environment. New log forwarders are spun up as needed to meet the demand, and are automatically removed as demand subsides.
+
+- **Reduced Azure costs** by utilizing more cost-effective Azure services, and by scaling down in periods of low volume. 
path: content/en/logs/guide/azure-automated-logs-architecture.md
user: login: jhgilbert
body: ```suggestion
- **Reduced Azure costs** by using more cost-effective Azure services, and by scaling down in periods of low volume. 
```
created_at: 2025-03-06T19:23:05Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,103 @@
+---
+title: Azure Automated Log Forwarding Architecture and Configuration
+description: "Guide to architecture and configuration of the Datadog Azure integration automated log forwarding setup"
+private: true
+further_reading:
+- link: "https://docs.datadoghq.com/integrations/azure/"
+  tag: "Documentation"
+  text: "Azure Integration"
+---
+
+## Overview
+
+Datadog's automated log forwarding setup for the Azure integration offers several benefits over other setup methods:
+
+- **Simplified setup** of the required Azure infrastructure across all of your subscriptions and regions, allowing you to start forwarding logs from across your Azure environment in minutes. New resources added to your environment in the future are automatically set up to forward logs to Datadog.
+
+- **Automatic scaling** to match the volume of logs in your Azure environment. New log forwarders are spun up as needed to meet the demand, and are automatically removed as demand subsides.
+
+- **Reduced Azure costs** by utilizing more cost-effective Azure services, and by scaling down in periods of low volume. 
+
+This log forwarding method is available to all [Datadog sites][5] and most Azure regions (any region that supports Container Apps). Datadog recommends this method to set up log forwarding from your Azure environment.
+
+### Supported logs
+
+This setup supports forwarding of any logs available through diagnostic settings, including activity logs and resource logs. For non-platform logs, Datadog recommends using the [Datadog Agent][6] to forward logs.
+
+## Architecture
+
+### Services used
+
+1. [Azure Function][7] apps are used to discover resources in your Azure subscriptions, scale log forwarders, and configure diagnostic settings on the detected resources. 
+2. [Azure Container Apps][8] are used to collect resource logs generated by diagnostic settings, track which logs have been processed already, and submit them to Datadog.
+3. [Azure Storage Accounts][9] are used to store logs generated by your resources, as well as a small cache of metadata such as subscription IDs, resource IDs, and regions.
+
+### High level architecture
path: content/en/logs/guide/azure-automated-logs-architecture.md
user: login: jhgilbert
body: ```suggestion
### High-level architecture
```
created_at: 2025-03-06T19:24:20Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,103 @@
+---
+title: Azure Automated Log Forwarding Architecture and Configuration
+description: "Guide to architecture and configuration of the Datadog Azure integration automated log forwarding setup"
+private: true
+further_reading:
+- link: "https://docs.datadoghq.com/integrations/azure/"
+  tag: "Documentation"
+  text: "Azure Integration"
+---
+
+## Overview
+
+Datadog's automated log forwarding setup for the Azure integration offers several benefits over other setup methods:
+
+- **Simplified setup** of the required Azure infrastructure across all of your subscriptions and regions, allowing you to start forwarding logs from across your Azure environment in minutes. New resources added to your environment in the future are automatically set up to forward logs to Datadog.
+
+- **Automatic scaling** to match the volume of logs in your Azure environment. New log forwarders are spun up as needed to meet the demand, and are automatically removed as demand subsides.
+
+- **Reduced Azure costs** by utilizing more cost-effective Azure services, and by scaling down in periods of low volume. 
+
+This log forwarding method is available to all [Datadog sites][5] and most Azure regions (any region that supports Container Apps). Datadog recommends this method to set up log forwarding from your Azure environment.
+
+### Supported logs
+
+This setup supports forwarding of any logs available through diagnostic settings, including activity logs and resource logs. For non-platform logs, Datadog recommends using the [Datadog Agent][6] to forward logs.
+
+## Architecture
+
+### Services used
+
+1. [Azure Function][7] apps are used to discover resources in your Azure subscriptions, scale log forwarders, and configure diagnostic settings on the detected resources. 
+2. [Azure Container Apps][8] are used to collect resource logs generated by diagnostic settings, track which logs have been processed already, and submit them to Datadog.
+3. [Azure Storage Accounts][9] are used to store logs generated by your resources, as well as a small cache of metadata such as subscription IDs, resource IDs, and regions.
+
+### High level architecture
+
+{{<img src="/logs/guide/azure_automated_logs_architecture/high_level_architecture.png" alt="A high-level representation of the automated log forwarding setup" style="width:100%">}}
+
+The deployment template sets up a [control plane](#control-plane) and [log forwarders](#log-forwarders) in your selected subscriptions.
+
+#### Control plane 
+
+The control plane is a set of Azure Function apps and storage account for caching. One control plane is deployed in your chosen subscription and performs the following tasks:
path: content/en/logs/guide/azure-automated-logs-architecture.md
user: login: jhgilbert
body: ```suggestion
The control plane is a set of Azure Function apps and a storage account for caching. One control plane is deployed in your chosen subscription and performs the following tasks:
```
created_at: 2025-03-06T19:24:35Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,103 @@
+---
+title: Azure Automated Log Forwarding Architecture and Configuration
+description: "Guide to architecture and configuration of the Datadog Azure integration automated log forwarding setup"
+private: true
+further_reading:
+- link: "https://docs.datadoghq.com/integrations/azure/"
+  tag: "Documentation"
+  text: "Azure Integration"
+---
+
+## Overview
+
+Datadog's automated log forwarding setup for the Azure integration offers several benefits over other setup methods:
+
+- **Simplified setup** of the required Azure infrastructure across all of your subscriptions and regions, allowing you to start forwarding logs from across your Azure environment in minutes. New resources added to your environment in the future are automatically set up to forward logs to Datadog.
+
+- **Automatic scaling** to match the volume of logs in your Azure environment. New log forwarders are spun up as needed to meet the demand, and are automatically removed as demand subsides.
+
+- **Reduced Azure costs** by utilizing more cost-effective Azure services, and by scaling down in periods of low volume. 
+
+This log forwarding method is available to all [Datadog sites][5] and most Azure regions (any region that supports Container Apps). Datadog recommends this method to set up log forwarding from your Azure environment.
+
+### Supported logs
+
+This setup supports forwarding of any logs available through diagnostic settings, including activity logs and resource logs. For non-platform logs, Datadog recommends using the [Datadog Agent][6] to forward logs.
+
+## Architecture
+
+### Services used
+
+1. [Azure Function][7] apps are used to discover resources in your Azure subscriptions, scale log forwarders, and configure diagnostic settings on the detected resources. 
+2. [Azure Container Apps][8] are used to collect resource logs generated by diagnostic settings, track which logs have been processed already, and submit them to Datadog.
+3. [Azure Storage Accounts][9] are used to store logs generated by your resources, as well as a small cache of metadata such as subscription IDs, resource IDs, and regions.
+
+### High level architecture
+
+{{<img src="/logs/guide/azure_automated_logs_architecture/high_level_architecture.png" alt="A high-level representation of the automated log forwarding setup" style="width:100%">}}
+
+The deployment template sets up a [control plane](#control-plane) and [log forwarders](#log-forwarders) in your selected subscriptions.
+
+#### Control plane 
+
+The control plane is a set of Azure Function apps and storage account for caching. One control plane is deployed in your chosen subscription and performs the following tasks:
+- Discovery of resources in your chosen subscriptions that are able to log through diagnostic settings.
+- Automatic configuration of diagnostic settings on discovered resources to flow logs into a storage account that the log forwarders are tracking.
+- Scaling of log forwarders in regions where your resources are located, enabling them to match log volume dynamically.
+
+#### Log forwarders 
+
+Log forwarders consist of an Azure Container Apps job and storage account for logs. They are deployed by the control plane in each subscription you select for log forwarding. The number of log forwarders deployed per subscription scales according to the volume of logs generated by your resources. Log forwarders perform the following tasks:
+- Temporarily store logs generated from your resources' diagnostic settings in a storage account.
+- Process the stored logs and forward them to Datadog. 
+	
+In Azure, a resource's diagnostic settings can only target storage accounts within the same region. As such, the forwarders are spun up in each region where resources with diagnostic settings exist.
+
+### Detailed architecture
+
+{{<img src="/logs/guide/azure_automated_logs_architecture/detailed_architecture.png" alt="A detailed representation of the automated log forwarding setup" style="width:100%">}}
+
+## Setup
+
+Setup is completed through an [Azure Resource Manager][1] (ARM) template. This allows you to update configuration options such as the API Key, Datadog Site, or monitored subscriptions through redeployments with the same template.
+
+Upon accessing the ARM template, you select the management group, region, and subscriptions where you would like to automate log forwarding. The template then deploys a control plane, which in turn deploys log forwarders in each of the subscriptions you selected.
+
+See the [Azure Automated Log Forwarding Setup guide][2] for a step by step walkthrough of deploying the [ARM template][3] through the Azure Portal.
path: content/en/logs/guide/azure-automated-logs-architecture.md
user: login: jhgilbert
body: ```suggestion
See the [Azure Automated Log Forwarding Setup guide][2] for a step-by-step walkthrough of deploying the [ARM template][3] through the Azure Portal.
```
created_at: 2025-03-06T19:26:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,103 @@
+---
+title: Azure Automated Log Forwarding Architecture and Configuration
+description: "Guide to architecture and configuration of the Datadog Azure integration automated log forwarding setup"
+private: true
+further_reading:
+- link: "https://docs.datadoghq.com/integrations/azure/"
+  tag: "Documentation"
+  text: "Azure Integration"
+---
+
+## Overview
+
+Datadog's automated log forwarding setup for the Azure integration offers several benefits over other setup methods:
+
+- **Simplified setup** of the required Azure infrastructure across all of your subscriptions and regions, allowing you to start forwarding logs from across your Azure environment in minutes. New resources added to your environment in the future are automatically set up to forward logs to Datadog.
+
+- **Automatic scaling** to match the volume of logs in your Azure environment. New log forwarders are spun up as needed to meet the demand, and are automatically removed as demand subsides.
+
+- **Reduced Azure costs** by utilizing more cost-effective Azure services, and by scaling down in periods of low volume. 
+
+This log forwarding method is available to all [Datadog sites][5] and most Azure regions (any region that supports Container Apps). Datadog recommends this method to set up log forwarding from your Azure environment.
+
+### Supported logs
+
+This setup supports forwarding of any logs available through diagnostic settings, including activity logs and resource logs. For non-platform logs, Datadog recommends using the [Datadog Agent][6] to forward logs.
+
+## Architecture
+
+### Services used
+
+1. [Azure Function][7] apps are used to discover resources in your Azure subscriptions, scale log forwarders, and configure diagnostic settings on the detected resources. 
+2. [Azure Container Apps][8] are used to collect resource logs generated by diagnostic settings, track which logs have been processed already, and submit them to Datadog.
+3. [Azure Storage Accounts][9] are used to store logs generated by your resources, as well as a small cache of metadata such as subscription IDs, resource IDs, and regions.
+
+### High level architecture
+
+{{<img src="/logs/guide/azure_automated_logs_architecture/high_level_architecture.png" alt="A high-level representation of the automated log forwarding setup" style="width:100%">}}
+
+The deployment template sets up a [control plane](#control-plane) and [log forwarders](#log-forwarders) in your selected subscriptions.
+
+#### Control plane 
+
+The control plane is a set of Azure Function apps and storage account for caching. One control plane is deployed in your chosen subscription and performs the following tasks:
+- Discovery of resources in your chosen subscriptions that are able to log through diagnostic settings.
+- Automatic configuration of diagnostic settings on discovered resources to flow logs into a storage account that the log forwarders are tracking.
+- Scaling of log forwarders in regions where your resources are located, enabling them to match log volume dynamically.
+
+#### Log forwarders 
+
+Log forwarders consist of an Azure Container Apps job and storage account for logs. They are deployed by the control plane in each subscription you select for log forwarding. The number of log forwarders deployed per subscription scales according to the volume of logs generated by your resources. Log forwarders perform the following tasks:
+- Temporarily store logs generated from your resources' diagnostic settings in a storage account.
+- Process the stored logs and forward them to Datadog. 
+	
+In Azure, a resource's diagnostic settings can only target storage accounts within the same region. As such, the forwarders are spun up in each region where resources with diagnostic settings exist.
+
+### Detailed architecture
+
+{{<img src="/logs/guide/azure_automated_logs_architecture/detailed_architecture.png" alt="A detailed representation of the automated log forwarding setup" style="width:100%">}}
+
+## Setup
+
+Setup is completed through an [Azure Resource Manager][1] (ARM) template. This allows you to update configuration options such as the API Key, Datadog Site, or monitored subscriptions through redeployments with the same template.
+
+Upon accessing the ARM template, you select the management group, region, and subscriptions where you would like to automate log forwarding. The template then deploys a control plane, which in turn deploys log forwarders in each of the subscriptions you selected.
+
+See the [Azure Automated Log Forwarding Setup guide][2] for a step by step walkthrough of deploying the [ARM template][3] through the Azure Portal.
+
+## Security and permissions
+
+The ARM template grants the control plane only the permissions needed to manage the forwarders and place diagnostic settings on your resources. To achieve this, resource groups are created and permissions are granted during the ARM template deployment. After this, you can add permissions for more subscriptions by redeploying the ARM template.
+
+### Permissions used
+
+- [Monitoring Contributor][10] role at the **subscription** level for the selected subscriptions.
+   - This is needed to discover resources with available diagnostic settings and enable log output to storage.
+
+- [Contributor][11] role at the **resource group** level, for the log-forwarding resource groups in the selected subscriptions.
+   - This is needed to manage (create and delete) forwarder storage accounts and Container Apps jobs.
+   
+- [Website Contributor][12] role at the **control plane resource group** level, for updating the control plane function apps.
+
+No information about your resources is exported. Datadog only requests the information required to enable log output, and the only output of this architecture is the logs sent to Datadog.
+
+**Note**: Optionally, you can generate metrics, logs, and events about the health of the control plane and send them to Datadog for debugging purposes. This is enabled through a feature flag.
+
+## Help and feedback
+
+To get help or provide feedback, email [azure-log-forwarding@datadoghq.com][4] 
path: content/en/logs/guide/azure-automated-logs-architecture.md
user: login: jhgilbert
body: ```suggestion
To get help or provide feedback, email [azure-log-forwarding@datadoghq.com][4].
```
created_at: 2025-03-06T19:27:48Z
author_association: CONTRIBUTOR

PR comments:
user: login: github-actions[bot]
created_at: 2025-02-26T23:41:38Z
body: ## Preview links (active after the `build_preview` check completes)

### New or renamed files
* https://docs-staging.datadoghq.com/docs10170/azure-automated-logs-architecture/logs/guide/azure-automated-logs-architecture
author_association: CONTRIBUTOR
user: login: buraizu
created_at: 2025-03-26T19:54:50Z
body: /merge
author_association: CONTRIBUTOR
user: login: dd-devflow[bot]
created_at: 2025-03-26T19:54:53Z
body: <!-- "FeedbackWorkflowId":"f2694583-77d2-415f-bc5f-e819f5868809_36" -->
[View all feedbacks in Devflow UI.](https://devflow.static-app.us1.prod.dog/logs/f2694583-77d2-415f-bc5f-e819f5868809_36)
`2025-03-26 19:54:53 UTC` :information_source: Start processing command `/merge`

---
`2025-03-26 19:55:00 UTC` :information_source: **MergeQueue:** pull request added to the queue

The expected merge time in `master` is approximately 15m (p90).

---
`2025-03-26 20:14:01 UTC` :information_source: **MergeQueue:** This merge request was merged

author_association: NONE