[Feature Request]: Log management with Hop Docker
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 476
- Avg merge
- 18h 32m
- Merged PRs (30d)
- 216
Description
### What would you like to happen?
Currently the default behaviour in Hop Docker for the log trace is to create a new file /opt/hop/hop.err.log in the Docker environment. You can alternatively mount your log file from your external environment, but in this case the file is recreated at every launch, causing the log history to be deleted.
There are cases in which this scenario is undesirable, so some improvements to the log management can be:
- append the log trace if the designed log file already exists, instead of recreating it
- add a timestamp in the file name for the log file
Those can be probably achieved with some new Docker environment variables
### Issue Priority
Priority: 3
### Issue Component
Component: Containers
Contributor guide
Research direction
Start by locating the Hop Docker container log configuration and environment-variable handling. Check how an existing mounted log file is created at container launch, then verify that the selected behavior preserves prior history through restarts and that timestamped filenames are handled consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100