Feature Request: Define Alerts Using YAML
Currently, alerts have to be configured manually through the HyperDX UI. This works for a few services, but when there are many services and APIs, creating and maintaining alerts for each one becomes repetitive and difficult.
It would be useful to support defining alerts in a YAML file alongside the service code:
alerts:
- name: service-a-api-errors
service: service-a
api: /api/orders
threshold: 10
window: 5m
- name: service-b-api-latency
service: service-b
api: /api/users
threshold: 2000
window: 5mHyperDX could then provide a way to consume this YAML — through an upload option, API, CLI, or CI/CD integration — and automatically create/update the corresponding alerts.
This would make alerts version-controlled, reproducible, and much easier to manage across multiple services and environments.
Instead of manually setting up alerts for every API in the UI, define them once in YAML alongside the code and let HyperDX provision them automatically.
Feature Request: Define Alerts Using YAML
Currently, alerts have to be configured manually through the HyperDX UI. This works for a few services, but when there are many services and APIs, creating and maintaining alerts for each one becomes repetitive and difficult.
It would be useful to support defining alerts in a YAML file alongside the service code:
HyperDX could then provide a way to consume this YAML — through an upload option, API, CLI, or CI/CD integration — and automatically create/update the corresponding alerts.
This would make alerts version-controlled, reproducible, and much easier to manage across multiple services and environments.