389-ds-base

#50187 improve replication logging
Closed: wontfix by spichugi. Opened by lkrispen.

Closed: wontfix
Reopen Issue

Issue Description

The replication logging is very valuable for debugging replication, but the amount of logging can be massive and it can be difiicult to find the relevant information, especially if there are multiple replicas and replication agreements.

I suggest the following enhancements:
- alllow logging only for a selected backend
- allow logging only for a selected replication agreement
- allow logging only for specific areas eg conflict resoultion, changelog processing. At least mark the logging for the subsystems clearly to be able to filter easily

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue set to the milestone: 1.4.1

Metadata Update from @mreynolds:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1684198

Issue linked to Bugzilla: Bug 1684198

Metadata Update from @mreynolds:
- Issue priority set to: normal
- Issue set to the milestone: 1.4.4 (was: 1.4.1)
- Issue tagged with: RFE

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/3246

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)
Metadata
None

RFE

None
None
High
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.