NO-JIRA clarify logging docs

apache · Dec 8, 2023 · bd925a7 · bd925a7
1 parent b0545d9
commit bd925a7
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 2 deletions.
diff --git a/docs/user-manual/logging.adoc b/docs/user-manual/logging.adoc
@@ -41,7 +41,7 @@ Disabled by default
 Disabled by default
 |===
 
-== Activating TRACE for a specific logger
+== Configuring a Specific Level for a Logger
 
 Sometimes it is necessary to get more detailed logs from a particular logger.
 For example, when you're trying to troublshoot an issue.

diff --git a/docs/user-manual/mqtt.adoc b/docs/user-manual/mqtt.adoc
@@ -82,7 +82,7 @@ This feature can be useful in an IoT style scenario to detect errors across a po
 == Debug Logging
 
 Detailed protocol logging (e.g. packets in/out) can be activated by turning on `TRACE` logging for `org.apache.activemq.artemis.core.protocol.mqtt`.
-Follow xref:logging.adoc#activating-trace-for-a-specific-logger[these steps] to configure logging appropriately.
+Follow xref:logging.adoc#configuring-a-specific-level-for-a-logger[these steps] to configure logging appropriately.
 
 The MQTT specification doesn't dictate the format of the payloads which clients publish.
 As far as the broker is concerned a payload is just an array of bytes.

diff --git a/docs/user-manual/stomp.adoc b/docs/user-manual/stomp.adoc
@@ -37,6 +37,8 @@ Incoming and outgoing STOMP frames can be logged by enabling `DEBUG` for `org.ap
 This can be extremely useful for debugging or simply monitoring client activity.
 Along with the STOMP frame itself the remote IP address of the client is logged as well as the internal connection ID so that frames from the same client can be correlated.
 
+Follow xref:logging.adoc#configuring-a-specific-level-for-a-logger[these steps] to configure logging appropriately.
+
 == Routing Semantics
 
 The STOMP specification is intentionally ambiguous about message routing semantics.