#4318 [RFE] Allow managing DS log level from UI/CLI
Closed: wontfix 5 years ago Opened 9 years ago by dpal.

Expose capability to change DS log level in UI and CLI. See http://port389.org/wiki/FAQ#Troubleshooting for details.

Would be nice to be able to do it per server but probably in future via the topology tool we have in mind.


It would be good to know what are the real audit requests. Turning on some of the debug log levels gives tons of information and could make the server unusable in a production environment.
The most relevant information is in the access log (who did bind and perform which operations) and the audit log (log all the changes), but if this is not enough, then we probably need new logging features

Replying to [comment:1 lkrispen]:

It would be good to know what are the real audit requests. Turning on some of the debug log levels gives tons of information and could make the server unusable in a production environment.
The most relevant information is in the access log (who did bind and perform which operations) and the audit log (log all the changes), but if this is not enough, then we probably need new logging features

I think this is enough and this is what the user was looking for to be able to turn on. Sorry if I was not clear. Feel free to change the bug description to match this use case.

Given the discussion, moving to Ticket Backlog as it is not a priority.

Metadata Update from @dpal:
- Issue assigned to someone
- Issue set to the milestone: Ticket Backlog

7 years ago

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

Given that we are unable to fulfil this request I am closing the issue as wontfix. To request re-consideration of this decision please reopen this issue and provide additional technical details about its importance to you.

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

5 years ago

Login to comment on this ticket.

Metadata