We just tested the Azure Storage Analytics service, and something very unusual caught our attention.
The transaction account for the diagnostic account (the account for which the Diagnostic Service records data) was extremely high. We are talking about 600 ~ transactions per hour , all of which are GetBlob () operations, and they all end in error (ClientOtherError is equal to the total number of operations). Further research showed that each instance in which Diagnostics is enabled produces 300 ~ transactions per hour (we have 2 instances, thus 600). Continuing the investigation, looking at the $ logs that the Analytics Service produces, shows what is actually happening:
The log is populated with many calls to an XML file that does not exist. The log file itself is very cluttered, but it is very clear that most calls are looking for
https: // **** .blob.core.windows.net /mam/MACommand.xml , as well as /mam/MACommanda.xml and /mam/MACommandb.xml
all of these calls have a 404 error.
This problem is a real problem for us, and we do not know what causes it.
Has anyone encountered this issue?
(edit: Forgot to mention, the diagnostic service does not write anything - scheduleTransferPeriod is zero for all categories)
source share