K
KentWeareMSFT
We are pleased to announce Application Insights Enhancements for Azure Logic Apps (Standard) has reached General Availability. This new capability offers customers a simplified experience for discovering insights about your logic app workflows and more control over filtering events at source which allow you to reduce your storage costs.
Note: The investments that we have made in this area are opt-in, meaning that your existing Logic Apps will continue to use the v1 schema. By enabling this new schema, also referred to as v2, your data will be emitted using a new schema. This means that if you have built custom reports that use the v1 schema, you will need to update those reports to take advantage of the new data structures. To learn about how to enable the v2 schema, please refer to our in-product documentation.
Benefits Summary
Based upon customer feedback, we have improved the observability experience for Azure Logic Apps (Standard) in the following areas:
General
Requests table
Traces table
Exceptions
Filtering (at source)
Log Stream Support
Live Metrics Stream Support
Metrics
To learn more about these features, please refer to our in-product documentation or check out our previous post.
Thank-you to the customers who participated in the private and public preview of this feature. The feedback collected during this time has improved our overall offering.
Continue reading...
Note: The investments that we have made in this area are opt-in, meaning that your existing Logic Apps will continue to use the v1 schema. By enabling this new schema, also referred to as v2, your data will be emitted using a new schema. This means that if you have built custom reports that use the v1 schema, you will need to update those reports to take advantage of the new data structures. To learn about how to enable the v2 schema, please refer to our in-product documentation.
Benefits Summary
Based upon customer feedback, we have improved the observability experience for Azure Logic Apps (Standard) in the following areas:
General
- Implemented consistency of names/Ids being used across different events and tables. These include:
- Workflow Id
- Workflow name
- Run Id
Requests table
- Reducing redundant data across tables.
- Reducing the amount of storage required by your Application Insights instance by moving key information from the trace table to the requests table. This avoids customers having to collect both sets of information to obtain a complete view of your workflow executions.
- Moving custom tracking ids and tracked properties from trace table to requests table.
- Making retry events easier to track.
- For trigger and action events, we now include the Trigger/Action type and the API name that allows you to query for the use of specific connectors.
Traces table
- Reduced the amount of verbosity in traces.
- Added meaningful categories and log levels to provide more flexibility with filtering.
- Workflow start/end records now stored in traces table.
- Batch events are now emitted to this table.
- Events using a consistent id/name, resource, and correlation details.
Exceptions
- Making Exceptions more descriptive.
- Exceptions are now captured for action/trigger failures.
Filtering (at source)
- Advanced filtering that allows for more control over how events are emitted including: actions and triggers.
- More control over filtering non-workflow related events.
Log Stream Support
- When using Logic Apps (Standard), developers can use the Log stream feature to view a stream of application log files. This source includes verbose technical information and is equivalent to the output seen when you debug your workflows during local development.
Live Metrics Stream Support
When your logic app is connected to Application Insights , you can view log data and other metrics in near real-time in the Azure portal using Live Metrics Stream. Visualizations are available that allow you to plot incoming requests, outgoing requests and overall health. It also includes a table of trace level diagnostics.
Metrics
- Improved consistency and filtering capabilities
To learn more about these features, please refer to our in-product documentation or check out our previous post.
Thank-you to the customers who participated in the private and public preview of this feature. The feedback collected during this time has improved our overall offering.
Continue reading...