From 4b3d1e700d308cec046fe4ffb59341d013464775 Mon Sep 17 00:00:00 2001
From: Mark Craig <mark.craig@forgerock.com>
Date: Fri, 14 Oct 2011 13:35:03 +0000
Subject: [PATCH] OPENDJ-308: Implement access log filtering and configurable message format
---
opendj3/src/main/docbkx/admin-guide/chap-monitoring.xml | 13 +++++++++++++
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/opendj3/src/main/docbkx/admin-guide/chap-monitoring.xml b/opendj3/src/main/docbkx/admin-guide/chap-monitoring.xml
index ffb2a17..4f5db8f 100644
--- a/opendj3/src/main/docbkx/admin-guide/chap-monitoring.xml
+++ b/opendj3/src/main/docbkx/admin-guide/chap-monitoring.xml
@@ -346,6 +346,9 @@
search was indexed)</para>
</listitem>
<listitem>
+ <para>Target DN</para>
+ </listitem>
+ <listitem>
<para>Type of operation (connect, bind, add, delete, modify, rename,
search, etc.)</para>
</listitem>
@@ -400,6 +403,16 @@
<para>At this point, OpenDJ filters out connections over LDAPS to port
4444.</para>
</example>
+
+ <para>In addition to the filtering policy, you can also adjust how OpenDJ
+ writes log messages. By default, OpenDJ writes one log message for a
+ request, and another for a response. You can set the log publisher
+ property <literal>log-format</literal> to <literal>combined</literal>
+ to have OpenDJ write a single message per operation. This can be helpful,
+ for example, when evaluating response times. In addition, you can change
+ the log message time stamps with <literal>log-record-time-format</literal>,
+ and specify whether to log LDAP control OIDs for operations by setting
+ <literal>log-control-oids</literal> to <literal>true</literal>.</para>
</section>
</section>
--
Gitblit v1.10.0