Support configuration of log file size and amount for sentinel-record.log
Open
area/logging
good first issue
kind/enhancement
- Dominant language
- Java
- Stars
- 23.1k
- Forks
- 8.1k
- PR merge metrics
- No merged PRs in 30d
Description
## Issue Description
我们这面现在因为record.log打印的太多导致服务器磁盘爆掉
### Describe what happened (or what feature you want)
希望新增控制record.log的数量和大小功能
### Describe what you expected to happen
像日志框架一下,可以增加数量,大小,自动清理功能
### How to reproduce it (as minimally and precisely as possible)
1. 长时间不清理就可以复现
### Tell us your environment
linux,docker
### Anything else we need to know?
暂无
Contributor guide
Research direction
Start by locating where sentinel-record.log is generated and where its files are managed. Review the existing logging configuration and determine how size, file count, and automatic cleanup should be exposed; done means long-running use no longer allows these logs to exhaust the disk.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100