Skip to content

Commit 6732e36

Browse files
committed
fixd blocking issues
1 parent 938638e commit 6732e36

File tree

4 files changed

+29
-29
lines changed

4 files changed

+29
-29
lines changed

articles/stream-analytics/cicd-deploy-with-bicep.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
---
2-
title: Deploy Stream Analytics jobs with Bicep
3-
description: This article shows you how to generate and deploy Stream Analytics jobs using Bicep template.
2+
title: Deploy Azure Stream Analytics jobs using Bicep files
3+
description: This article shows you how to generate and deploy Azure Stream Analytics jobs using Bicep files.
44
ms.service: stream-analytics
55
author: alexlzx
66
ms.author: zhenxilin
77
ms.date: 05/24/2023
88
ms.topic: how-to
99
---
1010

11-
# Deploy Stream Analytics jobs with Bicep
11+
# Deploy Stream Analytics jobs with Bicep files
1212

1313
The Azure Stream Analytics (ASA) CI/CD npm package allows you to build, test, and deploy your Stream Analytics projects in your CI/CD pipeline using Bicep files. This article walks you through how to generate bicep files and deploy your ASA jobs.
1414

articles/stream-analytics/cicd-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Continuous integration and continuous deployment of Stream Analytics jobs
2+
title: Continuous integration and continuous deployment of Azure Stream Analytics jobs
33
description: This article gives an overview of setting up a continuous integration and deployment (CI/CD) pipeline for Azure Stream Analytics jobs.
44
services: stream-analytics
55
author: alexlzx
Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Export and manage Stream Analytics jobs in Visual Studio Code
2+
title: Export and manage Azure Stream Analytics jobs in Visual Studio Code
33
description: This article shows you how to export and manage an Azure Stream Analytics job with the Azure Stream Analytics extension for Visual Studio Code.
44
ms.service: stream-analytics
55
author: alexlzx
@@ -10,7 +10,7 @@ ms.topic: how-to
1010

1111
# Export and manage Stream Analytics jobs in Visual Studio Code
1212

13-
The Azure Stream Analytics extension (ASA) for Visual Studio Code gives you a seamless experience for managing Stream Analytics jobs in the cloud. It can be used across Windows, Mac and Linux platforms. With the ASA extension, it allows you to:
13+
The Azure Stream Analytics (ASA) extension for Visual Studio Code gives you a seamless experience for managing Stream Analytics jobs in the cloud. It can be used across Windows, Mac and Linux platforms. With the ASA extension, it allows you to:
1414

1515
- Create, start, and stop a cloud job in Azure
1616
- Export existing jobs to a local machine
@@ -22,59 +22,59 @@ The Azure Stream Analytics extension (ASA) for Visual Studio Code gives you a se
2222
1. Open your VS Code and select **Azure** icon on the activity bar. If you haven't installed the ASA extension, follow [this guide](./quick-create-visual-studio-code.md) to install.
2323
2. Select **STREAM ANALYTICS** in the explorer to locate the job you want to export.
2424

25-
![Export ASA job in Visual Studio Code](./media/vscode-explore-jobs/export-job.png)
25+
![Screenshot of VSCode extension exporting ASA job to Visual Studio Code.](./media/vscode-explore-jobs/export-job.png)
2626

2727
## List job and view job entities
2828

2929
You can use the job view to interact with Azure Stream Analytics jobs from Visual Studio.
3030

3131
1. Select the **Azure** icon on Visual Studio Code Activity Bar and then expand **Stream Analytics node**. Your jobs should appear under your subscriptions.
3232

33-
![Open Stream Analytics Explorer](./media/vscode-explore-jobs/open-explorer.png)
33+
![Screenshot of VSCode extension opening Stream Analytics Explorer.](./media/vscode-explore-jobs/open-explorer.png)
3434

3535
2. Expand your job node, you can open and view the job query, configuration, inputs, outputs and functions.
3636

3737
3. Right-click your job node, and choose the **Open Job View in Portal** node to open the job view in the Azure portal.
3838

39-
![Open job view in portal](./media/vscode-explore-jobs/open-job-view.png)
39+
![Screenshot of VSCode extension opening job view in portal.](./media/vscode-explore-jobs/open-job-view.png)
4040

4141
## View job diagram and debug in Job Monitor
4242

4343
You can use job monitor in Visual Studio Code to view and troubleshoot your Azure Stream Analytics jobs.
4444

4545
### View job diagram and job summary
4646
1. Select **Job Monitor**. Your Job Monitor should appear, and job diagram should be loaded automatically.
47-
![Open Job Monitor](./media/vscode-explore-jobs/open-job-monitor.png)
47+
![Screenshot of VSCode extension opening Job Monitor.](./media/vscode-explore-jobs/open-job-monitor.png)
4848

4949
2. You can view your job diagram and select **Job Summary** to view properties and information of your job.
50-
![View Job Summary](./media/vscode-explore-jobs/view-jobs-summary.png)
50+
![Screenshot of VSCode extension viewing Job Summary.](./media/vscode-explore-jobs/view-jobs-summary.png)
5151

5252
3. You can select **Test Connection** button to test connection to your input and output.
53-
![Test Connection](./media/vscode-explore-jobs/test-connection.png)
53+
![Screenshot of VSCode extension testing connection.](./media/vscode-explore-jobs/test-connection.png)
5454

5555
4. You can also select **Locate Script** button to view your query.
5656
![View Query](./media/vscode-explore-jobs/view-query.png)
5757

5858
### Monitor and debug with Metrics
5959

6060
1. Select the arrow button, you can open the Metrics panel.
61-
![Open Metrics Panel](./media/vscode-explore-jobs/open-metrics-panel.png)
61+
![Screenshot of VSCode extension opening Metrics Panel.](./media/vscode-explore-jobs/open-metrics-panel.png)
6262

6363
2. You can interact with it and analyze your job with key metrics showing in chart. You can choose to view job-level metrics or nodes level metrics. And you can also decide which metrics you want them to show in the chart.
64-
![View Metrics](./media/vscode-explore-jobs/view-metrics.png)
64+
![Screenshot of VSCode extension viewing job metrics.](./media/vscode-explore-jobs/view-metrics.png)
6565

6666
### Debug with diagnostic logs and activity logs
6767

6868
You can view your job’s diagnostic logs and activity logs for troubleshooting.
6969

7070
1. Select **Diagnostic Logs** tab.
7171

72-
![View Diagnostic Logs](./media/vscode-explore-jobs/view-diagnostic-log.png)
72+
![Screenshot of VSCode extension viewing Diagnostic Logs.](./media/vscode-explore-jobs/view-diagnostic-log.png)
7373

7474
2. Select **Activity Logs** tab
7575

76-
![View Activity Logs](./media/vscode-explore-jobs/view-activity-logs.png)
76+
![Screenshot of VSCode extension viewing Activity Logs.](./media/vscode-explore-jobs/view-activity-logs.png)
7777

7878
## Next steps
7979

80-
* [Create an Azure Stream Analytics cloud job in Visual Studio Code](quick-create-visual-studio-code.md)
80+
* [Create an Azure Stream Analytics cloud job using Visual Studio Code extension](quick-create-visual-studio-code.md)

articles/stream-analytics/visual-studio-code-local-run-live-input.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Testing Stream Analytics query locally against live stream input with Visual Studio Code
2+
title: Testing Azure Stream Analytics query locally against live stream input using Visual Studio Code extension.
33
description: This article describes how to test query locally against live stream input using the Azure Stream Analytics Tools extension for Visual Studio Code.
44
ms.service: stream-analytics
55
ms.custom: build-2023
@@ -21,32 +21,32 @@ Testing your Stream Analytics query locally against live stream input is a cruci
2121
## Define a live stream input
2222

2323
1. Right-click the **Inputs** folder in your Stream Analytics project and select **ASA: Add Input**.
24-
![Screenshot of VSCode adding input via drop-down menu](./media/quick-create-visual-studio-code/add-input-from-inputs-folder.png)
24+
![Screenshot of VSCode extension adding input via drop-down menu.](./media/quick-create-visual-studio-code/add-input-from-inputs-folder.png)
2525
OR press **Ctrl+Shift+P** to open the command palette and enter **ASA: Add Input**. Then choose the query script for processing the input stream.
26-
![Screenshot of VSCode adding input via command palette](./media/quick-create-visual-studio-code/add-input.png)
26+
![Screenshot of VSCode extension adding input via command palette.](./media/quick-create-visual-studio-code/add-input.png)
2727

2828
2. Choose a live input source type from the drop-down list, **Select from your Azure Subscriptions** and enter a name for the input source.
29-
![Screenshot of VSCode showing series of steps for Event Hub input configuration](./media/quick-create-visual-studio-code/add-input-select-subscription.png)
29+
![Screenshot of VSCode extension showing series of steps for Event Hub input configuration.](./media/quick-create-visual-studio-code/add-input-select-subscription.png)
3030

3131
3. You see a new JSON file created under the **Input** folder. Open the file and **Select from your subscriptions** to help you configure your Event Hubs input.
32-
![Screenshot of VSCode showing the input json files](./media/quick-create-visual-studio-code/configure-input.png)
32+
![Screenshot of VSCode extension showing the input json files.](./media/quick-create-visual-studio-code/configure-input.png)
3333

3434
4. Select **Preview data** to validate if the live input is successfully configured.
35-
![Screenshot of VSCode previewing live input data](./media/quick-create-visual-studio-code/preview-live-input.png)
35+
![Screenshot of VSCode extension previewing live input data.](./media/quick-create-visual-studio-code/preview-live-input.png)
3636

3737
## Run query locally
3838

3939
Open your query file, select **Run locally** or the **Play** button on the menu bar to open a **Local run option** window for configuring local run mode.
4040

41-
![Screenshot of selecting "Run locally" in the query editor](./media/vscode-local-run-live-input/run-locally.png)
41+
![Screenshot of VSCode extension selecting "Run locally" in the query editor.](./media/vscode-local-run-live-input/run-locally.png)
4242

4343
Choose **Use Live Input and Local Output** to run job locally against live input stream and produce output results to a local folder. Then select **Run** to start running job locally.
4444

45-
![Screenshot of VSCode select play mode](./media/vscode-local-run-live-input/run-live-input-and-local-output.png)
45+
![Screenshot of VSCode extension selecting play mode for local run.](./media/vscode-local-run-live-input/run-live-input-and-local-output.png)
4646

4747
You can see a **Local test** window is opened and refreshed every 3 seconds. The output results are stored as JSON format in **LocalRunOutputs** folder.
4848

49-
![Screenshot of VSCode showing local test window](./media/vscode-local-run-live-input/local-testing-window.png)
49+
![Screenshot of VSCode extension showing local test window.](./media/vscode-local-run-live-input/local-testing-window.png)
5050

5151

5252
## Specify input partitions for local testing
@@ -57,7 +57,7 @@ To avoid ingesting all data from Event Hubs, you can specify specific partitions
5757
2. Under **Select the input partitions** section and choose **Custom**.
5858
3. Enter the specific partition numbers that you want to ingest data from for your local testing.
5959

60-
![Screenshot of VSCode specifying event hub partitions](./media/vscode-local-run-live-input/specify-partitions.png)
60+
![Screenshot of VSCode extension specifying event hub partitions.](./media/vscode-local-run-live-input/specify-partitions.png)
6161

6262
By specifying the partitions, you can focus on testing your query logic without worrying about a large volume of data. This feature allows for more efficient and targeted testing of your Stream Analytics job.
6363

@@ -68,11 +68,11 @@ Once you have completed testing your query locally, you can submit your Stream A
6868
2. In the submit options window, you can **update an existing job in Azure** or **create a new job** for the upload.
6969
3. Provide the necessary details, including your subscription, resource group, and region for the deployment.
7070

71-
![Screenshot of VSCode submitting job to Azure](./media/vscode-local-run-live-input/submit-to-azure.png)
71+
![Screenshot of VSCode extension submitting job to Azure.](./media/vscode-local-run-live-input/submit-to-azure.png)
7272

7373
Once the submission process is complete, you can view your cloud job in a new window. From there, you can monitor its performance and manage its configurations as needed. You can also open the job in your browser by clicking on the link provided in the OUTPUT panel.
7474

75-
![Screenshot of VSCode showing cloud view job](./media/vscode-local-run-live-input/cloud-view-job.png)
75+
![Screenshot of VSCode extension showing cloud view job.](./media/vscode-local-run-live-input/cloud-view-job.png)
7676

7777
## Next steps
7878

0 commit comments

Comments
 (0)