Request per second - Dashboards - Allow per second granularity?
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9.9k
- Forks
- 471
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 117
Description
HyperDX does not allow to have a RPS/TPS (request per second or transaction per second) like dashboards.
toStartOfInterval (toDateTime (Timestamp), INTERVAL 1 minute) AS `__hdx_time_bucket`
Allow 1 second? any reason we dont allow?
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 tracing how dashboard queries construct the shown ClickHouse time bucket, using the toStartOfInterval SQL in the issue as the search clue. Determine where the one-minute granularity is constrained; done means dashboards can request and render one-second buckets without breaking existing granularities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse, typescript
- Domain
- data-visualization, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100