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
