[
https://issues.apache.org/jira/browse/DIRSERVER-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-1637:
-----------------------------------------
Component/s: monitoring
logs
> Create generic loggers for common operations like Replication, Protocol,
> Store...
> ---------------------------------------------------------------------------------
>
> Key: DIRSERVER-1637
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1637
> Project: Directory ApacheDS
> Issue Type: Improvement
> Components: logs, monitoring
> Affects Versions: 2.0.0-M1
> Reporter: Emmanuel Lecharny
> Priority: Major
> Fix For: 2.1.0
>
>
> It would be very convenient if we can have some loggers not directly
> associated with classes, but with operations.
> For instance, I'd like to have a log containing everything related to
> replication, whatever class is dealing with that. Same for the LDAP protocol
> handling, etc.
> Some possible categories could be :
> PROTOCOL : logs every operation received and sent
> STORE : logs every modification done on the backend
> SESSION : stores any session modifications (opening, closing, ldap request)
> ACI : stores any ACI decision taken
> REPLICATION : stores anything related to replication
> KERBEROS : stores anything related to Kerberos
> TRIGGERS : stores anything related to triggers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
