pingcap / pingcap/tidb-operator
improve log output format
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Feature Request
Is your feature request related to a problem? Please describe:
TiDB Operator log output does not contain date and timezone info, it will bring additional work to investigate long history issue without date info
log output from TiDB Operator
log output from kernel component like PD
Describe the feature you'd like:
TiDB Operator has the same log output format as kernel component does.
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
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 comparing the TiDB Operator log output shown in the issue with the kernel component example, then locate the operator's logging entry points in the repository. Done means operator logs include date and timezone information and use the same format as the kernel component logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100