You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem:
Currently the application insights logger maps the dotnet LogLevel enum value to an application insights specific SeverityLevel.
This mapping is not one-to-one, as multiple log levels (Debug, Trace) get mapped to the single SeverityLevel.Verbose value. As a result, information is lost which prevents querying distinctly for trace telemetry specific to LogLevel.Debug vs LogLevel.Trace.
Problem:
Currently the application insights logger maps the dotnet LogLevel enum value to an application insights specific SeverityLevel.
This mapping is not one-to-one, as multiple log levels (Debug, Trace) get mapped to the single SeverityLevel.Verbose value. As a result, information is lost which prevents querying distinctly for trace telemetry specific to LogLevel.Debug vs LogLevel.Trace.
Describe the solution you'd like.
Include the specific LogLevel value in the telemetry properties dictionary along side the logging category name so that, when needed, it
can be queries against.
Describe alternatives you've considered.
N/A
Additional context.
The application insights logger implementation in the webjob sdk already includes the LogLevel in this way.
The text was updated successfully, but these errors were encountered: