Application Insights

Code-based monitoring and Codeless monitoring

Application Insights overview - Azure MonitorMicrosoftLearn

Log Levels

Logging in .NET Core and ASP.NET CoreMicrosoftLearn

ASP.NET Core defines the following log levels, ordered here from lowest to highest severity.

• Trace = 0

  For information that's typically valuable only for debugging. These messages may contain sensitive application data and so shouldn't be enabled in a production environment. Disabled by default.

• Debug = 1

  For information that may be useful in development and debugging. Example: Entering method Configure with flag set to true. Enable Debug level logs in production only when troubleshooting, due to the high volume of logs.

• Information = 2

  For tracking the general flow of the app. These logs typically have some long-term value. Example: Request received for path /api/todo

• Warning = 3

  For abnormal or unexpected events in the app flow. These may include errors or other conditions that don't cause the app to stop but might need to be investigated. Handled exceptions are a common place to use the Warning log level. Example: FileNotFoundException for file quotes.txt.

• Error = 4

  For errors and exceptions that cannot be handled. These messages indicate a failure in the current activity or operation (such as the current HTTP request), not an app-wide failure. Example log message: Cannot insert record due to duplicate key violation.

• Critical = 5

  For failures that require immediate attention. Examples: data loss scenarios, out of disk space.

Control ILogger Logging levels

Application Insights logging with .NET - Azure MonitorMicrosoftLearn

Adding custom Telemetry Initializer

Application Insights for ASP.NET Core applications - Azure MonitorMicrosoftLearn

Filtering and preprocessing in the Application Insights SDK - Azure MonitorMicrosoftLearn

Custom Telemetry events

Application Insights API for custom events and metrics - Azure MonitorMicrosoftLearn

Exceptions, and why not all are logged

Diagnose failures and exceptions with Azure Application Insights - Azure MonitorMicrosoftLearn

Track request body

• https://stackoverflow.com/questions/51671154/view-requests-response-body-in-application-insights

• https://stackoverflow.com/questions/42686363/view-post-request-body-in-application-insights

• https://stackoverflow.com/questions/49313665/view-request-body-in-application-insights?noredirect=1&lq=1

• https://stackoverflow.com/questions/42686363/view-post-request-body-in-application-insights