| title | description | author | manager | editor | services | documentationcenter | ms.assetid | ms.service | ms.workload | ms.tgt_pltfrm | ms.devlang | ms.topic | ms.date | ms.author |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Monitor your Logic apps in Azure | Microsoft Docs |
How to see what your Logic apps have done |
jeffhollan |
anneta |
logic-apps |
5c1b1e15-3b6c-49dc-98a6-bdbe7cb75339 |
logic-apps |
integration |
na |
na |
article |
10/18/2016 |
jehollan |
After you create a Logic app, you can see the full history of its execution in the Azure portal. You can also set up services like Azure Diagnostics and Azure Alerts to monitor events real-time, and alert you for events like "when more than 5 runs fail within an hour."
To view the history, select Browse, and select Logic Apps. A list of all logic apps in your subscription is displayed. Select the logic app you want to monitor. You will see a list of all actions and triggers that have occurred for this logic app.
There are a few sections on this blade that are helpful:
- Summary lists All runs and the Trigger History
- All runs list the latest logic app runs. You can click any row for details on the run, or click on the tile to list more runs.
- Trigger History lists all the trigger activity for this logic app. Trigger activity could be a "Skipped" check for new data (e.g. looking to see if a new file was added to FTP), "Succeeded" meaning data was returned to fire a logic app, or "Failed" corresponding an error in configuration.
- Diagnostics allows you to view runtime details and events, and subscribe to Azure Alerts
Note
All runtime details and events are encrypted at rest within the Logic App service. They are only decrypted upon a view request from a user. Access to these events can also be controlled by Azure Role-Based Access Control (RBAC).
This list of runs shows the Status, the Start Time, and the Duration of the particular run. Select any row to see details on that run.
The monitoring view shows you each step of the run, the inputs and outputs, and any error messages that may have occurre.
If you need any additional details like the run Correlation ID (that can be used for the REST API), you can click the Run Details button. This includes all steps, status, and inputs/outputs for the run.
In addition to the details provided by the Azure Portal and REST API above, you can configure your logic app to use Azure Diagnostics for more rich details and debugging.
-
Click the Diagnostics section of the logic app blade
-
Click to configure the Diagnostic Settings
-
Configure an Event Hub or Storage Account to emit data to
Once diagnostics are configured, you can add Azure Alerts to fire when certain thresholds are crossed. In the Diagnostics blade, select the Alerts tile and Add alert. This will walk you through configuring an alert based on a number of thresholds and metrics.
You can configure the Condition, Threshold, and Period as desired. Finally, you can configure an email address to send a notification to, or configure a webhook. You can use the request trigger in a logic app to run on an alert as well (to do things like post to Slack, send a text, or add a message to a queue).
Each of these events contains details about the logic app and event like status. Here is an example of a ActionCompleted event:
{
"time": "2016-07-09T17:09:54.4773148Z",
"workflowId": "/SUBSCRIPTIONS/80D4FE69-ABCD-EFGH-A938-9250F1C8AB03/RESOURCEGROUPS/MYRESOURCEGROUP/PROVIDERS/MICROSOFT.LOGIC/WORKFLOWS/MYLOGICAPP",
"resourceId": "/SUBSCRIPTIONS/80D4FE69-ABCD-EFGH-A938-9250F1C8AB03/RESOURCEGROUPS/MYRESOURCEGROUP/PROVIDERS/MICROSOFT.LOGIC/WORKFLOWS/MYLOGICAPP/RUNS/08587361146922712057/ACTIONS/HTTP",
"category": "WorkflowRuntime",
"level": "Information",
"operationName": "Microsoft.Logic/workflows/workflowActionCompleted",
"properties": {
"$schema": "2016-06-01",
"startTime": "2016-07-09T17:09:53.4336305Z",
"endTime": "2016-07-09T17:09:53.5430281Z",
"status": "Succeeded",
"code": "OK",
"resource": {
"subscriptionId": "80d4fe69-ABCD-EFGH-a938-9250f1c8ab03",
"resourceGroupName": "MyResourceGroup",
"workflowId": "cff00d5458f944d5a766f2f9ad142553",
"workflowName": "MyLogicApp",
"runId": "08587361146922712057",
"location": "eastus",
"actionName": "Http"
},
"correlation": {
"actionTrackingId": "e1931543-906d-4d1d-baed-dee72ddf1047",
"clientTrackingId": "my-custom-tracking-id"
},
"trackedProperties": {
"myProperty": "<value>"
}
}
}The two properties that are especially useful for tracking and monitoring are clientTrackingId and trackedProperties.
The client tracking ID is a value that will correlate events across a logic app run, including any nested workflows called as a part of a logic app. This ID will be auto-generated if not provided, but you can manually specify the client tracking ID from a trigger by passing a x-ms-client-tracking-id header with the ID value in the trigger request (request trigger, HTTP trigger, or webhook trigger).
Tracked properties can be added onto actions in the workflow definition to track inputs or outputs in diagnostics data. This can be useful if you wish to track data like an "order ID" in your telemetry. To add a tracked property, include the trackedProperties property on an action. Tracked properties can only track a single actions inputs and outputs, but you can use the correlation properties of the events to correlate across actions in a run.
{
"myAction": {
"type": "http",
"inputs": {
"uri": "http://uri",
"headers": {
"Content-Type": "application/json"
},
"body": "@triggerBody()"
},
"trackedProperties":{
"myActionHTTPStatusCode": "@action()['outputs']['statusCode']",
"myActionHTTPValue": "@action()['outputs']['body']['foo']",
"transactionId": "@action()['inputs']['body']['bar']"
}
}
}You can leverage this telemetry from the Event Hub or Storage into other services like Operations Management Suite, Azure Stream Analytics, and Power BI to have real time monitoring of your integration workflows.