Bug 2207823

Summary: There is no documentation on how to reset journald logging back to default
Product: Red Hat Satellite Reporter: Alexey Masolov <amasolov>
Component: InstallerAssignee: Aneta Šteflová Petrová <apetrova>
Status: CLOSED CURRENTRELEASE QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.13.0CC: agadhave, ehelms, mjivraja
Target Milestone: UnspecifiedKeywords: Documentation, Triaged
Target Release: UnusedFlags: mdolezel: needinfo? (mjivraja)
mdolezel: needinfo? (agadhave)
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-04 12:08:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alexey Masolov 2023-05-17 03:46:43 UTC
Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/administering_red_hat_satellite/index#Configuring_Logging_to_Journal_admin

Section Number and Name: 
17.6. Configuring Logging to Journal

Describe the issue: 
There is no procedure on how to revert the change back to default.

Suggestions for improvement: 
satellite-installer \
--reset-foreman-logging-layout \
--reset-foreman-logging-level \
--reset-foreman-logging-type \
--reset-foreman-proxy-log


Additional information:

Comment 1 Marie Hornickova 2023-05-17 08:36:38 UTC
Hello Alexey,

Thank you very much for reporting this suggestion for improvement! 

The BZ will go through proper team triage and once the documentation is updated, the link will be shared in this ticket.

Thank you!

Comment 2 Aneta Šteflová Petrová 2023-07-06 10:42:21 UTC
PR submitted for review: https://github.com/theforeman/foreman-documentation/pull/2278

Comment 3 Aneta Šteflová Petrová 2023-07-24 12:24:29 UTC
Merged: https://github.com/theforeman/foreman-documentation/pull/2278#event-9899543107