oxidecomputer / oxidecomputer/omicron
[ClickHouse] Allow for metric TTL to be customisable
Open
Nobody has claimed this yet.
oximeter
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Currently all metrics have a hardcoded TTL of 30 days https://github.com/oxidecomputer/omicron/pull/3553
As the company grows, we'll have customers with different data retention policies. We'll need to allow for this TTL setting to be customised by the user.
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 reading the linked pull request #3553 to find where the 30-day metric TTL is hardcoded. Trace how metric settings are configured and define the user-facing retention setting; done means the TTL can be customized for different customer policies and the relevant behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse, rust
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100