[BUG] <title> ( GSoC '26 )
- Dominant language
- Java
- Stars
- 7.4k
- Forks
- 1.3k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 32
Description
### Is there an existing issue for this?
- [x] I have searched the existing issues
### Current Behavior
Requirements:
Refer to https://doris.apache.org/docs/4.x/log-storage-analysis and create tables based on the recommended content and Apache Hetzbeat's actual implementation.
Implement an optional automatic log data expiration feature.
Implement identical log collection and query functionality to the existing Greptimedb, ensuring seamless user switching (module located in hertzbeat-log).
Log writing is recommended to use stream load mode; log queries are recommended to utilize database connection pools and MySQL JDBC.
Task List
No response
### Expected Behavior
_No response_
### Steps To Reproduce
_No response_
### Environment
```markdown
HertzBeat version(s):
```
### Debug logs
_No response_
### Anything else?
_No response_
Contributor guide
Research direction
Start with the Apache Doris log-storage-analysis documentation and the existing Greptimedb implementation in the hertzbeat-log module. The work is complete when the recommended tables, optional automatic log expiration, and equivalent log collection and query functionality are implemented, including stream-load writing and pooled MySQL JDBC queries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, mysql
- Domain
- databases, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100