#50223 need a uniq identifier for each DS error message
Closed: wontfix 4 months ago by spichugi. Opened 2 years ago by tbordaz.

Issue Description

DS can log many messages. Sometime they look similar and we need to grep into the code to understand where/why it happened.

Having a unique identifier would accelerate the diagnostic

Package Version and Platform

All version

Steps to reproduce

NA

Actual results

- INFO - PBKDF2_SHA256 - Based on CPU performance, chose 2048 rounds

Expected results

- INFO - ISEC809 - PBKDF2_SHA256 - Based on CPU performance, chose 2048 rounds

@tbordaz I already started to work on something similar for lib389 to use this. It would be great to have something like this. I would suggest we make a new log interface (slapi_log_id_err), and then start to use that where it takes a char *id. We can then add a deprecation tag to the slapi_log_err function, and start to move people away from it.

Metadata Update from @firstyear:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

2 years ago

@firstyear that looks a good idea. I have also concerns about customer existing scripts that use to catch some messages. We should have a toggle to keep the old logging way even if by default we would start logging with an ID.

It worth a small design IMHO

I don't think there shoulid be a toggle. We need to remove options, not add more. I think we should feature gate it IE a compile definition for inclusion, but then opting to using this as the default and only option.

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

2 years ago

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.1

2 years ago

Metadata Update from @mhonek:
- Issue set to the milestone: None (was: 1.4.1)
- Issue tagged with: RFE

2 years ago

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.1

2 years ago

Metadata Update from @mreynolds:
- Issue priority set to: minor
- Issue set to the milestone: 1.4.4 (was: 1.4.1)

11 months ago

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

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)

4 months ago

Login to comment on this ticket.

Metadata