[lake/tiering] Add More Tiering Monitoring Metrics
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 625
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 97
Description
### Search before asking
- [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar.
### Motivation
Introduce a set of monitoring metrics focused on the tiering process, including file/record sizes, read/write throughput.
### Solution
_No response_
### Anything else?
_No response_
### Willingness to contribute
- [x] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue points to the lake/tiering area but names no files, tests, or entry points. Start by locating the tiering implementation and existing monitoring metrics, then determine the relevant file and record sizes plus read/write throughput to cover. Done means the requested tiering metrics are available and validated by the project's appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100