This is an automated email from the ASF dual-hosted git repository.
jbertram pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/activemq-artemis.git
The following commit(s) were added to refs/heads/main by this push:
new bd925a7ea5 NO-JIRA clarify logging docs
bd925a7ea5 is described below
commit bd925a7ea55133559387a1c68ca38eedf2341911
Author: Justin Bertram <[email protected]>
AuthorDate: Thu Dec 7 22:40:38 2023 -0600
NO-JIRA clarify logging docs
---
docs/user-manual/logging.adoc | 2 +-
docs/user-manual/mqtt.adoc | 2 +-
docs/user-manual/stomp.adoc | 2 ++
3 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/docs/user-manual/logging.adoc b/docs/user-manual/logging.adoc
index 35720c1803..a4250bbef6 100644
--- 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
index 2adea4926a..f05e73d5bf 100644
--- 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
index 9c89bfec6d..ae18646295 100644
--- 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.
