For your transaction issue make use of Azure Storage Analytics metrics (classic) | Microsoft Docs,This issues mainly because of many Duplicate records may exist for logs created in the same hour
Make sure you enable Azure Storage Analytics metrics, in your storage account use blob container $logs which you can proceed to more log entries and find information and $logs are not worked when List Containers operation is accomplished.
For example :
http://<accountname>.blob.core.windows.net/$logs.
You can try the below PowerShell cmdlet to filter the list of log blobs at specify time which you can done in your storage account container
Get-AzStorageBlob -Container '$logs' |
Where-Object {
$_.Name -match 'blob/2014/05/21/05' -and
$_.ICloudBlob.Metadata.LogType -match 'write'
} |
ForEach-Object {
"{0} {1} {2} {3}" –f $_.Name,
$_.ICloudBlob.Metadata.StartTime,
$_.ICloudBlob.Metadata.EndTime,
$_.ICloudBlob.Metadata.LogType
}
Otherwise, You can make use of azure application Insights it can automatically detect performance and resolve your diagnose issues io understand what actually required
For your information please refer below link which answered by sVathis & Gaurav Mantri :
How can I find the source of my Hot LRS Write Operations on Azure Storage Account?
Azure Storage Analytics logging | Microsoft Docs
And also may I know which category (Read, Iterative Read, All other operations) I should consider these transactions as in the Blob transactions pricing table
You can use azure Pricing calculator Pricing is depends on the region where the data is stored
please refer this offical documents for operations based on your requirement
