apache / apache/incubator-seata
support for separate client log files
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26k
- Forks
- 8.8k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
Why you need it?
Is your feature request related to a problem? Please describe in details
As a data middleware, Seata should have a separate log file. Currently used on the business side, Seata logs are not configured with separate logback/log4j, resulting in middleware logs being mixed with business logs. Seata log rolling base on the business's log policy, causing some problems that cannot be traced through Seata's log files.
How it could be?
A clear and concise description of what you want to happen. You can explain more about input of the feature, and output of it.
Other related information
Add any other context or screenshots about the feature request here.
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 Seata and its Logback/Log4j logging setup but does not identify files, tests, or entry points. Start by locating the existing logging configuration and how Seata logs are routed and rolled; done should mean middleware logs use a separate configurable file and rolling policy without mixing with business logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100