#2808 Replace hexadecimal debug level code in log messages with a text tag
Closed: wontfix 10 months ago by pbrezina. Opened 5 years ago by sbose.

Currently a log message of SSSD like e.g.

(Mon Jun 29 22:10:59 2015) [sssd[be[lab.runlevelone.lan]]] [be_get_account_info] (0x0200): Got request for [0x1001][1][name=dlavu]

has the debug level given by '(0x0200)'. For the inexperienced reader it is hard to see if the message indicates an error or is only some informational messages.

It would be good to replace them which short text tags which better indicates the character and severity of the message. E.g. something like ERR_CRIT, INFO_DATA, TRACE_FUNC ...


Fields changed

owner: somebody => pcech

Fields changed

rhbz: => 0

I think this would be nice to have in 1.13.3. Downstreams and people who support them would really benefit from this.

One issue that I realized is that we might want to add the string representation in addition to hexa to avoid breaking existing scripts. But on the other hand, I'm not sure if we should care too much about keeping compatibility of debug logs..

I use very often hexadecimal representation for filtering huge log file. So it should not be replaced.
It's much simpler (and shorter) to write regex for hexadecimal numbers.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13.3

Fields changed

status: new => assigned

Fields changed

patch: 0 => 1

It seems that at first we do #1372 and then we could do this ticket. There is discuss about it on mailing list.

Yes and since #1372 might be quite big, I think we might want to move both to 1.14 alpha. If the changes are digestable for 1.13 as well, we can push to the stable branch, too, but I would decide that when the patches are available.

This ticket still needs work and we need to release 1.13.3 soon.

milestone: SSSD 1.13.3 => SSSD 1.14 alpha

The 1.14 Alpha release should be small and targeted at stabilizing the refactoring and important fixes, therefore I'm demoting this ticket to the Beta milestone.

milestone: SSSD 1.14 alpha => SSSD 1.14 beta

This ticket still needs work and we need to release 1.14 beta soon.

milestone: SSSD 1.14 beta => SSSD 1.15 beta

Fields changed

status: assigned => new

Metadata Update from @sbose:
- Issue assigned to pcech
- Issue set to the milestone: SSSD Future releases (no date set yet)

3 years ago

Metadata Update from @thalman:
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch adjusted to on (was: 1)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: Canditate to close

10 months ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

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

10 months ago

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

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/3849

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.

Login to comment on this ticket.

Metadata