Make `order by` optional in searches
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9.9k
- Forks
- 471
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 117
Description
Coming from other tools, hyperdx feels quite rigid. It would go along way to support custom queries for searches (and maybe charts). The custom queries should also support alerting functionality. We use custom queries and alerts on those in axiom, for example. While I think it's good to strive for having high-level UI primitives for most things, I don't think that'll cover 100% of user needs, so it would be very powerful to allow folks to write custom queries and setup alerts over those queries.
This is maybe not the best example, but I was trying to calculate rate. The screenshot below demonstrates a few issues:
- Sort of working, but verry clunky to put in custom SQL
- bug: adds my default fields to select even though I removed them
- bug: adds order by even though I removed it
- Because it adds order by and other fields, query doesn't work
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 reproducing the search behavior described in the issue with custom SQL, especially removing the default fields and ORDER BY. Trace the search query-building entry point and determine how custom queries interact with searches, charts, and alerting. Done means custom SQL remains valid without unwanted fields or ordering, with the intended alerting behavior clarified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql, typescript
- Domain
- backend, frontend, search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100