What is Monitors?
Flashduty Monitors is a unified alert engine that integrates various metrics and log data sources. Based on your configured alert rules, it periodically queries data, performs threshold evaluation, and pushes generated alert events to Flashduty On-Call for aggregation and delivery.Core Capabilities
Multi-datasource Support
Support for Prometheus, VictoriaMetrics, Elasticsearch, ClickHouse, and other mainstream data sources
Flexible Alert Rules
Support for threshold alerts, year-over-year alerts, period-over-period alerts, no-data alerts, and more
Distributed Architecture
Support for multi-datacenter deployment with automatic sharding for high availability
Deep Integration
Deep integration with On-Call, delivering alerts directly to responders
Architecture Design
Flashduty is a SaaS service that cannot directly access data sources within user private networks, so Monitors adopts an edge computing architecture:monitedge Edge Node
Deployed within user private networks, syncs alert rules from SaaS, periodically queries data sources, and performs threshold evaluation
If you have multiple datacenters, you can deploy independent monitedge instances in each datacenter, each responsible for alerting on data sources within their respective datacenter.
High Availability Deployment
Monitors supports cluster deployment to ensure high availability of the alert engine:Single Datacenter Cluster
Single Datacenter Cluster
Deploy multiple monitedge instances in the same datacenter, use the
--alerter.clusterName parameter to set the same cluster name, and the system will automatically shard alert rule processing.Multi-datacenter Deployment
Multi-datacenter Deployment
Deploy independent monitedge clusters in different datacenters, each cluster using a different cluster name to process their respective datacenter’s data sources.
Failover
Failover
If an instance in the cluster fails, other instances will automatically take over its alert rules, ensuring high availability while avoiding duplicate alerts.
Alert Rule Types
| Type | Description | Use Cases |
|---|---|---|
| Threshold alert | Trigger when metric exceeds/falls below threshold | CPU, memory, disk, and other resource monitoring |
| Year-over-year alert | Trigger when deviation from historical same period exceeds threshold | Business volume, traffic anomaly detection |
| Period-over-period alert | Trigger when deviation from previous period exceeds threshold | Spike and drop detection |
| No-data alert | Trigger when metric stops reporting | Service liveness detection |
| Composite alert | Combined condition evaluation | Complex business scenarios |
Supported Data Sources
Prometheus
PromQL query support
VictoriaMetrics
Prometheus protocol compatible
Elasticsearch
Log alerting support
ClickHouse
SQL query support
MySQL
SQL query support
More...
Continuously expanding