https://bugs.openldap.org/show_bug.cgi?id=10293
Issue ID: 10293 Summary: Log operations generated by syncrepl at STATS level Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: slapd Assignee: bugs@openldap.org Reporter: nivanova@symas.com Target Milestone: ---
Similarly to how incoming operations are logged, operations created by syncrepl should be logged as well.
https://bugs.openldap.org/show_bug.cgi?id=10293
--- Comment #1 from Quanah Gibson-Mount quanah@openldap.org --- Why? we already have "sync" log level for this.
https://bugs.openldap.org/show_bug.cgi?id=10293
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED Keywords|needs_review |
--- Comment #2 from Quanah Gibson-Mount quanah@openldap.org ---
*** This issue has been marked as a duplicate of issue 9886 ***
https://bugs.openldap.org/show_bug.cgi?id=10293
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED
https://bugs.openldap.org/show_bug.cgi?id=10293
--- Comment #3 from mheyman@symas.com mheyman@symas.com --- The current implementation of syncrepl operation logging should be updated to make the logging outut formatted the same as normal operations. Customers using data reduction tools like Splunk and DataDog expect regular and easily processed formats and this implementation is neither. Furthermore the splitting of the name of the verb being sent and the etime makes processing complex in geneeral.
To this end I asked @nivanova to to an implementation. It was completed and demonstrates the attributes I asked for. It would dramatically simplify the postprocessing of logs to better understand the overall load on consumer instances.
-
openldap-its＠openldap.org