#47751 make replication logging cofigurable per agreement/session
Closed: wontfix by mreynolds. Opened by tbordaz.

When enabling a error log level it could be useful to see which thread is logging a specific message.

This change of log format will likely require an new flag in the config

It could be done in vslapd_log_error:

PRThread *thr = PR_GetCurrentThread();
PRUint32 tid = PR_GetThreadID(thr);
sprintf(buffer, "...(tid %u) - ", ..., tid);

The inclusion of the thread ID is one possibility to filter replication logging for a specific agreement or replication session. We should go further and allow finer graine replication logging
per replica
per role (supplier/consumer)
per agreement

Per triage, push the target milestone to 1.3.6.

Metadata Update from @nhosoi:
- Issue assigned to lkrispen
- Issue set to the milestone: 1.3.6.0

Metadata Update from @mreynolds:
- Issue close_status updated to: None
- Issue set to the milestone: 1.4 backlog (was: 1.3.6.0)

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None
- Issue tagged with: RFE

Closing this ticket as a duplicate of https://pagure.io/389-ds-base/issue/50187

Metadata Update from @mreynolds:
- Issue close_status updated to: duplicate
- Issue status updated to: Closed (was: Open)

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/1083

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 (was: duplicate)

Metadata