Skip to main content

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 10 alertable data source types, including Prometheus, Elasticsearch, ClickHouse, and MySQL

Flexible Alert Rules

Three detection modes: threshold evaluation, missing data, and data exists

Distributed Architecture

Support for multi-datacenter deployment, with rules shared across instances 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 alert rules run on an alert engine deployed inside your network:
1

SaaS Server

Responsible for managing alert rules, permission control, and alert event aggregation
2

Alert engine (monitedge)

Deployed within your private network, syncs alert rules from SaaS, periodically queries data sources, and performs threshold evaluation
3

Alert Push

When the alert engine generates alert events, they push them to the SaaS server for subsequent processing
If you have multiple datacenters, you can deploy an independent alert engine 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:
Deploy multiple alert engine instances in the same datacenter and set the same cluster name with the --alerter.clusterName parameter. The instances share the alert rules automatically.
Deploy independent alert engine clusters in different datacenters, each cluster using a different cluster name to process their respective datacenter’s data sources.
If an instance in the cluster fails, other instances will automatically take over its alert rules, ensuring high availability while avoiding duplicate alerts.

Detection modes

Supported data sources

Prometheus

PromQL queries, VictoriaMetrics compatible

Elasticsearch

Log alerting

Loki / VictoriaLogs

Log alerting

ClickHouse

SQL queries

MySQL / Oracle / PostgreSQL

SQL queries

Aliyun SLS / Tencent CLS

Cloud log services
See Data source management for the full list.

Use cases

  • Monitoring is spread across multiple clouds and data centers, and you want to onboard sources and manage alert rules in one place
  • Data sources live in a private network without public access, and alert evaluation should stay local
  • Manage Prometheus, log, database, and middleware alerting under one workflow
  • Let rule-generated alerts flow straight into Flashduty grouping, escalation, and routing

Quick start

Deployment Guide

Learn how to deploy the alert engine and create your first alert rule

FAQ

Answers to common questions during usage