Provide API to access profiling data volume per label.
- Dominant language
- Go
- Stars
- 11.7k
- Forks
- 802
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 80
Description
#### Is your feature request related to a problem? Please describe.
Currently is really difficult to understand what series have which profiling volume.
#### Describe the solution you'd like
Would like to provide an API, that can based on TSDB index information, determine how much profiling data has been stored.
A potential returned unit could be for example the profiling sample count. (Providing bytes, there might be tricky because of deduplication of symbols), maybe ingested uncompressed bytes would be best as that is how we charge in Grafana Cloud.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the API entry points and TSDB index code responsible for profiling data. Clarify whether the result should report sample count, bytes, or ingested uncompressed bytes, including how labels and symbol deduplication affect it. Done means a documented API can determine profiling volume per label with tests covering the chosen metric.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, databases, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100