GitHub user ppkarwasz added a comment to the discussion: Adding a Routing Filter to log4j2
Hi @mlangc, Thank you for sharing this with us! > Would it make sense to have such a filter in mainline Log4j2? It’s a bit early to say. At the moment, we only add plugins to the Log4j distribution once they have demonstrated long-term stability and are adopted by a broad user base. New plugins typically go through a “ramp-up” phase before reaching that point: * They are listed on our website as **third-party components**, making them easier for users to discover and experiment with. For example, see my own [Tomcat Lookup](https://logging.apache.org/log4j/2.x/manual/lookups.html#third-party). * If a component gains noticeable community interest, for instance, through downloads, GitHub stars, or feedback, we may consider integrating it into Log4j Core, which effectively means committing to maintaining it for the next **decade or more**. Here’s what I’d suggest as next steps: 1. Publish your plugin on Maven Central, so that users can easily consume it. 2. Provide clear documentation, which you’ve already done a great job with. 3. Open a PR updating our [Filters page](https://github.com/apache/logging-log4j2/blob/2.x/src/site/antora/modules/ROOT/pages/manual/filters.adoc) to include: * A new “**Third-party filters**” section (below “Collection”) with a brief disclaimer explaining that these filters are not part of the official distribution (yet). * A short subsection about your filter, including a link to your documentation and repository. This way, your work becomes visible to the community and can start building traction, which is exactly what we look for before considering inclusion in Log4j. GitHub link: https://github.com/apache/logging-log4j2/discussions/3976#discussioncomment-14845384 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
