vy commented on code in PR #3982:
URL: https://github.com/apache/logging-log4j2/pull/3982#discussion_r2503784184
##########
src/site/antora/antora.yml:
##########
@@ -51,6 +51,7 @@ asciidoc:
logging-services-url: "https://logging.apache.org";
lmax-disruptor-url: "https://lmax-exchange.github.io/disruptor/";
slf4j-url: "https://www.slf4j.org";
+ more-log4j2-url: "https://github.com/mlangc/more-log4j2";
Review Comment:
```suggestion
```
##########
src/site/antora/modules/ROOT/pages/manual/filters.adoc:
##########
@@ -1452,6 +1452,28 @@
include::example$manual/filters/ScriptFilter.properties[tag=global]
xref:plugin-reference.adoc#org-apache-logging-log4j_log4j-core_org-apache-logging-log4j-core-filter-ScriptFilter[📖
Plugin reference for `ScriptFilter`]
+[#third-party]
+== Third-party filters
+
+[IMPORTANT]
+====
+These filters are provided by **third-party** vendors and are not maintained
by the
+link:{logging-services-url}[Apache Logging Services]
+(Log4j, Log4cxx, Log4net) project.
+====
+
+=== Routing filter
+
+[cols="1h,4"]
+|===
+| Purpose | Routing messages to different filter chains
+| Dependency | {more-log4j2-url}[more-log4j2]
+| Use Cases | Marker or level based log throttling
+|===
+
+Sometimes xref:#CompositeFilter[composing filters sequentially] is not enough.
Using a `RoutingFilter`, different filter chains can be
+applied to log messages depending on their attributes.
Review Comment:
```suggestion
[WARNING]
====
These filters are provided by **third-party** vendors and are not maintained
by the link:{logging-services-url}[Apache Logging Services] project.
====
=== Routing filter (`more-log4j2`)
`RoutingFilter` by https://github.com/mlangc/more-log4j2[more-log4j2] helps
to compose filters by defining routes selected using log event attributes.
For instance, it can be used to implement log throttling based on log event
markers or levels.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
