Skip to content

Commit a8820e1

Browse files
committed
Adding a line to the monitoring scenario doc
1 parent 6867f6c commit a8820e1

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/storage/blobs/blob-storage-monitoring-scenarios.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -174,6 +174,8 @@ Then, you can pass that string to the [Get-FileHash](/powershell/module/microsof
174174

175175
Alternatively, you can pass the decoded string to the [hash_sha256()](/azure/data-explorer/kusto/query/sha256hashfunction) function as part of a query when you use Azure Data Explorer.
176176

177+
SAS tokens do not contain identity information. One way to track the activities of users or organizations, is to keep a mapping of users or organizations to various SAS token hashes.
178+
177179
## Optimize cost for infrequent queries
178180

179181
You can export logs to Log Analytics for rich native query capabilities. When you have massive transactions on your storage account, the cost of using logs with Log Analytics might be high. For more information, see [Azure Log Analytics Pricing](https://azure.microsoft.com/pricing/details/monitor/). If you only plan to query logs occasionally (for example, query logs for compliance auditing), you can consider reducing the total cost by exporting logs to storage account, and then using a serverless query solution on top of log data, for example, Azure Synapse.

0 commit comments

Comments
 (0)