This is an automated email from the ASF dual-hosted git repository.
andy pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/jena-site.git
The following commit(s) were added to refs/heads/main by this push:
new 2366a8f0e Format block. Link to fuseki-logging
2366a8f0e is described below
commit 2366a8f0e584df6f61f57f4064704668b3f5025a
Author: Andy Seaborne <[email protected]>
AuthorDate: Wed Aug 28 18:45:12 2024 +0100
Format block. Link to fuseki-logging
---
source/documentation/fuseki2/fuseki-webapp.md | 4 +++
text-logging | 48 +++++++++++++++++++++++++++
2 files changed, 52 insertions(+)
diff --git a/source/documentation/fuseki2/fuseki-webapp.md
b/source/documentation/fuseki2/fuseki-webapp.md
index ab44f9a8f..37bc67c23 100644
--- a/source/documentation/fuseki2/fuseki-webapp.md
+++ b/source/documentation/fuseki2/fuseki-webapp.md
@@ -105,10 +105,12 @@ unpacked war file, e.g.
`/var/lib/tomcat9/webapps/fuseki/log4j2.properties`.
The name of the file is taken from `web.xml`:
+```xml
<context-param>
<param-name>log4jConfiguration</param-name>
<param-value>log4j2.properties</param-value>
</context-param>
+```
This only applies when running in a webapp container. When run from the command
line, the server looks for `log4j2.properties` in the current directory and if
@@ -116,6 +118,8 @@ not found, uses a built-in configuration.
This logging goes to the standard output.
+See also [Fuseki Logging](./fuseki-logging.html).
+
## Fuseki with Tomcat9 and systemd
`systemd` may be set to sandbox Tomcat9. The file area `/etc/fuseki` will not
diff --git a/text-logging b/text-logging
new file mode 100644
index 000000000..8aedc97ee
--- /dev/null
+++ b/text-logging
@@ -0,0 +1,48 @@
+merge with fuseki2/fuseki-logging.md
+
+### Fuseki loggers
+
+| Logger | Usage |
+| ------- | ----- |
+| Fuseki | The action log used for all endpoint requests |
+| Server | Server information |
+| Admin | Server administration operations |
+| Config | Dataset build/configuration log |
+| Request | NCSA [Common Log
Format](https://en.wikipedia.org/wiki/Common_Log_Format) |
+| Backup | Log for backup tasks |
+| riot | Uploaded data parse errors |
+
+Parse errors for uploaded data go to the logger `org.apache.jena.riot`
+
+The full name used in the logging provider setup is
+of the form <code>org.apache.jena.fuseki.<i><NAME></i>
+except for `org.apache.jena.riot`.
+
+Logging default to level `INFO`.
+
+Any externally set logging setup takes precidence over the Fuseki default
+logging configuration.
+
+#### Server packaging
+
+Logging goes to stderr.
+
+The logging pattern is `%d{HH:mm:ss} %-5p %-15c{1} :: %m%n`.
+
+#### webapp (WAR file) packaging
+
+Logging goes to stdout.
+
+The logging pattern is `[%d{yyyy-MM-dd HH:mm:ss}] %-10c{1} %-5p %m%n`.
+
+#### Embedded mode:
+
+The default for logging is silent. To instead use the Fuseki setup, call
+`FusekiLogging.setLogging();` before any jena code is called. Then
+logging is the same as the server packaging.
+
+### `Request` log
+
+In all cases, the `Request` uses the plain pattern `%m%n` and the format
+follows the [Common Log
Format](https://en.wikipedia.org/wiki/Common_Log_Format)
+used by many log analysis tools. The log defaults to `OFF`.
