Skip to content

Commit 4bf2c1e

Browse files
Merge pull request #301254 from aadetayo/patch-3
Update blob inventory.md and blob-inventory-performance-characteristics.md
2 parents 0e5002c + aee4876 commit 4bf2c1e

File tree

2 files changed

+3
-2
lines changed

2 files changed

+3
-2
lines changed

articles/storage/blobs/blob-inventory-performance-characteristics.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ When generating inventory reports, opt for csv format if your use case doesn't r
5757
Instead of running inventory on the entire storage account, use a prefix match filter to generate an inventory report for specific subsets of your data.
5858
- Include Prefix: This filter targets a set of containers or paths within a container. This approach helps narrow down the scope of your inventory report, making the process faster and more efficient.
5959

60-
- Exclude Prefix: Use this filter to exclude some specific subset from it. This approach also helps narrow the scope of your inventory report. To learn more, see the articles/storage/blobs/blob-inventory.md#rule-filters.
60+
- Exclude Prefix: Use this filter to exclude some specific subset from it. This approach also helps narrow the scope of your inventory report. To learn more, see [Rule filters](blob-inventory.md#rule-filters)
6161

6262
### Select relevant fields
6363
Customize your inventory reports by selecting only the relevant fields you need. Doing this reduces the amount of data processed and exported, leading to quicker report generation, and easier analysis. To learn more about the inventory schema fields, see [Custom schema fields supported for blob inventory](blob-inventory.md#custom-schema-fields-supported-for-blob-inventory)

articles/storage/blobs/blob-inventory.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -260,7 +260,8 @@ View the JSON for inventory rules by selecting the **Code view** tab in the **Bl
260260

261261
If you configure a rule to run daily, then it will be scheduled to run every day. If you configure a rule to run weekly, then it will be scheduled to run each week on Sunday UTC time.
262262

263-
Most inventory runs complete within 24 hours. For hierarchical namespace enabled accounts, a run can take as long as two days, and depending on the number of files being processed, the run might not complete by end of that two days. The maximum amount of time that a run can complete before it fails is six days.
263+
The time taken to generate an inventory report depends on various factors and the maximum amount of time that an inventory run can complete before it fails is six days. To learn more about these influencing factors, see [Blob inventory performance characteristics](blob-inventory-performance-characteristics.md).
264+
264265

265266
Runs don't overlap so a run must complete before another run of the same rule can begin. For example, if a rule is scheduled to run daily, but the previous day's run of that same rule is still in progress, then a new run won't be initiated that day. Rules that are scheduled to run weekly will run each Sunday regardless of whether a previous run succeeds or fails. If a run doesn't complete successfully, check subsequent runs to see if they complete before contacting support. The performance of a run can vary, so if a run doesn't complete, it's possible that subsequent runs will.
266267

0 commit comments

Comments
 (0)