SpringBoot项目log4j2.xml配置放到apollo是否支持？

[hongkuan45]

期望的用法是，在apollo创建一个namaspace （比如命名为log4j2.xml)。
启动项目指定apollo的log4j2.xml为日志配置文件。
以此做到在线化log配置。

此文做了自定义开发实现了相同的目的。想了解有没有更原生的方式。
https://blog.csdn.net/xiaokuanblog/article/details/123114628

[nisiyong]

We had supported this feature in our company.
I do this by log4j2 origin way, extend log4j2 org.apache.logging.log4j.core.config.ConfigurationFactory in the dependency module apollo-log4j2.

Usage

1) maven dependency

if someone want to manage log4j2.xml in apollo, they should add this dependency:

<dependency>
    <groupId>com.ctrip.framework.apollo</groupId>
    <artifactId>apollo-log4j2</artifactId>
</dependency>

2) create log4j2.xml namespace

3) enable this feature by system properties

-Dapollo.log4j2.enabled=true

Note: By default, it will load the local log4j2.xml in the classpath.

---

If anyone wants this feature, please comment on this issue. I think I could create a PR for this, we have already used this feature at least a year.

@nobodyiam I create an apollo-plugin module and put it in this.

[nisiyong]

Okay, I think we could kick off a new project to do this, and named it like apollo-plugins, apollo-extensions, or apollo-externals.

[nobodyiam]

That sounds like a great idea!

[nisiyong]

Which name do you prefer? I can create it in the next few days.

[Anilople]

How about refer to maven's plugins? https://mvnrepository.com/artifact/org.apache.maven.plugins

All maven plugin's parent is

  <parent>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-plugins</artifactId>
    <version>34</version>
    <relativePath/>
  </parent>

and their artifactId is maven-xxx-plugin, for example

<artifactId>maven-dependency-plugin</artifactId>

---

for the log4j2, can we use name convention like follow?

<dependency>
    <groupId>com.ctrip.framework.apollo</groupId>
    <artifactId>apollo-log4j2-plugin</artifactId>
</dependency>

and it's parent is

  <parent>
    <groupId>com.ctrip.framework.apollo</groupId>
    <artifactId>apollo-plugins</artifactId>
  </parent>

or other better name convention?

[nisiyong]

In my opinion, if we create a new repo to do this, it is not only plugin things.
We could put other third parties feature stuff in this repo, it is more like apollo-externals, inspired by this project rocketmq-externals.