Merge pull request #227395 from ecfan/diagnostics

Azure Logic Apps: [Standard] Diagnostic settings (preview)

Author: Stacyrch140

.openpublishing.redirection.json

@@ -13241,7 +13241,7 @@
         },
         {
             "source_path_from_root": "/articles/logic-apps/logic-apps-monitor-your-logic-apps-oms.md",
-            "redirect_url": "/azure/logic-apps/monitor-logic-apps-log-analytics",
+            "redirect_url": "/azure/logic-apps/monitor-workflows-collect-diagnostic-data",
             "redirect_document_id": false
         },
         {
@@ -13339,6 +13339,12 @@
             "redirect_url": "/connectors/custom-connectors/submit-certification",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/logic-apps/monitor-logic-apps-log-analytics.md",
+            "redirect_url": "/azure/logic-apps/monitor-workflows-collect-diagnostic-data",
+            "redirect_document_id": true
+        },
+
         {
             "source_path_from_root": "/articles/connectors/connectors-create-api-sharepointonline.md",
             "redirect_url": "/azure/connectors/connectors-create-api-sharepoint",

articles/azure-functions/functions-compare-logic-apps-ms-flow-webjobs.md

@@ -53,7 +53,7 @@ You can mix and match services when you build an orchestration, such as calling
 | **Development** | Code-first (imperative) | Designer-first (declarative) |
 | **Connectivity** | [About a dozen built-in binding types](functions-triggers-bindings.md#supported-bindings), write code for custom bindings | [Large collection of connectors](/connectors/connector-reference/connector-reference-logicapps-connectors), [Enterprise Integration Pack for B2B scenarios](../logic-apps/logic-apps-enterprise-integration-overview.md), [build custom connectors](/connectors/custom-connectors/) |
 | **Actions** | Each activity is an Azure function; write code for activity functions |[Large collection of ready-made actions](/connectors/connector-reference/connector-reference-logicapps-connectors)|
-| **Monitoring** | [Azure Application Insights](../azure-monitor/app/app-insights-overview.md) | [Azure portal](../logic-apps/quickstart-create-first-logic-app-workflow.md), [Azure Monitor logs](../logic-apps/monitor-logic-apps-log-analytics.md), [Microsoft Defender for Cloud](../logic-apps/healthy-unhealthy-resource.md) |
+| **Monitoring** | [Azure Application Insights](../azure-monitor/app/app-insights-overview.md) | [Azure portal](../logic-apps/quickstart-create-first-logic-app-workflow.md), [Azure Monitor Logs](../logic-apps/monitor-workflows-collect-diagnostic-data.md), [Microsoft Defender for Cloud](../logic-apps/healthy-unhealthy-resource.md) |
 | **Management** | [REST API](durable/durable-functions-http-api.md), [Visual Studio](/visualstudio/azure/vs-azure-tools-resources-managing-with-cloud-explorer) | [Azure portal](../logic-apps/quickstart-create-first-logic-app-workflow.md), [REST API](/rest/api/logic/), [PowerShell](/powershell/module/az.logicapp), [Visual Studio](../logic-apps/manage-logic-apps-with-visual-studio.md) |
 | **Execution context** | Can run [locally](./functions-kubernetes-keda.md) or in the cloud | Runs in Azure, locally, or on premises. For more information, see [What is Azure Logic Apps](../logic-apps/logic-apps-overview.md#resource-environment-differences). |
 

articles/azure-monitor/logs/create-pipeline-datacollector-api.md

@@ -28,30 +28,30 @@ We are using a classic ETL-type logic to design our pipeline. The architecture w
 
 ![Data collection pipeline architecture](./media/create-pipeline-datacollector-api/data-pipeline-dataflow-architecture.png)
 
-This article will not cover how to create data or [upload it to an Azure Blob Storage account](../../storage/blobs/storage-upload-process-images.md). Rather, we pick the flow up as soon as a new file is uploaded to the blob. From here:
+This article will not cover how to create data or [upload it to an Azure Blob Storage account](../../storage/blobs/blob-upload-function-trigger.md). Rather, we pick the flow up as soon as a new file is uploaded to the blob. From here:
 
-1. A process will detect that new data has been uploaded.  Our example uses an [Azure Logic App](../../logic-apps/logic-apps-overview.md), which has available a trigger to detect new data being uploaded to a blob.
+1. A process will detect that new data has been uploaded. Our example uses an [logic app workflow](../../logic-apps/logic-apps-overview.md), which has available a trigger to detect new data being uploaded to a blob.
 
-2. A processor reads this new data and converts it to JSON, the format required by Azure Monitor  In this example, we use an [Azure Function](../../azure-functions/functions-overview.md) as a lightweight, cost-efficient way of executing our processing code. The function is kicked off by the same Logic App that we used to detect the new data.
+2. A processor reads this new data and converts it to JSON, the format required by Azure Monitor  In this example, we use an [Azure Function](../../azure-functions/functions-overview.md) as a lightweight, cost-efficient way of executing our processing code. The function is kicked off by the same logic app workflow that we used to detect the new data.
 
-3. Finally, once the JSON object is available, it is sent to Azure Monitor. The same Logic App sends the data to Azure Monitor using the built in Log Analytics Data Collector activity.
+3. Finally, once the JSON object is available, it is sent to Azure Monitor. The same logic app workflow sends the data to Azure Monitor using the built in Log Analytics Data Collector activity.
 
-While the detailed setup of the blob storage, Logic App, or Azure Function is not outlined in this article, detailed instructions are available on the specific products’ pages.
+While the detailed setup of the blob storage, logic app workflow, or Azure Function is not outlined in this article, detailed instructions are available on the specific products’ pages.
 
-To monitor this pipeline, we use Application Insights to monitor our Azure Function [details here](../../azure-functions/functions-monitoring.md), and Azure Monitor to monitor our Logic App [details here](../../logic-apps/monitor-logic-apps-log-analytics.md). 
+To monitor this pipeline, we use Application Insights to [monitor our Azure Function](../../azure-functions/functions-monitoring.md), and Azure Monitor to [monitor our logic app workflow](../../logic-apps/monitor-workflows-collect-diagnostic-data.md).
 
 ## Setting up the pipeline
 To set the pipeline, first make sure you have your blob container created and configured. Likewise, make sure that the Log Analytics workspace where you’d like to send the data to is created.
 
 ## Ingesting JSON data
-Ingesting JSON data is trivial with Logic Apps, and since no transformation needs to take place, we can encase the entire pipeline in a single Logic App. Once both the blob container and the Log Analytics workspace have been configured, create a new Logic App and configure it as follows:
+Ingesting JSON data is trivial with Azure Logic Apps, and since no transformation needs to take place, we can encase the entire pipeline in a single logic app workflow. Once both the blob container and the Log Analytics workspace have been configured, create a new logic app workflow and configure it as follows:
 
 ![Logic apps workflow example](./media/create-pipeline-datacollector-api/logic-apps-workflow-example-01.png)
 
-Save your Logic App and proceed to test it.
+Save your logic app workflow and proceed to test it.
 
 ## Ingesting XML, CSV, or other formats of data
-Logic Apps today does not have built-in capabilities to easily transform XML, CSV, or other types into JSON format. Therefore, we need to use another means to complete this transformation. For this article, we use the serverless compute capabilities of Azure Functions as a very lightweight and cost-friendly way of doing so. 
+monitor-workflows-collect-diagnostic-data today does not have built-in capabilities to easily transform XML, CSV, or other types into JSON format. Therefore, we need to use another means to complete this transformation. For this article, we use the serverless compute capabilities of Azure Functions as a very lightweight and cost-friendly way of doing so. 
 
 In this example, we parse a CSV file, but any other file type can be similarly processed. Simply modify the deserializing portion of the Azure Function to reflect the correct logic for your specific data type.
 
@@ -93,7 +93,7 @@ In this example, we parse a CSV file, but any other file type can be similarly p
 
     public static async Task<HttpResponseMessage> Run(HttpRequestMessage req, TraceWriter log)
     {
-        string filePath = await req.Content.ReadAsStringAsync(); //get the CSV URI being passed from Logic App
+        string filePath = await req.Content.ReadAsStringAsync(); //get the CSV URI being passed from logic app workflow
         string response = "";
 
         //get a stream from blob
@@ -121,12 +121,12 @@ In this example, we parse a CSV file, but any other file type can be similarly p
 
     ![Function Apps test code](./media/create-pipeline-datacollector-api/functions-test-01.png)
 
-Now we need to go back and modify the Logic App we started building earlier to include the data ingested and converted to JSON format.  Using View Designer, configure as follows and then save your Logic App:
+Now we need to go back and modify the logic app we started building earlier to include the data ingested and converted to JSON format.  Using View Designer, configure as follows and then save your logic app:
 
-![Logic Apps workflow complete example](./media/create-pipeline-datacollector-api/logic-apps-workflow-example-02.png)
+![Azure Logic Apps workflow complete example](./media/create-pipeline-datacollector-api/logic-apps-workflow-example-02.png)
 
 ## Testing the pipeline
-Now you can upload a new file to the blob configured earlier and have it monitored by your  Logic App. Soon, you should see a new instance of the Logic App kick off, call out to your Azure Function, and then successfully send the data to Azure Monitor. 
+Now you can upload a new file to the blob configured earlier and have it monitored by your logic app workflow. Soon, you should see a new instance of the logic app workflow kick off, call out to your Azure Function, and then successfully send the data to Azure Monitor. 
 
 >[!NOTE]
 >It can take up to 30 minutes for the data to appear in Azure Monitor the first time you send a new data type.
@@ -151,12 +151,12 @@ The output should show the two data sources now joined.
 ## Suggested improvements for a production pipeline
 This article presented a working prototype, the logic behind which can be applied towards a true production-quality solution. For such a production-quality solution, the following improvements are recommended:
 
-* Add error handling and retry logic in your Logic App and Function.
+* Add error handling and retry logic in your logic app workflow and Function.
 * Add logic to ensure that the 30MB/single Log Analytics Ingestion API call limit is not exceeded. Split the data into smaller segments if needed.
 * Set up a clean-up policy on your blob storage. Once successfully sent to the Log Analytics workspace, unless you’d like to keep the raw data available for archival purposes, there is no reason to continue storing it. 
 * Verify monitoring is enabled across the full pipeline, adding trace points and alerts as appropriate.
-* Leverage source control to manage the code for your function and Logic App.
-* Ensure that a proper change management policy is followed, such that if the schema changes, the function and Logic Apps are modified accordingly.
+* Leverage source control to manage the code for your function and logic app workflow.
+* Ensure that a proper change management policy is followed, such that if the schema changes, the function and logic app are modified accordingly.
 * If you are uploading multiple different data types, segregate them into individual folders within your blob container, and create logic to fan the logic out based on the data type. 
 
 

articles/azure-monitor/logs/logicapp-flow-connector.md

@@ -13,7 +13,7 @@ ms.date: 03/22/2022
 # Azure Monitor Logs connector for Logic Apps and Power Automate
 [Azure Logic Apps](../../logic-apps/index.yml) and [Power Automate](https://make.powerautomate.com) allow you to create automated workflows using hundreds of actions for various services. The Azure Monitor Logs connector allows you to build workflows that retrieve data from a Log Analytics workspace or an Application Insights application in Azure Monitor. This article describes the actions included with the connector and provides a walkthrough to build a workflow using this data.
 
-For example, you can create a logic app to use Azure Monitor log data in an email notification from Office 365, create a bug in Azure DevOps, or post a Slack message.  You can trigger a workflow by a simple schedule or from some action in a connected service such as when a mail or a tweet is received. 
+For example, you can create a logic app workflow to use Azure Monitor log data in an email notification from Office 365, create a bug in Azure DevOps, or post a Slack message.  You can trigger a workflow by a simple schedule or from some action in a connected service such as when a mail or a tweet is received. 
 
 ## Connector limits
 The Azure Monitor Logs connector has these limits:
@@ -44,25 +44,24 @@ The following tutorial illustrates the use of the Azure Monitor Logs connector i
 ### Create a Logic App
 
 1. Go to **Logic Apps** in the Azure portal and select **Add**. 
-1. Select a **Subscription**, **Resource group**, and **Region** to store the new logic app and then give it a unique name. You can turn on the **Log Analytics** setting to collect information about runtime data and events as described in [Set up Azure Monitor logs and collect diagnostics data for Azure Logic Apps](../../logic-apps/monitor-logic-apps-log-analytics.md). This setting isn't required for using the Azure Monitor Logs connector.
-
-    ![Screenshot that shows the Basics tab on the Logic App creation screen.](media/logicapp-flow-connector/create-logic-app.png)
+1. Select a **Subscription**, **Resource group**, and **Region** to store the new logic app and then give it a unique name. You can turn on the **Log Analytics** setting to collect information about runtime data and events as described in [Set up Azure Monitor logs and collect diagnostics data for Azure Logic Apps](../../logic-apps/monitor-workflows-collect-diagnostic-data.md). This setting isn't required for using the Azure Monitor Logs connector.
 
+   ![Screenshot that shows the Basics tab on the logic app creation screen.](media/logicapp-flow-connector/create-logic-app.png)
 
 1. Select **Review + create** > **Create**. 
 1. When the deployment is complete, select **Go to resource** to open the **Logic Apps Designer**.
 
-### Create a trigger for the logic app
+### Create a trigger for the logic app workflow
 1. Under **Start with a common trigger**, select **Recurrence**. 
 
-    This creates a logic app that automatically runs at a regular interval. 
+    This creates a logic app workflow that automatically runs at a regular interval. 
 
 1. In the **Frequency** box of the action, select **Day** and in the **Interval** box, enter **1** to run the workflow once per day.
 
     ![Screenshot that shows the Logic Apps Designer "Recurrence" window on which you can set the interval and frequency at which the logic app runs.](media/logicapp-flow-connector/recurrence-action.png)
 
 ## Walkthrough: Mail visualized results
-This tutorial shows how to create a logic app that sends the results of an Azure Monitor log query by email. 
+This tutorial shows how to create a logic app workflow that sends the results of an Azure Monitor log query by email. 
 
 ### Add Azure Monitor Logs action
 1. Select **+ New step** to add an action that runs after the recurrence action. 
@@ -112,23 +111,23 @@ This tutorial shows how to create a logic app that sends the results of an Azure
 
 1. Specify the email address of a recipient in the **To** window and a subject for the email in **Subject**. 
 
-    ![Screenshot of the settings for the new Send an email (V2) action, showing the subject line and email recepients being defined.](media/logicapp-flow-connector/mail-action.png)
+    ![Screenshot of the settings for the new Send an email (V2) action, showing the subject line and email recipients being defined.](media/logicapp-flow-connector/mail-action.png)
 
-### Save and test your logic app
-1. Select **Save** and then **Run** to perform a test run of the logic app.
+### Save and test your workflow
+1. Select **Save** and then **Run** to perform a test run of the workflow.
 
     ![Save and run](media/logicapp-flow-connector/save-run.png)
 
 
-    When the logic app completes, check the mail of the recipient that you specified.  You should receive a mail with a body similar to the following:
+    When the workflow completes, check the mail of the recipient that you specified.  You should receive a mail with a body similar to the following:
 
     ![An image of a sample email.](media/logicapp-flow-connector/sample-mail.png)
 
     > [!NOTE]
-    > The log app generates an email with a JPG file that depicts the query result set. If your query doesn't return results, the logic app won't create a JPG file.  
+    > The workflow generates an email with a JPG file that depicts the query result set. If your query doesn't return results, the workflow won't create a JPG file.  
 
 ## Next steps
 
 - Learn more about [log queries in Azure Monitor](./log-query-overview.md).
-- Learn more about [Logic Apps](../../logic-apps/index.yml)
+- Learn more about [Azure Logic Apps](../../logic-apps/index.yml)
 - Learn more about [Power Automate](https://make.powerautomate.com).