Skip to content

Commit 53b1df8

Browse files
committed
Learn Editor: Update report-usage-across-multiple-labs-subscriptions.md
1 parent 42b3b94 commit 53b1df8

File tree

1 file changed

+1
-11
lines changed

1 file changed

+1
-11
lines changed

articles/devtest-labs/report-usage-across-multiple-labs-subscriptions.md

Lines changed: 1 addition & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -30,17 +30,7 @@ Before you can export DevTest Labs resource usage, you have to set up an Azure S
3030
> [!NOTE]
3131
> The date parameter doesn't include a time stamp so the data includes everything from midnight based on the time zone where the lab is located.
3232
33-
Once the export is complete, there will be multiple CSV files in the blob storage with the different resource information.
34-
35-
Currently there are two CSV files:
36-
37-
* *virtualmachines.csv* - contains information about the virtual machines in the lab
38-
* *disks.csv* - contains information about the different disks in the lab
39-
40-
These files are stored in the *labresourceusage* blob container. The files are under the lab name, lab unique ID, date executed, and either `full` or the start date of the export request. An example blob structure is:
41-
42-
* `labresourceusage/labname/1111aaaa-bbbb-cccc-dddd-2222eeee/<End>DD26-MM6-2019YYYY/full/virtualmachines.csv`
43-
* `labresourceusage/labname/1111aaaa-bbbb-cccc-dddd-2222eeee/<End>DD-MM-YYYY/26-6-2019/20-6-2019<Start>DD-MM-YYYY/virtualmachines.csv`
33+
Once the export is complete, there will be a CSV file in the blob storage with the different resource information.
4434

4535
## Exporting usage for all labs
4636

0 commit comments

Comments
 (0)