Repository: brooklyn-docs
Updated Branches:
  refs/heads/master 0ca3f6e74 -> aedfae2a1


Configuring logging from karaf distribution of Apache Brooklyn


Project: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/commit/6e59fe15
Tree: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/tree/6e59fe15
Diff: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/diff/6e59fe15

Branch: refs/heads/master
Commit: 6e59fe1597a23eca9b5e8141ae6d432c6f14bd91
Parents: 0ca3f6e
Author: Valentin Aitken <[email protected]>
Authored: Thu Jan 26 13:34:52 2017 +0200
Committer: Valentin Aitken <[email protected]>
Committed: Fri Jun 23 16:29:41 2017 +0300

----------------------------------------------------------------------
 guide/dev/tips/logging.md | 30 ++++++++++++++++++++++++++----
 guide/ops/logging.md      |  8 ++++++++
 2 files changed, 34 insertions(+), 4 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/6e59fe15/guide/dev/tips/logging.md
----------------------------------------------------------------------
diff --git a/guide/dev/tips/logging.md b/guide/dev/tips/logging.md
index 7c4543c..a6e9a71 100644
--- a/guide/dev/tips/logging.md
+++ b/guide/dev/tips/logging.md
@@ -11,6 +11,28 @@ with a default configuration which just works out of the box
 and bindings to the other common libraries (``java.util.logging``, ``log4j``, 
...)
 if you prefer one of those.
 
+
+### OSGi based Apache Brooklyn
+
+While developing it may be useful to change logging level of some of the 
Apache Brooklyn modules.
+The easiest way to do that is via the karaf console which can be started by 
`bin/client`.
+(Details regarding using [Apache Brooklyn Karaf 
console](../../blueprints/java/bundle-dependencies.html#karaf-console))
+For example if you would like to inspect jclouds API calls, enable 
jclouds.wire logging just enable it from karaf client.
+
+    log:set DEBUG jclouds.wire
+
+To check other log levels.
+
+    log:list
+
+If for some reason log level needs modified before the first start of Karaf
+then you can modify the config file `etc/org.ops4j.pax.logging.cfg` before 
hand.
+For more information check
+[https://ops4j1.jira.com/wiki/display/paxlogging/Configuration](https://ops4j1.jira.com/wiki/display/paxlogging/Configuration).
+
+
+### Classic - non-OSGI based Apache Brooklyn
+
 To use:
 
 * **Users**:
@@ -25,7 +47,7 @@ and then to put custom logging configuration in either 
``logback-custom.xml`` or
 as described below.
 
 
-## Customizing Your Logging
+#### Customizing Your Logging
 
 The project ``brooklyn-logback-xml`` supplies a ``logback.xml`` configuration,
 with a mechanism which allows it to be easily customized, consumed, and 
overridden.
@@ -82,7 +104,7 @@ You can set a specific logback config file to use with:
 {% endhighlight %}
 
 
-## Assemblies
+#### Assemblies
 
 When building an assembly, it is recommended to create a ``conf/logback.xml`` 
which 
 simply includes ``logback-main.xml`` (which comes from the classpath).  Users 
of the assembly
@@ -99,7 +121,7 @@ logging categories and define the log file name) and it 
should get picked up,
 both in the IDE and in the assembly.   
  
 
-## Tests
+#### Tests
 
 Brooklyn projects ``test`` scope includes the ``brooklyn-utils-test-support`` 
project
 which supplies a ``logback-test.xml``. logback uses this file in preference to 
``logback.xml``
@@ -112,7 +134,7 @@ The only differences of the ``logback-test.xml`` 
configuration is that:
 * The log file is called ``brooklyn-tests.log`` 
 
 
-## Caveats
+#### Caveats
 
 * logback uses SLF4J version 1.6 which is **not compatible** with 1.5.x. 
   If you have dependent projects using 1.5.x (such as older Grails) things may 
break.

http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/6e59fe15/guide/ops/logging.md
----------------------------------------------------------------------
diff --git a/guide/ops/logging.md b/guide/ops/logging.md
index 81d55e9..5fc1a3b 100644
--- a/guide/ops/logging.md
+++ b/guide/ops/logging.md
@@ -17,6 +17,14 @@ some other problem has occured which the user is expected to 
attend to
 Loggers follow the ``package.ClassName`` naming standard.  
 
 
+## Using Logback through OSGi Pax Logging
+
+In the OSGi based Apache Brooklyn logging is configured from ops4j pax logging.
+
+See: [Logging - OSGi based Apache 
Brooklyn](../dev/tips/logging.html#osgi-based-apache-brooklyn) <br/>
+[https://ops4j1.jira.com/wiki/display/paxlogging/Configuration](https://ops4j1.jira.com/wiki/display/paxlogging/Configuration)
+
+
 ## Standard Configuration
 
 A `logback.xml` file is included in the `conf/` directly of the Brooklyn 
distro;

Reply via email to