From 4c1828438e7933310ab868d66a9dbfef04a2156c Mon Sep 17 00:00:00 2001 From: Alexey Venderov Date: Thu, 25 Apr 2024 11:03:57 +0200 Subject: [PATCH] Fix javadoc link to include module name (#1292) --- docs/src/main/paradox/typed/logging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/main/paradox/typed/logging.md b/docs/src/main/paradox/typed/logging.md index 44e04be4125..3531c8213e9 100644 --- a/docs/src/main/paradox/typed/logging.md +++ b/docs/src/main/paradox/typed/logging.md @@ -199,7 +199,7 @@ A starting point for configuration of `logback.xml` for production: @@snip [logback.xml](/actor-typed-tests/src/test/resources/logback-doc-prod.xml) -Note that the [AsyncAppender](https://logback.qos.ch/apidocs/ch/qos/logback/classic/AsyncAppender.html) may drop log events if the queue becomes full, which may happen if the +Note that the [AsyncAppender](https://logback.qos.ch/apidocs/ch.qos.logback.classic/ch/qos/logback/classic/AsyncAppender.html) may drop log events if the queue becomes full, which may happen if the logging backend can't keep up with the throughput of produced log events. Dropping log events is necessary if you want to gracefully degrade your application if only your logging backend or filesystem is experiencing issues.