search

exceptionless / Exceptionless.Net

Exceptionless clients for the .NET platform
https://exceptionless.com
Other
554 stars 142 forks source link

Framework 4.6 log4net only records the error log #245

Closed knowyi closed 3 years ago

knowyi commented 3 years ago

Hello, my log4net can upload all log level logs in NETCORE environment. Historical project or framework version 4.6, but only error logs can be uploaded. What's the difference?

image

<?xml version="1.0" encoding="utf-8" ?>

ejsmith commented 3 years ago

The client sets the default minimum log level to error. You will need to set the min log level that you want either through the UI or in code.

knowyi commented 3 years ago

The client sets the default minimum log level to error. You will need to set the min log level that you want either through the UI or in code.

Is the minimum log level set in log4net configuration file useless?

ejsmith commented 3 years ago

I don't think you can set the min level on the appender itself, can you? I don't remember how it's configured. Can you show me a sample?

ejsmith commented 3 years ago

Found a sample here: https://stackoverflow.com/q/8926409/55890

So the problem is that generally Exceptionless is used for error reporting and not as a general log collector. With the log level defaulting to all, people were eating up their plan limits unintentionally. So we changed the default min level to error. Since that minimum level is in the Exceptionless client it will override the level set in the log4net appender. There is no way for us to know if you intentionally set a min level in the appender config or not. So we are taking the less chatty default since generally people just want their error log messages sent to exceptionless.

knowyi commented 3 years ago

Found a sample here: https://stackoverflow.com/q/8926409/55890

So the problem is that generally Exceptionless is used for error reporting and not as a general log collector. With the log level defaulting to all, people were eating up their plan limits unintentionally. So we changed the default min level to error. Since that minimum level is in the Exceptionless client it will override the level set in the log4net appender. There is no way for us to know if you intentionally set a min level in the appender config or not. So we are taking the less chatty default since generally people just want their error log messages sent to exceptionless.

I wonder why NETCORE's log4net will upload all log levels

knowyi commented 3 years ago

I don't think you can set the min level on the appender itself, can you? I don't remember how it's configured. Can you show me a sample?

I tested the Framework 4.6. The minimum level of log upload is warn. I want to change it to info. I don't know where to set it

niemyjski commented 3 years ago

I'm not sure why you are seeing different minimum levels. There are no code differences between our NET 4.5+ client and our .NET Core clients (it's the same code base). Can you please share a snippet of how you are configuring your logger and exceptionless client. If you could provide a github repo with a minimal sample I would be more than happy to debug it.

Here is a link to the source for the client implementation if you are curious: https://github.com/exceptionless/Exceptionless.Net/tree/master/src/Platforms/Exceptionless.Log4net

niemyjski commented 3 years ago

Were you able to narrow down this issue?