Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ILogger LogLevel Not Include In Trace Telemetry Data #2894

Open
RyanThomas73 opened this issue Aug 6, 2024 · 0 comments
Open

ILogger LogLevel Not Include In Trace Telemetry Data #2894

RyanThomas73 opened this issue Aug 6, 2024 · 0 comments

Comments

@RyanThomas73
Copy link

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.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant