Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] 1 hour lag on Azure storage metric (UsedCapacity) #483

Open
haedri opened this issue Jul 31, 2023 · 0 comments
Open

[BUG] 1 hour lag on Azure storage metric (UsedCapacity) #483

haedri opened this issue Jul 31, 2023 · 0 comments
Labels
bug Something isn't working detectors About nex or existing detectors

Comments

@haedri
Copy link
Contributor

haedri commented Jul 31, 2023

What is the module?
azure-storage-account

What is the detector?
Azure Storage Account count
Azure Storage Account capacity

Describe the bug
There's a one hour lag on UsedCapacity because the metric is sent late by Azure according to Splunk support :

These metrics look to be published hourly by Azure, which explains the hourly lag. Azure Blob Storage monitoring data reference - Azure Storage

So the detector can not trigger (max delay is 15 minutes)
Support says we should use timeshift method to add a one hour timeshift, and this seems to fix the problem indeed

@haedri haedri added bug Something isn't working detectors About nex or existing detectors labels Jul 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working detectors About nex or existing detectors
Projects
None yet
Development

No branches or pull requests

1 participant