Message Severity Levels for Application Insights Logs

Correct Answers: A, D and F

Application Insights is the feature of Azure Monitor.

It can help makers and developers to collect and analyze the canvas app telemetry.

Application Insights provides information like the number of sessions, number of the logged events, number of app users.

Developers can even trace the app's event executions by incorporating the Trace command within the app's code.

Then they use Azure Logs and Kusto to analyze the Trace output.

Or makers and developers might use Power BI for a visual representation of the Trace results.

The Trace function can help you collect information about errors, specific app users, and screen controls usage details.

The trace sends messages with three severity levels: Information, Warning, and Error.

All other options are the typical log severity levels, but the Power Apps tracer produces messages only with severity levels, as mentioned above.

For more information about using trace and Application Insights to troubleshoot canvas apps, please visit the below URLs:

When you add an event trace to your code in a canvas app and use Azure Application Insights to troubleshoot the app, the trace messages are sent to the Application Insights logs. The severity level of the trace messages determines their importance and helps you identify the severity of the issues in your app. Here's an explanation of the different message severity levels:

A. Information - This level is used for messages that provide general information about the application, such as the start and stop times of an operation. These messages are used to track the behavior of the application and do not indicate any issues.

B. Debug - This level is used for messages that are helpful in debugging the application. These messages are used to track the execution path of the application and provide details about how the application is working. Debug messages are typically only used during development and testing, and are not typically used in production.

C. Notice - This level is used for messages that indicate a condition that could be a problem in the future. These messages are used to track potential issues before they become critical.

D. Warning - This level is used for messages that indicate a potential problem that could affect the performance or functionality of the application. These messages are used to track issues that could affect the user experience and should be investigated.

E. Critical - This level is used for messages that indicate a critical problem that is preventing the application from functioning properly. These messages are used to track issues that require immediate attention.

F. Error - This level is used for messages that indicate an error condition that occurred in the application. These messages are used to track issues that need to be investigated and resolved.

In summary, the trace messages in a canvas app that are sent to Application Insights logs can have different severity levels, and you should pay attention to the severity level of the messages to help you identify and prioritize issues in your app. The severity levels range from least severe (Information) to most severe (Error). Therefore, the message severity levels that the trace sends to Application Insights logs are A. Information, B. Debug, C. Notice, D. Warning, E. Critical, and F. Error.