DOCSEARCHbyAlgolia
Submit Docs

Apache HertzBeat Documentation

repository·master·Indexed 27 days ago

https://github.com/apache/hertzbeat

An AI-powered, agentless, real-time observability system that unifies metrics and logs collection, alerting, and notification. It supports high performance and customization via YML templates for protocols including HTTP, JMX, SSH, and SNMP. The system includes an AI SOP engine for automated workflows, a bash MCP server, and a structured process for HertzBeat Improvement Proposals (HIP).

Tokens
209.8K
Snippets
282
Records
882
Agent score
92%

What's inside Apache HertzBeat

  1. Overview of Apache HertzBeat features

    master

    Apache HertzBeat is an open-source, real-time observability system designed for high performance and ease of use. Key capabilities include:

    • Unified Platform: Combines monitoring, alarming, and notification in a single platform.
    • Agentless Monitoring: Supports web services, programs, databases, caches, OS, webservers, middleware, big data, cloud-native, network, and custom targets without requiring agents.
    • Protocol Support: Configurable via online YML templates for protocols including Http, Jmx, Ssh, Snmp, Jdbc, and Prometheus.
    • Prometheus Compatibility: Compatible with the Prometheus ecosystem.
    • Scalability: Supports horizontal expansion of multi-collector clusters and cloud-edge collaboration.
    • Flexible Notifications: Supports multiple notification channels including Discord, Slack, Telegram, Email, Dingtalk, WeChat, FeiShu, Webhook, SMS, and ServerChan.
    • Status Pages: Built-in capabilities for creating real-time service status pages.

  2. Overview of HertzBeat Monitoring Capabilities

    master

    HertzBeat is an agentless, real-time, open-source monitoring and alarm system. It is designed for high performance and is compatible with the Prometheus ecosystem. It allows users to configure monitoring, alarms, and notifications in a single workflow through a web interface without requiring an agent installation on target systems.

    Key Capabilities:

    • Protocol Support: Configure monitoring via Http, Jmx, Ssh, Snmp, Jdbc, Prometheus, and more.
    • Customization: Use monitoring template YML files to define custom metrics for any service (e.g., K8s, Docker).
    • Alerting & Notifications: Supports various channels including mail, Discord, Slack, Telegram, Dingding, wechat, Feibook, SMS, Webhook, and Server sauce.
    • Scalability: Supports horizontal expansion of collector clusters and multi-isolated network monitoring.

  3. Overview of HertzBeat Alert Integration

    master

    HertzBeat acts as a centralized "Alert Center" that provides unified reception, standardized processing, and intelligent dispatching of alerts from various third-party monitoring and observability platforms.

    Key capabilities include:

    • Multi-Source Ingestion: Receives alerts from platforms like Webhook, Prometheus, Alertmanager, SkyWalking, and Tencent Cloud.
    • Standardization: Converts diverse external alert formats into a single internal HertzBeat format.
    • Processing Mechanisms:
      • Grouping and Convergence: Groups alerts by labels and deduplicates repeated alerts within a defined time window.
      • Inhibition: Suppresses secondary alerts when specific conditions are met.
      • Silencing: Temporarily disables notifications during maintenance to reduce noise.

  4. Overview of Apache HertzBeat capabilities

    master

    Apache HertzBeat is an AI-powered, agentless open-source real-time monitoring system designed for observability. It unifies four core functions into a single platform:

    1. Metrics Collection: Monitors over 200 services including databases, operating systems, middleware, and cloud infrastructure using native protocols (HTTP, SNMP, JMX, SSH, JDBC, Prometheus).
    2. Log Aggregation: Centralizes logs using the OTLP protocol for unified analysis.
    3. Alert Management: Processes internal and external alerts using flexible threshold rules, including features for grouping, convergence, silence, and suppression.
    4. Notification Distribution: Distributes alerts through multiple channels including Email, Slack, Discord, Telegram, DingTalk, WeChat, SMS, and Webhooks.

  6. Overview of HertzBeat features

    master

    HertzBeat is an open-source real-time monitoring and alerting system designed for high performance and ease of use. Key characteristics include:

    • Agentless Architecture: No agent installation is required on monitored targets; all operations are performed via the web interface.
    • Customizable Monitoring: Users can define metrics using configurable protocols such as Http, Jmx, Ssh, Snmp, and Jdbc by configuring monitoring templates in YML format.
    • High Performance: Supports horizontal scaling through multiple collector clusters and handles multi-isolated network monitoring.
    • Extensive Alerting Channels: Supports various notification methods including Email, Discord, Slack, Telegram, WeChat, Dingtalk, Flybook, SMS, Webhook, and Server Chan.

  8. Overview of Apache HertzBeat

    master

    Apache HertzBeat is an open-source, real-time observability system designed for high performance and ease of use. It is an agentless monitoring platform that combines monitoring, alarming, and notification capabilities into a single interface.

    Key capabilities include:

    • Agentless Monitoring: Monitor web services, databases, caches, OS, middleware, big data, and cloud-native environments without installing agents.
    • Protocol Support: Configurable monitoring via Http, Jmx, Ssh, Snmp, Jdbc, and Prometheus using online YML templates.
    • Ecosystem Compatibility: Compatible with the Prometheus ecosystem.
    • Flexible Notifications: Supports multiple channels including Discord, Slack, Telegram, Email, Dingtalk, WeChat, FeiShu, Webhook, and SMS.
    • Scalability: Supports horizontal expansion of multi-collector clusters and cloud-edge collaboration.

  12. Understand the Alarm Processing Mechanism

    master

    Before alarms are displayed in the Alarm Center, they pass through four processing stages to reduce noise and manage dependencies:

    • Grouping: Categorizes related alarms by source, type, severity, and other labels.
    • Consolidation: Merges multiple similar alarms occurring within short intervals into a single streamlined notification to prevent fatigue.
    • Suppression: Manages dependencies by suppressing secondary alarms when a primary alarm is already triggered.
    • Silencing: Temporarily mutes specific alarms during defined periods, such as maintenance windows, using time-based silence rules.