You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by GitBox <gi...@apache.org> on 2019/03/05 11:40:06 UTC

[GitHub] [brooklyn-docs] tbouron commented on a change in pull request #279: Update docs to describe log4j setup

tbouron commented on a change in pull request #279: Update docs to describe log4j setup
URL: https://github.com/apache/brooklyn-docs/pull/279#discussion_r262460442
 
 

 ##########
 File path: guide/ops/logging.md
 ##########
 @@ -8,40 +8,29 @@ Brooklyn uses the SLF4J logging facade, which allows use of many popular framewo
 The convention for log levels is as follows:
 
 * `ERROR` and above:  exceptional situations which indicate that something has unexpectedly failed or
-some other problem has occured which the user is expected to attend to
+some other problem has occurred which the user is expected to attend to
 * `WARN`:  exceptional situations which the user may which to know about but which do not necessarily indicate failure or require a response
 * `INFO`:  a synopsis of activity, but which should not generate large volumes of events nor overwhelm a human observer
 * `DEBUG` and lower:  detail of activity which is not normally of interest, but which might merit closer inspection under certain circumstances.
 
 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]({{book.path.docs}}/dev/tips/logging.md#osgi-based-apache-brooklyn) <br/>
-[https://ops4j1.jira.com/wiki/display/paxlogging/Configuration](https://ops4j1.jira.com/wiki/display/paxlogging/Configuration)
-
+The default logging is to write INFO+ messages to `amp.info.log`, 
+and DEBUG+ to `amp.debug.log`. Each is a rolling log file, 
 
 Review comment:
   Should say `brooklyn.debug.log`

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services