docs: logger names are Fully Qualified Class Names (#1476)

This commit is contained in:
PJ Fanning 2024-09-12 11:51:12 +01:00 committed by GitHub
parent 09486097e7
commit ffb31daeca
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -452,7 +452,7 @@ troubleshooting. Those logger names are typically prefixed with the package name
For example, in Logback the configuration may look like this to enable debug logging for Cluster Sharding: For example, in Logback the configuration may look like this to enable debug logging for Cluster Sharding:
``` ```
<logger name="pekko.cluster.sharding" level="DEBUG" /> <logger name="org.apache.pekko.cluster.sharding" level="DEBUG" />
<root level="INFO"> <root level="INFO">
<appender-ref ref="ASYNC"/> <appender-ref ref="ASYNC"/>
@ -462,18 +462,18 @@ For example, in Logback the configuration may look like this to enable debug log
Other examples of logger names or prefixes: Other examples of logger names or prefixes:
``` ```
pekko.cluster org.apache.pekko.cluster
pekko.cluster.Cluster org.apache.pekko.cluster.Cluster
pekko.cluster.ClusterHeartbeat org.apache.pekko.cluster.ClusterHeartbeat
pekko.cluster.ClusterGossip org.apache.pekko.cluster.ClusterGossip
pekko.cluster.ddata org.apache.pekko.cluster.ddata
pekko.cluster.pubsub org.apache.pekko.cluster.pubsub
pekko.cluster.singleton org.apache.pekko.cluster.singleton
pekko.cluster.sharding org.apache.pekko.cluster.sharding
pekko.coordination.lease org.apache.pekko.coordination.lease
pekko.discovery org.apache.pekko.discovery
pekko.persistence org.apache.pekko.persistence
pekko.remote org.apache.pekko.remote
``` ```
## Logging in tests ## Logging in tests