Bug 56826 - Provide reference about log files in UCS
Provide reference about log files in UCS
Status: NEW
Product: UCS manual
Classification: Unclassified
Component: General
unspecified
Other Linux
: P5 normal (vote)
: ---
Assigned To: Docu maintainers
Docu maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2023-11-15 11:03 CET by Nico Gulden
Modified: 2023-11-16 09:06 CET (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.069
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): External feedback
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nico Gulden univentionstaff 2023-11-15 11:03:55 CET
Add a reference about relevant log files in UCS and provide links to the respective section talking about the service.

As an administrator I want to quickly find the log file that I need to consult to find logging information about a specific service to troubleshot a problem I have.

The reference summary should include the following information:

* Path and filename
* What service uses that log file
* How to change the log level for that file
* Links to the sections that describe or mention the log file
Comment 3 Daniel Tröder univentionstaff 2023-11-16 09:06:22 CET
In the past, the developers talked about this - for developers.
In each "project" (can be a package or repo) there should be a README with the information needed to maintain the project. That includes the log files it generates.
Unfortunately, this has not become the norm.

I like the idea of having central documentation for operators to search for log files and log settings.

But a centralized structure is not good for developers to keep updated.
1. Software changes in one repository, and the documentation is in another repo.
2. New software is created every week. Developers have to remember about this separate docu repo.

Could we have something like the following?
A template (.rst, .json or .py file) exists in each git repo, possibly in subdirectories (Debian packages). The path to it is included in the repo for this documentation. The CI collects the files and assembles the doc.
The template contains a table/structure with the information required (path, service, log level, further docs).

Problem with the idea: Again the link to this template must be added manually to the central place. It would be nicer if that could be done automagically from the CI in the source repos.