theforeman / theforeman/foremanctl
How should logging be handled
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 27
- Forks
- 47
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 40
Description
This is to track how we should think about handling logging. The normal Foreman installation uses a variety of journal and independent log files across the various services. The cloud-native model is to log to stdout and let the container tooling incorporate that into the journal or whatever log driver is chosen.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reviewing how the normal Foreman installation and cloud-native model currently handle logs across services, then establish the project’s intended logging approach. Done means the logging behavior and ownership between services and container tooling are clearly decided.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100