https://community.dynatrace.com/t5/Alerting/Azure-transaction-counts-for-blob-storage-comes-into-Dynatrace/m-p/299192#M6305 <P>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?</P> <P><BR />timeseries tx_count = sum(cloud.azure.microsoft_storage.storageaccounts.blobservices.transactions),<BR />by: { dt.entity.custom_device },<BR />interval: 1m,<BR />filter: { dt.entity.custom_device == "CUSTOM_DEVICE-xxx" }<BR />| fieldsAdd tx_rolling_60m = arrayMovingSum(tx_count, 60)<BR />| fieldsRemove tx_count</P> Mon, 11 May 2026 12:12:21 GMT rseibert1 2026-05-11T12:12:21Z https://community.dynatrace.com/t5/Alerting/Azure-transaction-counts-for-blob-storage-comes-into-Dynatrace/m-p/299192#M6305 <P>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?</P> <P><BR />timeseries tx_count = sum(cloud.azure.microsoft_storage.storageaccounts.blobservices.transactions),<BR />by: { dt.entity.custom_device },<BR />interval: 1m,<BR />filter: { dt.entity.custom_device == "CUSTOM_DEVICE-xxx" }<BR />| fieldsAdd tx_rolling_60m = arrayMovingSum(tx_count, 60)<BR />| fieldsRemove tx_count</P> Mon, 11 May 2026 12:12:21 GMT https://community.dynatrace.com/t5/Alerting/Azure-transaction-counts-for-blob-storage-comes-into-Dynatrace/m-p/299192#M6305 rseibert1 2026-05-11T12:12:21Z