Skip to content

Commit 9e534f8

Browse files
committed
Acrolinx
1 parent 2169507 commit 9e534f8

File tree

2 files changed

+37
-38
lines changed

2 files changed

+37
-38
lines changed

articles/data-lake-analytics/data-lake-analytics-data-lake-tools-get-started.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ After the job submission, the **Job view** tab opens to show the job progress.
9696
* **MetaData Operations** shows all the actions that were taken on the U-SQL catalog.
9797
* **Data** shows all the inputs and outputs.
9898
* **State History** shows the timeline and state details.
99-
* **AU Analysis** shows how many AUs were used in the job and explore simulations of different AU allocation strategies.
99+
* **AU Analysis** shows how many AUs (analytics units) were used in the job and explore simulations of different AU allocation strategies.
100100
* **Diagnostics** provides an advanced analysis for job execution and performance optimization.
101101

102102
![U-SQL Visual Studio Data Lake Analytics job performance graph](./media/data-lake-analytics-data-lake-tools-get-started/data-lake-analytics-data-lake-tools-performance-graph.png)
@@ -117,7 +117,7 @@ To see the latest job status and refresh the screen, select **Refresh**.
117117

118118
1. In **Data Lake Analytics Explorer**, browse to the job you submitted.
119119

120-
1. Click the **Data** tab in your job.
120+
1. Select the **Data** tab in your job.
121121

122122
1. In the **Job Outputs** tab, select the `"/data.csv"` file.
123123

articles/data-lake-analytics/data-lake-analytics-manage-use-portal.md

Lines changed: 35 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -2,45 +2,41 @@
22
title: Manage Azure Data Lake Analytics by using the Azure portal
33
description: This article describes how to use the Azure portal to manage Data Lake Analytics accounts, data sources, users, & jobs.
44
ms.service: data-lake-analytics
5-
ms.reviewer: jasonh
5+
ms.reviewer: whhender
66
ms.topic: how-to
7-
ms.date: 12/05/2016
7+
ms.date: 11/15/2022
88
ms.custom: subject-rbac-steps
99
---
1010
# Manage Azure Data Lake Analytics using the Azure portal
1111
[!INCLUDE [manage-selector](../../includes/data-lake-analytics-selector-manage.md)]
1212

13-
This article describes how to manage Azure Data Lake Analytics accounts, data sources, users, and jobs by using the Azure portal.
14-
13+
[!INCLUDE [retirement-flag](includes/retirement-flag.md)]
1514

16-
<!-- ################################ -->
17-
<!-- ################################ -->
15+
This article describes how to manage Azure Data Lake Analytics accounts, data sources, users, and jobs by using the Azure portal.
1816

1917
## Manage Data Lake Analytics accounts
2018

2119
### Create an account
2220

2321
1. Sign in to the [Azure portal](https://portal.azure.com).
24-
2. Click **Create a resource** > **Intelligence + analytics** > **Data Lake Analytics**.
22+
2. Select **Create a resource** and search for **Data Lake Analytics**.
2523
3. Select values for the following items:
2624
1. **Name**: The name of the Data Lake Analytics account.
2725
2. **Subscription**: The Azure subscription used for the account.
2826
3. **Resource Group**: The Azure resource group in which to create the account.
2927
4. **Location**: The Azure datacenter for the Data Lake Analytics account.
3028
5. **Data Lake Store**: The default store to be used for the Data Lake Analytics account. The Azure Data Lake Store account and the Data Lake Analytics account must be in the same location.
31-
4. Click **Create**.
29+
4. Select **Create**.
3230

3331
### Delete a Data Lake Analytics account
3432

3533
Before you delete a Data Lake Analytics account, delete its default Data Lake Store account.
3634

3735
1. In the Azure portal, go to your Data Lake Analytics account.
38-
2. Click **Delete**.
36+
2. Select **Delete**.
3937
3. Type the account name.
40-
4. Click **Delete**.
38+
4. Select **Delete**.
4139

42-
<!-- ################################ -->
43-
<!-- ################################ -->
4440

4541
## Manage data sources
4642

@@ -54,11 +50,11 @@ You can use Data Explorer to browse data sources and perform basic file manageme
5450
### Add a data source
5551

5652
1. In the Azure portal, go to your Data Lake Analytics account.
57-
2. Click **Data Sources**.
58-
3. Click **Add Data Source**.
53+
2. Select **Data explorer**.
54+
3. Select **Add Data Source**.
5955

6056
* To add a Data Lake Store account, you need the account name and access to the account to be able to query it.
61-
* To add Azure Blob storage, you need the storage account and the account key. To find them, go to the storage account in the portal.
57+
* To add Azure Blob storage, you need the storage account and the account key. To find them, go to the storage account in the portal and select **Access keys**.
6258

6359
## Set up firewall rules
6460

@@ -69,20 +65,20 @@ If other Azure services, like Azure Data Factory or VMs, connect to the Data Lak
6965
### Set up a firewall rule
7066

7167
1. In the Azure portal, go to your Data Lake Analytics account.
72-
2. On the menu on the left, click **Firewall**.
68+
2. On the menu on the left, select **Firewall**.
7369

7470
## Add a new user
7571

7672
You can use the **Add User Wizard** to easily provision new Data Lake users.
7773

7874
1. In the Azure portal, go to your Data Lake Analytics account.
79-
2. On the left, under **Getting Started**, click **Add User Wizard**.
80-
3. Select a user, and then click **Select**.
81-
4. Select a role, and then click **Select**. To set up a new developer to use Azure Data Lake, select the **Data Lake Analytics Developer** role.
82-
5. Select the access control lists (ACLs) for the U-SQL databases. When you're satisfied with your choices, click **Select**.
83-
6. Select the ACLs for files. For the default store, don't change the ACLs for the root folder "/" and for the /system folder. Click **Select**.
84-
7. Review all your selected changes, and then click **Run**.
85-
8. When the wizard is finished, click **Done**.
75+
2. On the left, under **Getting Started**, select **Add User Wizard**.
76+
3. Select a user, and then select **Select**.
77+
4. Select a role, and then select **Select**. To set up a new developer to use Azure Data Lake, select the **Data Lake Analytics Developer** role.
78+
5. Select the access control lists (ACLs) for the U-SQL databases. When you're satisfied with your choices, select **Select**.
79+
6. Select the ACLs for files. For the default store, don't change the ACLs for the root folder "/" and for the /system folder. select **Select**.
80+
7. Review all your selected changes, and then select **Run**.
81+
8. When the wizard is finished, select **Done**.
8682

8783
## Manage Azure role-based access control
8884

@@ -94,6 +90,7 @@ The standard Azure roles have the following capabilities:
9490
* **Reader**: Can monitor jobs.
9591

9692
Use the Data Lake Analytics Developer role to enable U-SQL developers to use the Data Lake Analytics service. You can use the Data Lake Analytics Developer role to:
93+
9794
* Submit jobs.
9895
* Monitor job status and the progress of jobs submitted by any user.
9996
* See the U-SQL scripts from jobs submitted by any user.
@@ -115,46 +112,48 @@ Use the Data Lake Analytics Developer role to enable U-SQL developers to use the
115112
>If a user or a security group needs to submit jobs, they also need permission on the store account. For more information, see [Secure data stored in Data Lake Store](../data-lake-store/data-lake-store-secure-data.md).
116113
>
117114
118-
<!-- ################################ -->
119-
<!-- ################################ -->
120-
121115
## Manage jobs
122116

123117
### Submit a job
124118

125119
1. In the Azure portal, go to your Data Lake Analytics account.
126120

127-
2. Click **New Job**. For each job, configure:
121+
2. Select **New Job**. For each job, configure:
128122

129123
1. **Job Name**: The name of the job.
130-
2. **Priority**: Lower numbers have higher priority. If two jobs are queued, the one with lower priority value runs first.
131-
3. **Parallelism**: The maximum number of compute processes to reserve for this job.
124+
2. **Priority**: This is under **More options**. Lower numbers have higher priority. If two jobs are queued, the one with lower priority value runs first.
125+
3. **AUs**: The maximum number of Analytics Units, or compute processes to reserve for this job.
126+
4. **Runtime**: Also under **More options**. Select the Default runtime unless you've received a custom runtime.
127+
128+
3. Add your script.
132129

133-
3. Click **Submit Job**.
130+
4. Select **Submit Job**.
134131

135132
### Monitor jobs
136133

137134
1. In the Azure portal, go to your Data Lake Analytics account.
138-
2. Click **View All Jobs**. A list of all the active and recently finished jobs in the account is shown.
139-
3. Optionally, click **Filter** to help you find the jobs by **Time Range**, **Job Name**, and **Author** values.
135+
2. Select **View All Jobs** at the top of the page. A list of all the active and recently finished jobs in the account is shown.
136+
3. Optionally, select **Filter** to help you find the jobs by **Time Range**, **Status**, **Job Name**, **Job ID**, **Pipeline name** or **Pipeline ID**, **Recurrence name** or **Recurrence ID**, and **Author** values.
140137

141138
### Monitoring pipeline jobs
139+
142140
Jobs that are part of a pipeline work together, usually sequentially, to accomplish a specific scenario. For example, you can have a pipeline that cleans, extracts, transforms, aggregates usage for customer insights. Pipeline jobs are identified using the "Pipeline" property when the job was submitted. Jobs scheduled using ADF V2 will automatically have this property populated.
143141

144142
To view a list of U-SQL jobs that are part of pipelines:
145143

146144
1. In the Azure portal, go to your Data Lake Analytics accounts.
147-
2. Click **Job Insights**. The "All Jobs" tab will be defaulted, showing a list of running, queued, and ended jobs.
148-
3. Click the **Pipeline Jobs** tab. A list of pipeline jobs will be shown along with aggregated statistics for each pipeline.
145+
2. Select **Job Insights**. The "All Jobs" tab will be defaulted, showing a list of running, queued, and ended jobs.
146+
3. Select the **Pipeline Jobs** tab. A list of pipeline jobs will be shown along with aggregated statistics for each pipeline.
149147

150148
### Monitoring recurring jobs
149+
151150
A recurring job is one that has the same business logic but uses different input data every time it runs. Ideally, recurring jobs should always succeed, and have relatively stable execution time; monitoring these behaviors will help ensure the job is healthy. Recurring jobs are identified using the "Recurrence" property. Jobs scheduled using ADF V2 will automatically have this property populated.
152151

153152
To view a list of U-SQL jobs that are recurring:
154153

155154
1. In the Azure portal, go to your Data Lake Analytics accounts.
156-
2. Click **Job Insights**. The "All Jobs" tab will be defaulted, showing a list of running, queued, and ended jobs.
157-
3. Click the **Recurring Jobs** tab. A list of recurring jobs will be shown along with aggregated statistics for each recurring job.
155+
2. Select **Job Insights**. The "All Jobs" tab will be defaulted, showing a list of running, queued, and ended jobs.
156+
3. Select the **Recurring Jobs** tab. A list of recurring jobs will be shown along with aggregated statistics for each recurring job.
158157

159158
## Next steps
160159

0 commit comments

Comments
 (0)