Nightingale, an open‑source enterprise monitoring platform from Didi, combines cloud‑native design, high availability, flexible plugins, and a powerful object‑tree navigation to meet the monitoring needs of both small clusters and massive deployments, while extending and improving upon Open‑Falcon.
The article details 360's external network quality monitoring system, explaining its background, real‑time detection features, CDN‑based source host selection, three‑layer architecture, data collection and storage pipelines, fault‑diagnosis strategies, and visualization approaches for rapid network fault localization.
This article provides a comprehensive overview of Prometheus, covering its open‑source monitoring architecture, multi‑dimensional data model, query language, storage mechanisms, service discovery, alerting workflow with Alertmanager, and visualization using Grafana, all illustrated with key diagrams and configuration examples.
The article describes how 360 implements an external network quality monitoring system that uses CDN nodes as source hosts to perform minute‑level, end‑to‑end ping measurements, stores results in time‑series and other databases, analyzes them to detect VIP, data‑center or ISP faults, and generates visualized alerts and reports for operations teams.
This article introduces Prometheus and Grafana as a powerful monitoring stack, explains their architecture, metric collection, storage options, query language, integration with Grafana for dashboards and alerts, and shares practical deployment patterns and high‑availability solutions.
This guide explains how to combine ELK (Elasticsearch, Logstash, Kibana) with Zabbix using the logstash-output-zabbix plugin, configure Logstash pipelines to filter error keywords, and set up Zabbix templates and triggers for instant log‑based alerts.
This guide walks you through setting up the open‑source MySQL Monitor tool, covering environment preparation, installation, database schema import, host configuration, alert channel setup (email and WeChat), cron scheduling, and accessing the monitoring pages, all with a clean Chinese interface.
This article explains why many system alerts are poorly designed, describes the true purpose of alerts as actionable notifications, distinguishes business rule monitoring from reliability monitoring, and presents practical metrics, strategies, and simple anomaly‑detection algorithms to create high‑quality, actionable alerts for reliable operations.
This guide explains how to configure Zabbix to monitor Windows Server login events—both successful and failed—by using eventlog keys, creating templates, items, triggers, and testing alerts to quickly detect and respond to potential security incidents.
This article outlines a comprehensive, layered monitoring architecture for enterprise IT operations, detailing the construction of a centralized platform, responsibilities across infrastructure, server, service, and user‑experience layers, event aggregation, visualization, data integration standards, alert thresholds, and continuous optimization practices.
This article shares practical Prometheus best‑practice tips, covering the accuracy‑reliability trade‑off, self‑monitoring setups, avoiding NFS storage, pruning high‑cardinality metrics, handling rate‑function traps, alert‑graph mismatches, group_interval effects, and the overarching goal of stable, cost‑effective observability.
This article introduces Prometheus, compares it with Zabbix, Open‑Falcon and Nagios, explains its architecture, data model, exporters, storage options, query language, alerting and federation, and shares practical deployment experiences and common Q&A for cloud‑native environments.
This article introduces Prometheus, an open‑source cloud‑native monitoring and alerting system, covering its main characteristics, core components, architecture diagram, typical use cases, query language syntax, built‑in functions, time‑series types, and practical tips for reliable operation.
The Open Alarm Platform provides a flexible data model, modular architecture, and robust stability features to enable various business lines to integrate their custom monitoring systems via APIs, offering alert convergence, merging, multi‑channel delivery, and comprehensive management while reducing development and maintenance costs.
This article compares three container alerting frameworks—Alertmanager, Kapacitor, and Bosun—explains why Bosun was chosen for its flexible HTTP API rule deployment and low learning curve, and provides step‑by‑step configuration, rule definition, notification, and templating examples for integrating Bosun with Prometheus.
The article describes Autohome's evolution from a Zabbix‑based monitoring setup to a custom, distributed monitoring platform, detailing its architectural components, design goals, implementation choices, product features, and future roadmap for fault localization and dynamic alerting.
This article describes the motivation, architecture, key components, rule engine, alert actions, and practical lessons learned while building a unified monitoring and alarm system for MaFengWo's large‑scale transportation platform, highlighting data collection, Elasticsearch storage, scheduling, and future enhancements.
Open Distro for Elasticsearch is an AWS‑backed, fully open‑source distribution of Elasticsearch that adds enterprise‑grade security, alerting, SQL querying, and performance analysis features, includes Kibana for visualization, and follows a clear version‑release roadmap.
This article explains the fundamental flaws of typical alert systems, distinguishes between business rule and reliability monitoring, outlines essential metrics and strategies for effective alerts, and presents simple yet powerful anomaly‑detection algorithms to ensure alerts are actionable and reduce noise.
This article explains how the team designed and implemented a unified monitoring and alert platform for a multi‑service transportation business, covering architecture, data collection, storage, rule engine, alert delivery, troubleshooting aids, encountered pitfalls, and future enhancements.
This article explores the essential concepts of online monitoring, including effective monitoring items, objectives, scope, system and business monitoring types, stakeholder considerations, implementation steps, tool choices, alert strategies, and how to evaluate the overall value of monitoring initiatives.
This article provides a thorough overview of system monitoring, covering its objectives, practical methods, core concepts, a comparison of popular open‑source and commercial tools, detailed monitoring processes (using Zabbix as an example), key metrics, alerting strategies, interview tips, and a summary of how organizations extend monitoring solutions.
This guide walks through setting up a comprehensive security log collection pipeline—covering WAF, firewall, and Nginx logs—using ELK, Logstash, Kafka, and Flume, and then configuring real‑time alerts with Sentinl or ElastAlert integrated with DingTalk and email notifications.
The article chronicles the design, implementation, and iterative evolution of JD Digital Technology’s in‑house host monitoring platform Diting, detailing its V1, V2, and V3 architectures, the challenges encountered at each stage, and future directions toward intelligent, automated operations.
This article explores the essential concepts for selecting and building an operations monitoring platform, reviewing popular tools such as Cacti, Nagios, Zabbix, Ganglia, Centreon, Prometheus, and Grafana, and outlines a six‑layer architecture and practical strategies for scaling, alerting, and high‑availability in diverse environments.
This article explains how Prometheus collects metrics, evaluates alert rules, transitions through alert states, and uses grouping, suppression, silencing, and configurable delay parameters to reduce noise and ensure timely, actionable alerts in monitoring systems.
This article details the architectural evolution of Ctrip's Hickwall monitoring and alerting platform, describing the transition from an Elasticsearch‑based first generation to an InfluxDB‑driven second generation, the design of the Incluster storage layer, data aggregation strategies, and the implementation of high‑performance stream‑based alerting.
The 58 Intelligent Monitoring System provides a flexible, 24/7, multi‑dimensional monitoring solution that covers network, server, system, application and business layers, incorporates AI‑driven prediction, anomaly detection, alarm merging, root‑cause analysis and self‑healing, and offers both PC and WeChat interfaces for operators.
This guide introduces a PHP‑based reimplementation of Percona’s PT‑kill tool that not only terminates long‑running MySQL queries but also adds email and WeChat notifications, explains installation prerequisites, detailed command‑line options, example usages, configuration steps, and how to customize alerts and logging.
The article summarizes the 58 Group technical salon where experts from Momo and 58 shared practical experiences on monitoring platform architectures, coverage, alarm configurations, convergence techniques, custom dimensions, multi‑view dashboards, and future directions for intelligent and automated monitoring across the company.
The article introduces SGM, a comprehensive service governance and monitoring solution that addresses scaling, dependency complexity, and operational challenges by providing automated topology, real‑time tracing, capacity planning, root‑cause analysis, and extensive monitoring features such as performance metrics, JVM stats, call‑chain visualization, business dashboards, and intelligent alerting.
Zabbix offers a web‑based, enterprise‑grade solution for distributed system and network monitoring; this guide walks Linux ops engineers through why monitoring matters, key availability metrics, what to monitor, step‑by‑step installation, web UI configuration, custom checks, alerting, visualization, template sharing, full‑network scaling, auto‑discovery, proxy deployment, and SNMP integration.
The article presents a detailed overview of the internally developed X Monitoring system, covering its architecture, configuration, reporting and monitoring modules, the use of Redis, Qbus, ElasticSearch and MySQL, as well as both server‑side (API/DB) and agent‑side (PHP) monitoring features, data collection commands, alert thresholds, and overall operational benefits.
The article explains how a DSP advertising team moved testing right by building a four‑layer online monitoring system—including interface, UI, revenue, and daily key‑metric monitoring—to quickly detect and resolve production incidents, reduce false alarms, and improve overall reliability.
This guide walks through enabling MySQL binlog, installing Logtail, configuring data collection, indexing, previewing logs, writing custom SQL queries for user login analysis, constructing real‑time dashboards, setting abnormal‑login alerts, and backing up data to OSS for long‑term storage.
This article shares a comprehensive overview of game operation security at Tencent, covering personal background, real‑world incident cases, the inherent challenges of large‑scale game services, past monitoring efforts, and a new data‑driven alerting framework that dramatically reduces false alarms while protecting game economies.
This guide explains how to create and deploy a Bash script that retrieves a WeChat corporate token and sends Zabbix alarm messages to all users through the WeChat API, enabling automated monitoring alerts via the corporate WeChat platform.
The Horus system is a comprehensive call‑center monitoring platform that automates data collection, fault detection, alert generation, and escalation through statistical analysis, feature extraction, and integration with voice‑bot testing to improve operational efficiency and reduce false alarms.
This article walks you through the complete process of setting up Zabbix on a Linux server—including preparing the environment, installing LAMP, configuring the Zabbix server and agent, creating databases, defining templates, items, triggers, graphs, and custom script alerts—to achieve real‑time network traffic monitoring and automated notifications.
This article details the evolution of Wonder, 360’s internal monitoring platform built on Open‑Falcon, covering its architecture, key features, large‑scale deployment, data collection, alerting mechanisms, custom plugins, and future development plans for smarter, more flexible operations.
This article outlines the fundamentals, objectives, methods, core processes, tool selection, metrics, alerting, and interview tips for constructing a robust monitoring ecosystem, emphasizing Zabbix while comparing various open‑source solutions.
This article introduces the fundamental concepts, methods, types, goals, and product attributes of enterprise monitoring and alerting, explains the perspective differences between users and builders, and outlines a comprehensive monitoring system architecture for large‑scale operations.
This article explains how to design and implement a comprehensive operations monitoring platform by integrating Ganglia for data collection and Centreon for alerting, detailing a six‑layer architecture, data flow, seamless integration, and practical Q&A for real‑world deployment.
This guide explains how to install, configure, and use the wechat_sender tool—built on wxpy and Tornado—to forward logs, alerts, and scheduled messages from scripts or web services directly to personal or group WeChat chats.
Zabbix is an open‑source, web‑based enterprise monitoring platform that tracks Windows/Linux hosts, network devices, and hardware/software metrics, provides alerting, visualizes data via a customizable PHP web UI, and comprises components such as server, agents, proxies, Java gateway, and API, with flexible templates, discovery, and storage options.
This comprehensive guide explains why monitoring is vital for operations, outlines clear objectives and methods, compares popular open‑source and commercial tools, details a Zabbix‑based workflow, and covers hardware, system, application, network, security, API, performance, and business metrics with practical alerting strategies.
This article presents a comprehensive server‑side monitoring solution covering functional and performance requirements, monitoring objects, design choices between self‑monitoring and centralized reporting, system architecture, API definitions, key challenges such as key collisions, data formats, storage options, and operational considerations.
This article explains how Wonder's log monitoring system works, covering rolling count, string and numeric matching types, the underlying Go implementation with tail reading, alert strategies, and future enhancements for handling large log files.
This guide walks through setting up ElastAlert—a Python‑based alerting framework for Elasticsearch—by covering the required environment, dependencies, installation steps, index creation, configuration files, rule testing, and execution on an Ubuntu system.
This guide explains why WeChat is popular in China and introduces three ElastAlert plugins (shell, Python, Java) that send alerts via WeChat, compares alert channels, outlines prerequisites, and provides step‑by‑step installation and usage instructions with code examples and screenshots.
Mt‑Falcon, Meituan’s re‑engineered successor to Zabbix, introduces a modular architecture—Agent, Transfer, HBS, Judge, Graph, Alarm, Portal—and extensive refactorings that boost memory efficiency, asynchronous data handling, multi‑condition alerts, and API exposure, enabling over one million QPS, 200 million metrics, and robust, scalable monitoring across the company.
This article explains how to design and implement a comprehensive operations monitoring platform using Ganglia for data collection and Centreon for alerting, detailing a six‑layer architecture, integration steps, data flow, and practical Q&A for effective fault detection and response.
The article critiques popular but unnecessary log‑analysis features—such as sub‑second alerts, endless pagination, flashy maps, full SQL support, bulk downloads, and live tail—arguing that focusing on practical alert content, efficient querying, and proper architecture yields far more value for IT operations.
The discussion outlines essential service‑monitoring techniques—including health checks, JVM metrics, traffic and payment ring‑ratio analysis, client‑side exception tracking, third‑party CDN monitoring, alert thresholds, instrumentation via AOP or SDKs, and tooling such as Datadog, Zabbix, and the Elastic stack—to reliably detect and respond to incidents in e‑commerce environments.
This article explains how the internally built Wonder monitoring system, based on Open‑Falcon, tackles large‑scale operational challenges by offering automated agent updates, customizable metrics, log and port monitoring, persistent alarm storage, enhanced alert content, and comprehensive dashboards for thousands of devices.
This article details Ctrip's journey building a unified real-time data platform—covering business motivations, architectural requirements, technology choices like Kafka and Storm, implementation of Avro schemas, monitoring, alerting, operational lessons, and future explorations such as Streaming CQL and JStorm.
Zhang Yue, a Qunar operations engineer, discusses the design, selection, architecture, scalability challenges, visualization, alert strategies, and future plans of the company's in‑house monitoring platform Watcher, highlighting lessons learned from migrating from Cacti to a Graphite‑based, Grafana‑enhanced solution.
Twitter’s internal monitoring team built a full‑stack observability platform that handles billions of metric writes per minute, supports distributed tracing, log aggregation, visual dashboards, and alerting across data centers and public clouds, and shares the architecture, components, and key lessons learned.
This article explains how to design and implement a unified operations monitoring and alerting platform by combining Ganglia for data collection with Centreon for alerting, covering architecture layers, module functions, integration steps, and practical Q&A for large‑scale deployments.
This article outlines a comprehensive design for a high‑performance, unified operations monitoring platform, detailing a six‑layer architecture, the roles of data collection (using Ganglia), data extraction, and alerting modules (with Centreon), and provides practical integration tips, deployment diagrams, and Q&A for large‑scale environments.
Vipshop’s three‑tier monitoring system—covering system, application (Mercury), and business layers—collects and analyzes logs from distributed components, providing real‑time metrics, slow‑call detection, error tracing, and configurable alerts to help engineers quickly pinpoint and resolve performance issues.
This article introduces OWL, a distributed, enterprise‑grade monitoring solution that combines infrastructure and business metrics, offers floating alert rules, customizable dashboards, visual asset management, a resilient Golang‑based agent, and a parallel‑scalable HBase storage backend.
Open‑Falcon, an open‑source, enterprise‑grade monitoring solution from Xiaomi’s operations team, offers zero‑configuration data collection, high‑throughput horizontal scaling, flexible alerting, efficient historical queries, and a user‑friendly dashboard, with detailed documentation, quick installation steps, and a highly available architecture.
This guide walks you through registering a WeChat public account, setting up a Node.js simulator for login and friend retrieval, installing Node.js, configuring Nagios commands and contacts, and finally enabling WeChat notifications for monitoring alerts.
