activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jbert...@apache.org
Subject [activemq-artemis] branch master updated: NO-JIRA a few updates to the logging doc
Date Tue, 04 Aug 2020 16:22:07 GMT
This is an automated email from the ASF dual-hosted git repository.

jbertram pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/activemq-artemis.git


The following commit(s) were added to refs/heads/master by this push:
     new 92c4c65  NO-JIRA a few updates to the logging doc
92c4c65 is described below

commit 92c4c65d31e25b10a56f44d4705e4d3cdb9ab0c9
Author: Justin Bertram <jbertram@apache.org>
AuthorDate: Mon Aug 3 12:37:08 2020 -0500

    NO-JIRA a few updates to the logging doc
---
 docs/user-manual/en/logging.md | 43 ++++++++++++++++++++++++++++++++++--------
 1 file changed, 35 insertions(+), 8 deletions(-)

diff --git a/docs/user-manual/en/logging.md b/docs/user-manual/en/logging.md
index 4aaa26f..f640367 100644
--- a/docs/user-manual/en/logging.md
+++ b/docs/user-manual/en/logging.md
@@ -1,11 +1,10 @@
 # Logging
 
 Apache ActiveMQ Artemis uses the JBoss Logging framework to do its logging and is
-configurable via the `logging.properties` file found in the
-configuration directories. This is configured by Default to log to both
-the console and to a file.
+configurable via the `logging.properties` file found in the `etc` directory. This
+is configured by default to log to both the console and to a file.
 
-There are 9 loggers available which are as follows:
+There are a handful of general loggers available:
 
 Logger | Description
 ---|---
@@ -19,6 +18,34 @@ org.apache.activemq.audit.base|audit log. Disabled by default
 org.apache.activemq.audit.resource|resource audit log. Disabled by default
 org.apache.activemq.audit.message|message audit log. Disabled by default
 
+## Activating TRACE for a specific logger
+
+Sometimes it is necessary to get more detailed logs from a particular logger. For
+example, when you're trying to troublshoot an issue. Say you needed to get TRACE
+logging from the logger `org.foo`. First you would need to add `org.foo` to the
+`loggers` list at the top of `logging.properties`, e.g.:
+
+```
+loggers=...,org.foo
+```
+
+Then you need to configure the logging level for the `org.foo` logger to `TRACE`,
+e.g.:
+
+```
+logger.org.foo.level=TRACE
+```
+
+Lastly, you would need to update the `level` of the necessary `handler` to allow
+the `TRACE` logging through, e.g.:
+
+```
+handler.CONSOLE.level=TRACE
+```
+or
+```
+handler.FILE.level=TRACE
+```
 
 ## Logging in a client or with an Embedded server
 
@@ -30,12 +57,12 @@ the simplest way is to use the "all" client jar.
 <dependency>
    <groupId>org.jboss.logmanager</groupId>
    <artifactId>jboss-logmanager</artifactId>
-   <version>2.0.3.Final</version>
+   <version>2.1.10.Final</version>
 </dependency>
 <dependency>
    <groupId>org.apache.activemq</groupId>
-   <artifactId>activemq-core-client</artifactId>
-   <version>2.5.0</version>
+   <artifactId>activemq-core-client-all</artifactId>
+   <version>2.14.0</version>
 </dependency>
 ```
 
@@ -52,7 +79,7 @@ this is done via the `-Dlogging.configuration` for instance
 >
 > The `logging.configuration` system property needs to be valid URL
 
-The following is a typical `logging.properties for a client`
+The following is a typical `logging.properties` for a client
 
 ```
 # Root logger option


Mime
View raw message