Skip to content

Commit 4b3ea20

Browse files
Merge pull request #223118 from normesta/lifecycle-management
Making lifecycle management event more visible in docs
2 parents 863f783 + 92439e8 commit 4b3ea20

File tree

1 file changed

+44
-1
lines changed

1 file changed

+44
-1
lines changed

articles/storage/blobs/lifecycle-management-overview.md

Lines changed: 44 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Use Azure Storage lifecycle management policies to create automated
55
author: normesta
66

77
ms.author: normesta
8-
ms.date: 12/21/2022
8+
ms.date: 01/05/2023
99
ms.service: storage
1010
ms.subservice: common
1111
ms.topic: conceptual
@@ -175,6 +175,49 @@ The run conditions are based on age. Current versions use the last modified time
175175

176176
<sup>1</sup> If [last access time tracking](#move-data-based-on-last-accessed-time) is not enabled for a blob, **daysAfterLastAccessTimeGreaterThan** uses the date the lifecycle policy was enabled instead of the `LastAccessTime` property of the blob.
177177

178+
## Lifecycle policy completed event
179+
180+
The `LifecyclePolicyCompleted` event is generated when the actions defined by a lifecycle management policy are performed. The following json shows an example `LifecyclePolicyCompleted` event.
181+
182+
```json
183+
{
184+
"topic": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/contosoresourcegroup/providers/Microsoft.Storage/storageAccounts/contosostorageaccount",
185+
"subject": "BlobDataManagement/LifeCycleManagement/SummaryReport",
186+
"eventType": "Microsoft.Storage.LifecyclePolicyCompleted",
187+
"eventTime": "2022-05-26T00:00:40.1880331",
188+
"id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
189+
"data": {
190+
"scheduleTime": "2022/05/24 22:57:29.3260160",
191+
"deleteSummary": {
192+
"totalObjectsCount": 16,
193+
"successCount": 14,
194+
"errorList": ""
195+
},
196+
"tierToCoolSummary": {
197+
"totalObjectsCount": 0,
198+
"successCount": 0,
199+
"errorList": ""
200+
},
201+
"tierToArchiveSummary": {
202+
"totalObjectsCount": 0,
203+
"successCount": 0,
204+
"errorList": ""
205+
}
206+
},
207+
"dataVersion": "1",
208+
"metadataVersion": "1"
209+
}
210+
```
211+
212+
The following table describes the schema of the `LifecyclePolicyCompleted` event.
213+
214+
|Field|Type|Description|
215+
|---|---|---|
216+
|scheduleTime|string|The time that the lifecycle policy was scheduled|
217+
|deleteSummary|vector\<byte\>|The results summary of blobs scheduled for delete operation|
218+
|tierToCoolSummary|vector\<byte\>|The results summary of blobs scheduled for tier-to-cool operation|
219+
|tierToArchiveSummary|vector\<byte\>|The results summary of blobs scheduled for tier-to-archive operation|
220+
178221
## Examples of lifecycle policies
179222

180223
The following examples demonstrate how to address common scenarios with lifecycle policy rules.

0 commit comments

Comments
 (0)