temporalio / temporalio/temporal
Make temporal docker to not emit noisy logs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Currently temporal docker emits a lot of logs with 99.9% of them being useless. It also doesn't have clear indication when the service is ready serve requests. My proposal is to emit something like:
Temporal Service Starting...
Temporal Service Started
and then emit only fatal errors. For troubleshooting provide an option to enable logs.
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
Start by locating the Temporal Docker startup and logging configuration, then inspect how the service currently reports readiness and runtime logs. Done means startup and readiness messages are clear, routine output is suppressed by default, fatal errors remain visible, and an option enables troubleshooting logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100