This is an automated email from the ASF dual-hosted git repository.
heneveld pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git
The following commit(s) were added to refs/heads/master by this push:
new 6c443c1 update docs per brooklyn-server#1227
6c443c1 is described below
commit 6c443c10cc2dcb780c241ff598e4cf1cabbf1779
Author: Alex Heneveld <[email protected]>
AuthorDate: Mon Aug 23 09:03:09 2021 +0100
update docs per brooklyn-server#1227
---
guide/ops/logging.md | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/guide/ops/logging.md b/guide/ops/logging.md
index 072280a..ff881c3 100644
--- a/guide/ops/logging.md
+++ b/guide/ops/logging.md
@@ -86,11 +86,14 @@ The logbook offers the possibility to query and view logs
in the UI. By default,
in `etc/org.ops4j.pax.logging.cfg`. The logbook can be configured against
different log aggregation sources by setting the
`brooklyn.logbook.logStore` parameter in `brooklyn.cfg`, and depending which
backend is used, other parameters.
-For example to use the local log files written by Apache Brooklyn, assuming
`/var/logs`, you could configure (note these are the default values):
+For example to use the local log files written by Apache Brooklyn in a
production environment, assuming `/var/logs`,
+you could configure:
brooklyn.logbook.logStore=org.apache.brooklyn.util.core.logbook.file.FileLogStore
brooklyn.logbook.fileLogStore.path=/var/logs/brooklyn/brooklyn.debug.log
+The default mode is to use the local log file in `data/log/` relative to the
launch directory.
+
In production environments where log data is desired to be retained, Apache
Brooklyn supports Elasticsearch backends.
This can be a dedicated ES environment for use by Apache Brooklyn or a
shared/managed ES facility that handles many logs,
or -- for lightweight usage -- a simple local ES server running on the same
instance as Apache Brooklyn.
