Support Alerting for PromQL Charts
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9.9k
- Forks
- 471
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 117
Description
Currently, HyperDX supports setting up alerts on various chart types, but the "Alert" configuration tab is disabled when using PromQL charts. Users who rely heavily on Prometheus metrics need a way to trigger notifications based on PromQL query evaluations natively within HyperDX, rather than relying on external Alertmanagers.
Solution
Enable the alert configuration interface for PromQL charts and evaluate these alerts in the backend checkAlerts task loop.
Specifically:
- Allow users to configure thresholds, evaluation windows, and notification channels for PromQL charts exactly as they do for standard charts.
- During the background evaluation loop, proxy these queries to the underlying Prometheus endpoint or through ClickHouse's
prometheusQueryRangefunction. - Integrate the results into the standard alert state management and notification pipeline.
Additional Context
- The backend already supports querying Prometheus endpoints for standard dashboard views, we just need to route background alert evaluations through the same mechanisms.
- Requires unblocking
PromqlSavedChartConfigin theAlertChartConfigSchema.
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 the AlertChartConfigSchema and the PromqlSavedChartConfig handling, then follow the backend checkAlerts task loop and existing Prometheus query path. Done means PromQL charts expose alert configuration, evaluations use the Prometheus endpoint or ClickHouse prometheusQueryRange, and results flow through standard alert state and notification handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse, prometheus, typescript
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100