You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/storage/blobs/blob-inventory.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -380,7 +380,7 @@ Each inventory run for a rule generates the following files:
380
380
381
381
## Pricing and billing
382
382
383
-
Pricing for inventory is based on the number of blobs and containers that are scanned during the billing period. The [Azure Blob Storage pricing](https://azure.microsoft.com/pricing/details/storage/blobs/) page shows the price per one million objects scanned. For example, if the price to scan one million objects is $0.003, your account contains three million objects, and you produce four reports in a month, then your bill would be 4 * 3 * $0.003 = $0.036.
383
+
Pricing for inventory is based on the number of blobs and containers that are scanned during the billing period. The [Azure Blob Storage pricing](https://azure.microsoft.com/pricing/details/storage/blobs/) page shows the price per one million objects scanned. For example, if the price to scan one million objects is `$0.003`, your account contains three million objects, and you produce four reports in a month, then your bill would be `4 * 3 * $0.003 = $0.036`.
384
384
385
385
After inventory files are created, additional standard data storage and operations charges will be incurred for storing, reading, and writing the inventory-generated files in the account.
386
386
@@ -426,3 +426,4 @@ An object replication policy can prevent an inventory job from writing inventory
426
426
-[Calculate the count and total size of blobs per container](calculate-blob-count-size.md)
Copy file name to clipboardExpand all lines: articles/storage/blobs/storage-blob-faq.yml
+47-39Lines changed: 47 additions & 39 deletions
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ sections:
21
21
- question: |
22
22
If I update an existing policy, how long does it take for the actions to run?
23
23
answer: |
24
-
The updated policy takes up to 24 hours to go into effect. Once the policy is in effect, the time that it takes for the actions to run varies depending on size of the storage account and operations that are performed. If the update is to disable or delete a rule, and enableAutoTierToHotFromCool was used, then auto-tiering to the hot tier will still happen. For example, set a rule including enableAutoTierToHotFromCool based on last access. If the rule is disabled or deleted, and a blob is currently in the cool or cold tier and then accessed, it will move back to the hot tier as that is applied on access outside of lifecycle management. The blob won't then move from hot to cool or cold given the the lifecycle management rule is disabled or deleted. The only way to prevent autoTierToHotFromCool is to turn off last access time tracking.
24
+
The updated policy takes up to 24 hours to go into effect. Once the policy is in effect, the time that it takes for the actions to run varies depending on size of the storage account and operations that are performed. If the update is to disable or delete a rule, and enableAutoTierToHotFromCool was used, then auto-tiering to the hot tier will still happen. For example, set a rule including enableAutoTierToHotFromCool based on last access. If the rule is disabled or deleted, and a blob is currently in the cool or cold tier and then accessed, it will move back to the hot tier as that is applied on access outside of lifecycle management. The blob won't then move from hot to cool or cold given the lifecycle management rule is disabled or deleted. The only way to prevent autoTierToHotFromCool is to turn off last access time tracking.
25
25
- question: |
26
26
The run completes but doesn't move or delete some blobs
27
27
answer: |
@@ -55,48 +55,58 @@ sections:
55
55
Is there a way to identify the time at which the policy will be executing?
56
56
answer: |
57
57
Unfortunately, there's no way to track the time at which the policy will be executing, as it's a background scheduling process. However, the platform will run the policy once per day.
58
-
- name: Multiple inventory file output
58
+
- name: Azure Storage blob inventory
59
59
questions:
60
60
- question: |
61
-
What has changed with respect to the number of inventory files produced?
62
-
answer: |
63
-
Blob Inventory report produces three types of files. See [Inventory files](blob-inventory.md#inventory-files). Existing customers using blob inventory might see a change in the number of inventory files, from one file to multiple files. Today, we already have manifest file that provides the list of files. This behavior remains unchanged, so these files are listed in the manifest file.
64
-
- question: |
65
-
Why was the change made?
66
-
answer: |
67
-
The change was implemented to enhance blob inventory performance, particularly for large storage accounts containing over five million objects. Now, results are written in parallel to multiple files, eliminating the bottleneck of using a single inventory file. This change was prompted by customer feedback, as they reported difficulties in opening and working with the excessively large single inventory file.
68
-
- question: |
69
-
How does this change affect me as a user?
61
+
I created a new inventory rule. Will it run at the same time every day?
70
62
answer: |
71
-
As a user, this change has a positive impact on your experience with blob inventory runs. It's expected to enhance performance and reduce the overall running time. However, to fully benefit from this improvement, you must ensure that your code is updated to process multiple results files instead of just one. This adjustment aligns your code with the new approach and optimizes the handling of inventory data.
63
+
The daily inventory rule is designed to run once every day. Additionally, there is a weekly inventory rule scheduled for every Sunday.
72
64
- question: |
73
-
Is my existing data affected?
65
+
Can I expect the rules to run at a fixed time?
74
66
answer: |
75
-
No, existing data isn't affected. Only new blob inventory results have multiple inventory files.
76
-
- question: |
77
-
Will there be any downtime or service interruptions?
78
-
answer: |
79
-
No, the change happens seamlessly.
80
-
- question: |
81
-
Is there anything I need to do differently now?
82
-
answer: |
83
-
Your required actions depend on how you currently process blob inventory results:
67
+
While we strive to provide a consistent experience, we can't guarantee the exact execution time for each run. The inventory rule's execution time might vary. For example, if today's policy is scheduled for 12:05 am, it might kick in at 12:07 am, 12:15 am, or any other time on the following day.
68
+
- name: Multiple inventory file output
69
+
questions:
70
+
- question: |
71
+
What has changed with respect to the number of inventory files produced?
72
+
answer: |
73
+
Blob Inventory report produces three types of files. See [Inventory files](blob-inventory.md#inventory-files). Existing customers using blob inventory might see a change in the number of inventory files, from one file to multiple files. Today, we already have manifest file that provides the list of files. This behavior remains unchanged, so these files are listed in the manifest file.
74
+
- question: |
75
+
Why was the change made?
76
+
answer: |
77
+
The change was implemented to enhance blob inventory performance, particularly for large storage accounts containing over five million objects. Now, results are written in parallel to multiple files, eliminating the bottleneck of using a single inventory file. This change was prompted by customer feedback, as they reported difficulties in opening and working with the excessively large single inventory file.
78
+
- question: |
79
+
How does this change affect me as a user?
80
+
answer: |
81
+
As a user, this change has a positive impact on your experience with blob inventory runs. It's expected to enhance performance and reduce the overall running time. However, to fully benefit from this improvement, you must ensure that your code is updated to process multiple results files instead of just one. This adjustment aligns your code with the new approach and optimizes the handling of inventory data.
82
+
- question: |
83
+
Is my existing data affected?
84
+
answer: |
85
+
No, existing data isn't affected. Only new blob inventory results have multiple inventory files.
86
+
- question: |
87
+
Will there be any downtime or service interruptions?
88
+
answer: |
89
+
No, the change happens seamlessly.
90
+
- question: |
91
+
Is there anything I need to do differently now?
92
+
answer: |
93
+
Your required actions depend on how you currently process blob inventory results:
84
94
85
-
- If your current processing assumes a single inventory results file, then you need to modify your code to accommodate multiple inventory results files.
95
+
- If your current processing assumes a single inventory results file, then you need to modify your code to accommodate multiple inventory results files.
86
96
87
-
- However, if your current processing involves reading the list of results files from the manifest file, there's no need to make any changes to how you process the results. The existing approach continues to work seamlessly with the updated feature.
88
-
- question: |
89
-
Can I revert to the previous behavior if I don't like the change?
90
-
answer: |
91
-
This isn't recommended, but it's possible. Please work through your support channels to ask to turn off this feature.
92
-
- question: |
93
-
How can I provide feedback or report issues related to the changes?
94
-
answer: |
95
-
Please work through your current account team and support channels.
96
-
- question: |
97
-
When will this change take effect?
98
-
answer: |
99
-
This change will start gradual rollout starting September 1, 2023.
97
+
- However, if your current processing involves reading the list of results files from the manifest file, there's no need to make any changes to how you process the results. The existing approach continues to work seamlessly with the updated feature.
98
+
- question: |
99
+
Can I revert to the previous behavior if I don't like the change?
100
+
answer: |
101
+
This isn't recommended, but it's possible. Please work through your support channels to ask to turn off this feature.
102
+
- question: |
103
+
How can I provide feedback or report issues related to the changes?
104
+
answer: |
105
+
Please work through your current account team and support channels.
106
+
- question: |
107
+
When will this change take effect?
108
+
answer: |
109
+
This change will start gradual rollout starting September 1, 2023.
100
110
- name: Metrics and Logs
101
111
questions:
102
112
- question: |
@@ -118,7 +128,7 @@ sections:
118
128
answer: |
119
129
Analytics logs have records of all read, write, list, and delete operations with successful and failed requests across all operations. Analytics logs are best-effort and no ordering is guaranteed.
120
130
121
-
The change feed is a solution that provides transactional log of successful mutations or changes to your account such as blob creation, modification, and deletions. The change feed guarantees all events to be recorded and displayed in the order of successful changes per blob, thus you do not have to filter out noise from a huge volume of read operations or failed requests. The change feed is fundamentally designed and optimized for application development that require certain guarantees.
131
+
The change feed is a solution that provides transactional log of successful mutations or changes to your account such as blob creation, modification, and deletions. The change feed guarantees all events to be recorded and displayed in the order of successful changes per blob, thus you do not have to filter out noise from a huge volume of read operations or failed requests. The change feed is fundamentally designed and optimized for application development that requires certain guarantees.
122
132
- question: |
123
133
Should I use the change feed or Storage events?
124
134
answer: |
@@ -153,7 +163,6 @@ sections:
153
163
Why isn't the root directory of the website not redirecting to the default index page?
154
164
answer: |
155
165
In the Azure portal, open the static website configuration page of your account and locate the name and extension that is set in the **Index document name** field. Ensure that this name is exactly the same as the name of the file located in the **$web** container of the storage account. File names and extensions in the url of a static website are case-sensitive even though they're served over HTTP.
156
-
157
166
- name: Blob index tags
158
167
questions:
159
168
- question: |
@@ -168,7 +177,6 @@ sections:
168
177
Are blob index tags and Azure Resource Manager tags related?
169
178
answer: |
170
179
No, Resource Manager tags help organize control plane resources such as subscriptions, resource groups, and storage accounts. Index tags provide blob management and discovery on the data plane.
0 commit comments