[
https://issues.apache.org/jira/browse/DIRSERVER-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633013#action_12633013
]
Emmanuel Lecharny commented on DIRSERVER-1186:
----------------------------------------------
So let's consider we add an LogInterceptro to trace every single request from
the user.
I don't think that a control is the appropriate way to handle this, as a
control is associated with a request, and is not perfectly suited to the
feature. I would rather use an extended request. For instance, we can have such
a grammar :
logOperations ::= SEQUENCE {
loggedOperations SEQUENCE {
operation Operation ;; From the LDAP protocol definition
logLevel ENUMERATED {
none (0),
error (1),
warning (2),
info (3),
debug (4),
trace (5)
}
}
}
Operation ENUMERATION {
bindRequest (0),
bindResponse (1),
unbindRequest (2),
searchRequest (3),
searchResEntry (4),
searchResDone (5),
searchResRef (6),
modifyRequest (7),
modifyResponse (8),
addRequest (9),
addResponse (10),
delRequest (11),
delResponse (12),
modDNRequest (13),
modDNResponse (14),
compareRequest (15),
compareResponse (16),
abandonRequest (17),
extendedReq (18),
extendedResp (19),
};
With that, you can set up Logs level for each operation, at will.
Then you have to be able to manage the Logger in a specific interceptor.
I think it's a good way to handle this feature.
> Trace control and request level logging
> ---------------------------------------
>
> Key: DIRSERVER-1186
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1186
> Project: Directory ApacheDS
> Issue Type: New Feature
> Affects Versions: 1.5.4
> Reporter: Alex Karasulu
> Fix For: 1.5.5
>
>
> Would be really nice to have a debug level control for tracing requests with
> different log levels. This way logging can be off for the whole system while
> turned on just to trace an issue with a specific request. Would also be nice
> to send back the logging information to the client in the response payload
> even on success some way.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
