The sample log4j.xml file below shows how to enable Perf4J appenders for JMX.
下面的log4j . xml文件示例显示了如何启用用于JMX的Perf 4 jappender ？
It contains a hierarchy object plus data necessary for the custom appenders as shown in Listing 2.
该管理器包含一个hierarchy对象，以及定制appenders所需的数据，如清单2所示。
This mock logger sends its output to System.out instead of to any of the defined log4j appenders.
这个模拟记录器将它的输出发送到System . out而不是任何已定义的log4j输出器。
Much of Perf4J's extended functionality is made available through a set of custom log4j appenders.
Perf4J的扩展功能大部分通过一套定制的log4j appender提供。
As you can see in Listing 7, there are two appenders defined: the appender A1 is a PluginFileAppender and assigned to the root logger.
正如您在清单7中看到的一样，我们定义了两个appender：appender a 1是一个pluginfileappender类，它被分配给根记录器。
Runtime verbosity control: the verbosity level of log4j loggers and appenders can be configured at start time and then modified at run time.
运行时冗长控制：log4j记录程序和附加程序的冗长等级可以在系统启动时配置，并随后在运行时修改。
File needs to be on the classpath to specify the appenders to use, which is done here by adding a folder to the application server's classpath. To do this.
请注意，Log4J. properties文件需要在类路径上，以指定要使用的搜索路径，这里是通过向应用程序服务器的类路径添加文件夹来实现的。
You can then configure its output through the same property file; you only need to specify the Logger name and filter it, add appenders, etc. The class is shown in Listing 6.
然后您可以通过相同的配置文件对输出结果进行配置；只需指定记录器的名字、设置过滤条件、添加appender即可。
In addition to the JMX appender, Perf4J also provides graphing appenders that generate performance graphs that can be exposed through a web front-end using a Perf4J graphing servlet.
除了JMX插件，Perf4J也支持生成性能图表的画图appender，使用前端的Perf 4j画图servlet。
This is needed so that when the plug-in stops, it will be possible to shut down all the hierarchies and allow the appenders and loggers to be correctly removed as you can see in Listing 5.
这是必需的，这样，在插件停止时，就可以关闭该插件的所有层次结构，并正确删除appender和记录器，如清单 5 所示。
This is needed so that when the plug-in stops, it will be possible to shut down all the hierarchies and allow the appenders and loggers to be correctly removed as you can see in Listing 5.
这是必需的，这样，在插件停止时，就可以关闭该插件的所有层次结构，并正确删除appender和记录器，如清单 5 所示。
应用推荐