Improve time series data storage options
- Dominant language
- Erlang
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 9
Description
Originally: "Telemetry db rollups"
@chewbranca:
> Storing time series data in CouchDB can incur a lot of overhead when each data point is stored in a doc. One common approach to solving this problem is rolling up data, for instance, if you're storing a doc with metrics data every minute, you could roll up the docs for each minute into a single doc, then do the same for hours, or days, or etc. Right now this is a manual process that needs to be done in the app layer, rather than a core feature of the database.
Might be something a PSE could deal with?
Contributor guide
Research direction
No files, tests, or entry points are identified. Start by clarifying how CouchDB should support telemetry rollups across minute, hour, and day intervals, and whether this belongs in the core database. Done should be defined as an agreed design and implementation scope for reducing per-data-point document overhead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100