blocks|key|4035512|text|LogBack就是未来，它就在这里！|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4035513|logback是作为log4j的继任者创建的，并且完全符合slf4j框架，它可能是满足您的需求的最简单(且干净)的方法。|4035514|我不是专家，但我猜SiftingAppender可能是正确的答案。应该有一个针对您的鉴别器选项。也许你可以构建自己的鉴别器，扩展SiftingAppender，或者从Janino库中获得一些额外的帮助。|4035515|希望这能有所帮助！|4035516|entityMap|0|LINK|mutability|MUTABLE|url|http://logback.qos.ch/|1|http://logback.qos.ch/manual/appenders.html#SiftingAppender^0|0|7|0|0|0|9|F|1|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]|R|$5|M|N|O|C|$P|S]]]]

<a href="http://logback.qos.ch" rel="nofollow">LogBack</a> is the future, and it's here!

Created as a successor of log4j and fully complaint with the slf4j framework, logback might be the easy (and clean) way to fulfill your need.

I'm not an expert but I guess that <a href="http://logback.qos.ch/manual/appenders.html#SiftingAppender" rel="nofollow">SiftingAppender</a> might be the right answer. There should be a discriminator option for you. Maybe you can build your own discriminator, extend the SiftingAppender, or get some extra help from Janino library.

Hope this helps!

blocks|key|299441|text|如果您自己实现了记录器，那么没有什么可以阻止您这样做。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|299442|例如，将log函数作为参数提供给您当前正在与之通信的设备的编号，并按照您所描述的方式实现它。|299443|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If you are implementing the logger yourself, there's nothing to stop you from doing this. 
For example, give the log function as a parameter the number of the device you're currently communicating with, and implement it the way you described.

blocks|key|299459|text|如果您使用的是我强烈推荐的Apache+log4j，那么通过扩展AppenderSkeleton并为各个连接编写惟一的文件来创建自定义日志附加器就像使用变量文件名执行标准文件I/O一样简单。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|299460|entityMap|0|LINK|mutability|MUTABLE|url|http://logging.apache.org/log4j/index.html|1|http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/AppenderSkeleton.html^0|D|C|0|W|G|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

If you're using <a href="http://logging.apache.org/log4j/index.html" rel="nofollow">Apache log4j</a>, which I highly recommend, create a custom logging appender by extending <a href="http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/AppenderSkeleton.html" rel="nofollow">AppenderSkeleton</a> and writing unique files for individual connections will be as simple as doing standard file I/O with a variable filename.

blocks|key|4035455|text|如果您使用的是java.util.logging，请查看Handler+base+class；如果您使用的是log4j，请查看Appender。在这两种情况下，您都需要以某种方式获取与消息相关联的IMEI，以便编写日志消息的代码可以选择适当的文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4035456|有两种方法可以做到这一点。|4035457|第一个是扩展日志事件类(分别是LogRecord或LoggingEvent+)。这将允许您使用包含IMEI的事件进行记录。然而，这不考虑在与设备执行对话时由其他库等执行的日志记录。|4035458|另一种选择是使用ThreadLocal。每当您收到消息或正在制定消息时，设置与套接字关联的IMEI。确保日志记录发生在同一线程中，并且所有排队都在日志处理程序/附加器上完成。如果您不熟悉此方法，请查找/询问有关ThreadLocals的问题。我相信Log4J的NDC和MDC实现了这种策略，但我没有尝试在附加器中进行专门的上下文处理。|4035459|最后，请注意，如果您确实在考虑保持“数千”个日志文件处于打开状态，则某些操作系统将耗尽文件句柄。根据文件的数量，您可能需要考虑将日志消息(使用IMEI)写入数据库，或者执行某种基于LRU的文件关闭。在后一种情况下，对于一段时间内未被访问的日志文件，您基本上没有文件句柄。|4035460|entityMap|0|LINK|mutability|MUTABLE|url|http://download.oracle.com/javase/6/docs/api/java/util/logging/Handler.html|1|http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Appender.html|2|http://download.oracle.com/javase/6/docs/api/java/util/logging/LogRecord.html|3|http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/spi/LoggingEvent.html|4|http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/NDC.html|5|http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/MDC.html^0|7|H|S|7|1R|8|S|I|0|1R|8|1|0|0|F|9|P|C|F|9|2|P|C|3|0|3M|3|3Q|3|3M|3|4|3Q|3|5|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]|$9|1A|A|1B|B|C]]|D|@$9|1C|A|1D|1|1E]|$9|1F|A|1G|1|1H]]|E|$]]|$1|F|3|G|5|6|7|1I|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1J|8|@$9|1K|A|1L|B|C]|$9|1M|A|1N|B|C]]|D|@$9|1O|A|1P|1|1Q]|$9|1R|A|1S|1|1T]]|E|$]]|$1|J|3|K|5|6|7|1U|8|@$9|1V|A|1W|B|C]|$9|1X|A|1Y|B|C]]|D|@$9|1Z|A|20|1|21]|$9|22|A|23|1|24]]|E|$]]|$1|L|3|M|5|6|7|25|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|26|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U]]|V|$5|Q|R|S|E|$T|W]]|X|$5|Q|R|S|E|$T|Y]]|Z|$5|Q|R|S|E|$T|10]]|11|$5|Q|R|S|E|$T|12]]|13|$5|Q|R|S|E|$T|14]]]]

If you are using <code>java.util.logging</code>, look at the <a href="http://download.oracle.com/javase/6/docs/api/java/util/logging/Handler.html" rel="nofollow"><code>Handler</code> base class</a>, if you are using log4j, look at <a href="http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Appender.html" rel="nofollow"><code>Appender</code></a>. In both cases, you need to somehow get the IMEI associated with the message, so the code writing the log message can pick the appropriate file.

There are two approaches to doing this.

First is to extend the log event class (<a href="http://download.oracle.com/javase/6/docs/api/java/util/logging/LogRecord.html" rel="nofollow"><code>LogRecord</code></a> or <a href="http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/spi/LoggingEvent.html" rel="nofollow"><code>LoggingEvent</code></a> respectively). This would allow you to log using your event, which contains the IMEI. However, this does not account for logging performed by other libraries etc while performing the conversation with a device. 

The other alternative is to use a ThreadLocal. Set the IMEI associated with a socket whenever you receive a message or are formulating message. Make sure that the logging happens in the same thread, and any queuing is done at the log handler/appender. Look for / ask questions about ThreadLocals if you are unfamiliar with this approach. I believe that Log4J's <a href="http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/NDC.html" rel="nofollow"><code>NDC</code></a> and <a href="http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/MDC.html" rel="nofollow"><code>MDC</code></a> implements this sort of strategy, but I've not tried to do specialized processing of context at the appender.

Finally, be aware some operating systems will run out of file handles if you are indeed thinking of keeping "thousands" of log files open. Depending on just how many files, you may want to consider writing log messages (with IMEI) to a database, or doing some sort of LRU-based file closing. In the latter, you would basically not have file handles for log files that haven't been touched in a while.

I was just wondering if following thing exists.

I have a TCP communicator which keeps communicating with thousands of devices. 

Currently, the TCP communicator logs all the events in one log file. 

Now, is it possible to log communication with every device in different files. The IMEI number of every device is different. So the logger will check if a file with name equal to the IMEI number of the device exists. If the file exists, logger will start logging events of the device in that file, otherwise it will create a new file with IMEI as the file's name and start logging the events in that file.

(We are developing our application in Java.)

Implementing logging

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我只是想知道下面的东西是否存在。我有一个TCP通信器，它可以与成千上万的设备保持通信。目前，TCP通信器将所有事件记录在一个日志文件中。现在，是否可以将与每个设备的通信记录在不同的文件中。每个设备的IMEI编号是不同的。因此，记录器将检查是否存在名称等于设备的IMEI编号的文件。如果该文件存在，logger将开始在该文件中记录设备的事件，否则它将创建一个以IMEI作为文件名的新文件，并开始在该文件

问实现日志记录
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问实现日志记录EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问实现日志记录
EN