使用类别时在 log4j 中配置多个日志文件
这就是我想要做的：我想要 2 个日志文件：第一个记录应用程序所有部分的 INFO 级别及以上级别，还记录某些包的 DEBUG 及以上级别。第二个仅记录所有包中的错误和错误。我确信这可能是微不足道的，但我不太明白。这是我当前正在使用的配置文件：
log4j.rootLogger=INFO,console,R
#console appender
log4j.appender.console = org.apache.log4j.ConsoleAppender
log4j.appender.console.layout = org.apache.log4j.PatternLayout
log4j.appender.console.layout.ConversionPattern = %t %-5p %c{2} - %m%n
#file appender
log4j.appender.R = org.apache.log4j.DailyRollingFileAppender
log4j.appender.R.DatePattern = '.'yyyy-MM-dd
log4j.appender.R.File = log/log.txt
log4j.appender.R.layout = org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern = [%d{ISO8601}]%5p%6.6r[%t]%x(%F:%L) - %m%n
#Specific log levels
log4j.category.com.mypackage1=DEBUG
log4j.category.com.mypackage2=DEBUG
显然，它没有错误日志部分。我的基本想法是添加另一个附加程序并将其日志级别设置为“错误”，但类别似乎会覆盖它及其信息，这不是我想要的。它们存在的原因是因为其他包转储了许多我们在设置调试时不需要的信息，这就是我们解决它的方法。我认为可能有更好的整体方法，但这是我的第一个 log4j 配置文件。
更新：一位同事建议使用 2 个记录器，正如 kdgregory 在他的评论中链接到的帖子中提到的那样（用于调试和错误的不同 log4j 布局？）。那里的人们似乎认为这是一个坏主意，但没有人解释原因。它看起来确实有点老套，但它满足了我们的需要。不使用该方法的主要原因是什么（除了必须维护 2 个不同的记录器之外）？
Here's what I'm trying to do: I want 2 log files: The first logs INFO level and up for all parts of the applications but also logs DEBUG and up for some packages. The second only logs ERROR and up across all packages. I'm sure this is probably trivial but I can't quite figure it out. Here is the configuration file I am currently using:
log4j.rootLogger=INFO,console,R
#console appender
log4j.appender.console = org.apache.log4j.ConsoleAppender
log4j.appender.console.layout = org.apache.log4j.PatternLayout
log4j.appender.console.layout.ConversionPattern = %t %-5p %c{2} - %m%n
#file appender
log4j.appender.R = org.apache.log4j.DailyRollingFileAppender
log4j.appender.R.DatePattern = '.'yyyy-MM-dd
log4j.appender.R.File = log/log.txt
log4j.appender.R.layout = org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern = [%d{ISO8601}]%5p%6.6r[%t]%x(%F:%L) - %m%n
#Specific log levels
log4j.category.com.mypackage1=DEBUG
log4j.category.com.mypackage2=DEBUG
This doesn't have the error log part, obviously. My basic idea was to add another appender and set its log level to ERROR but the categories seem to override it and and their info in as well, which is not what I want. The reason they are there is because the other packages dump alot of information that we don't need when set to debug and this is how we are getting around it. I'm thinking there may be a better overall approach to this but this is my first log4j config file ever.
UPDATE: A co-worker suggested using 2 loggers as is mentioned in the post that kdgregory linked to in his comment (Different log4j layout for debug and error?). People there seemed to think it was a bad idea but no one ever explained why. It does seem a bit hacky but it does what we need. What are the main reasons to not use that method (other than having to maintain 2 different loggers)?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这就是我最终想出的方法：
这会生成 2 个日志，其中一个日志记录所有处于 Warn 或以上级别的日志，以及指定包上的 DEBUG 或以上级别的标准日志，以及 ERROR 及以上级别的日志，仅记录所有包到错误日志。
Here is what I eventually came up with that did the trick:
This makes 2 logs, one which logs everything at Warn or above plus at DEBUG or above on the specified packages for the standard log and at ERROR and above only across all packages to the error log.