# Azure transaction counts for blob storage comes into Dynatrace in bursts sometimes nothing for up to 70min

**URL:** <https://community.dynatrace.com/t/azure-transaction-counts-for-blob-storage-comes-into-dynatrace-in-bursts-sometimes-nothing-for-up-to-70min/55844>\
**Category:** Alerting\
**Tags:** azure, anomaly-detection\
**Created:** [May 8, 2026, 10:41am UTC](https://community.dynatrace.com/t/azure-transaction-counts-for-blob-storage-comes-into-dynatrace-in-bursts-sometimes-nothing-for-up-to-70min/55844 "2026-05-08T10:41:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rseibert1](https://avatars.discourse-cdn.com/v4/letter/r/c4cdca/32.png) [@rseibert1](https://community.dynatrace.com/u/rseibert1)\
**Post date:** [May 8, 2026, 10:41am UTC](https://community.dynatrace.com/t/azure-transaction-counts-for-blob-storage-comes-into-dynatrace-in-bursts-sometimes-nothing-for-up-to-70min/55844/1 "2026-05-08T10:41:24Z")

</div>

Setting up anomaly detection for this metric is becoming problematic. I have tried using arrayMovingSum but issue is it looks good on the notebook but still alerts. Maybe there is a setting I am missing? I have set the sliding window to 60 and require 59 violations. I think if Dynatrace allowed a larger moving window I could fix this. How do others deal with the batch nature of cloud metrics?

timeseries tx\_count = sum(cloud.azure.microsoft\_storage.storageaccounts.blobservices.transactions),  
by: { dt.entity.custom\_device },  
interval: 1m,  
filter: { dt.entity.custom\_device == “CUSTOM\_DEVICE-xxx” }  
| fieldsAdd tx\_rolling\_60m = arrayMovingSum(tx\_count, 60)  
| fieldsRemove tx\_count