Within this post I would like to briefly demonstrate how to enable monitoring metrics for Logic Apps and adding charts your azure start boards. I highly believe that keeping a non-automated close eye on resources is crucial after deploying new applications or alterations. This will also provide some useful insights on application usage patterns as well.
Monitoring Metrics Logic Apps – Enable diagnostics
NOTE: if you aren’t familiar with the default monitoring options available for Logic apps, I highly recommend reading the following article first: https://azure.microsoft.com/en-us/documentation/articles/app-service-logic-monitor-your-logic-apps
Monitoring diagnostics can be enabled via the Azure Portal by following the steps listed below:
- Open the Logic App for which you would like to enable Diagnostics.
- Within the details blade, scroll to the Monitoring group at the bottom. Here you will see the message “Monitoring may not be enabled. Click here to turn on diagnostics.” .
- Click on the empty chart area as suggested, this will trigger the display of the diagnostics blade.
- Here it’s required to set the Status to ON, select a storage account located within the same region as the Logic app and select Metrics PT1M
- Save the changes
After waiting for a few minutes, metrics will start appearing if your Logic app has activity.
Altering or adding new charts
By default, the monitoring sections of the Logic App blade will contain two charts: Runs succeeded and failed in the past hour and Runs success latency in the past hour.
Alter an existing Chart
If you would like at alter an existing chart, just right click in the chart and select Edit Chart within the popup menu or click on Edit within the right upper corner of the chart. The Edit Chart blade will appear allowing you to change the type of charge and add or remove additional metrics.
The following nine metrics are available at one-minute granularity for the past hour:
- Run latency: The average time between when a run starts an when it ends
- Run rate: How many runs start per second
- Run success latency: The average time between start and end, but only for successful runs
- Run success percentage: The number of successful runs divided by the total
- Runs cancelled: The number of runs you’ve cancelled
- Runs completed: The number of completed runs, irrespective of status
- Runs failed: The number of runs that failed
- Runs started: The number of runs that started in that minute
- Runs succeeded: The number of runs that completed successfully
Adding a new Chart
Adding a new chart isn’t as straightforward as expected given that the Add new chart button is missing within the interface. To add a new chart, select an existing chart, right click and select Customize.
A new popup menu will appear containing the Clone option. After selecting Clone, a clone of the chart should appear below the existing one. At this point it’s required to exit GUI edit / customization mode, a mode you enter as soon as you start altering the appearance of a blade or start board. To exit this mode just click on the button Done located at the top of the screen.
Now it’s possible to alter the chart as discussed within the previous section. In addition, it’s also possible to pin the complete blade to a start board (dashboard) or any of the existing charts. I’ve covered different Azure portal monitoring options in great detail within the following post:
https://devslice.net/2015/01/azure-portal-monitoring-basics/
Recent Comments