HertzBeat supports custom monitoring, only by configuring YML files we can customize the required monitoring types and indicators to meet common personalized needs.
HertzBeat Modular, manager, collector, scheduler, warehouse, alerter module decoupling, easy to understand and custom development.
HertzBeat supports more liberal alarm configuration (calculation expression), supports alarm notification, alarm template, email nail wechat flying book and other timely notification delivery.

Module

manager Provides basic services of monitoring and management and system management

Provides monitoring management, monitoring application configuration management, system user tenant background management, etc.

collector Provides monitoring data collection services

Remote acquisition of peer indicator data using a common protocol.

scheduler Provides monitoring task scheduling service

Collection task management, scheduling and distribution of one-time and periodic tasks.

warehouse Provide monitoring data warehousing services

Collection index results data management, data drop, query, calculation and statistics.

alerter Provide alarm service

Alarm calculation triggers, monitoring status linkage, alarm configuration, and alarm notification.

web-app Provides visual console page

HertzBeat Hertzbeat – High performance monitoring alarm system插图

Fast start

Deployment of dependent services

HertzBeat relies least on relational database MYSQL5+ and sequential database TDengine2+

HertzBeat installation

HertzBeat supports installation and deployment through source code installation, Docker container operation and installation package.

Fast installation in Docker mode

docker run -d -p  1157:1157 -v /opt/application.yml:/opt/hertzbeat/config/application.yml --name hertzbeat tancloud/hertzbeat:[version tag]

< Installation by installation package

Download the installation package for your system environment

https://gitee.com/dromara/hertzbeat/releases

Start deployment $./startup.sh

User-defined monitoring

Configure the custom monitoring type Two YML files need to be added

Monitoring configuration definition file named after the monitoring type – for example, example.yml must be located in the installation directory /hertzbeat/define/app/
Monitor parameter definition file named after the monitor type – for example, example.yml must be located in the installation directory /hertzbeat/define/param/
By restarting the hertzbeat system, we have adapted a new custom monitoring type.

< Monitoring configuration definition file

example: Create a user-defined monitoring type named example to collect indicator data using HTTP.
File name: example.yml located in /define/app/example.yml

# This monitoring type belongs to: service- Application service monitoring DB-Database monitoring custom- Custom monitoring OS-Operating system monitoring 
category: custom
# Monitor application type (consistent with file name) eg: linux windows tomcat mysql aws... 
app: example
name:
      en-CN :  Simulation application type 
     en-US: EXAMPLE APP
# Parameter map. These are input variables, that is, they can be written as ^_^host^_^ in the following configuration, and the system automatically replaces the  variable values.
# type is the parameter type: 0-number number, 1-string plaintext string, 2-secret encrypted string 
# Force fixed mandatory parameter -host 
configmap:
  - key: host
    type: 1
  - key: port
    type: 0
  - key: username
    type: 1
  - key: password
    type: 2
# List of indicator groups 
metrics:
# First monitor indicator group cpu
# Note: (responseTime - response time)
  - name: cpu
    # The smaller the indicator group scheduling priority (0-127), the higher the priority. The indicator group with a lower priority will be scheduled after the collection of the indicator group with a higher priority is completed, and the indicator group with the same priority will be scheduled in parallel. 
    # The indicator group with priority 0 is the availability indicator group, that is, it will be scheduled first, and other indicator groups will continue to be scheduled only after collection succeeds, and the scheduling will be interrupted if collection fails 
    priority: 0
    # Specific monitoring indicators in the indicator group 
    fields:
      # Indicator information includes field name type Field type :0-number number,1-string string instance Whether the instance is the primary key unit: indicator unit 
      - field: hostname
        type: 1
        instance: true
      - field: usage
        type: 0
        unit: '%'
      - field: cores
        type: 0
      - field: waitTime
        type: 0
        unit: s
# (not required) Monitor indicator alias, which maps to the indicator name above. The field used to collect interface data is not directly the final indicator name, and this alias is required for mapping conversion 
    aliasFields:
      - hostname
      - core1
      - core2
      - usage
      - allTime
      - runningTime
# (not required) indicator evaluation expression, which works with the aliases above to calculate the final required indicator value 
# eg: cores=core1+core2, usage=usage, waitTime=allTime-runningTime
    calculates:
      - hostname=hostname
      - cores=core1+core2
      - usage=usage
      - waitTime=allTime-runningTime
# Protocols eg: sql, ssh, http, telnet, wmi, snmp, sdk
    protocol: http
# Specific collection configuration when protocol is http 
    http:
      # host: ipv4 ipv6 domain name 
      host: ^_^host^_^
      # port 
      port: ^_^port^_^
      # url request interface path 
      url: /metrics/cpu
       GET POST PUT DELETE PATCH
      method: GET
      # Whether ssl/tls is enabled, i.e. http or https, default false
      ssl: false
      # Request header content 
      headers:
        apiVersion: v1
      # Request parameters 
      params:
        param1: param1
        param2: param2
      # Authentication 
      authorization:
        #Authentication mode:Basic Auth, Digest Auth, Bearer Token
        type: Basic Auth
        basicAuthUsername: ^_^username^_^
        basicAuthPassword: ^_^password^_^
      # Response data parsing methods: default- system rule,jsonPath-jsonPath script,website- website availability indicator monitoring 
      # todo xmlPath-xmlPath script,prometheus-Prometheus data rules 
      parseType: jsonPath
      parseScript: '$'

  - name: memory
    priority: 1
    fields:
      - field: hostname
        type: 1
        instance: true
      - field: total
        type: 0
        unit: kb
      - field: usage
        type: 0
        unit: '%'
      - field: speed
        type: 0
    protocol: http
    http:
      host: ^_^host^_^
      port: ^_^port^_^
      url: /metrics/memory
      method: GET
      headers:
        apiVersion: v1
      params:
        param1: param1
        param2: param2
      authorization:
        type: Basic Auth
        basicAuthUsername: ^_^username^_^
        basicAuthPassword: ^_^password^_^
      parseType: default

资源下载此资源为免费资源立即下载

Telegram:@John_Software

collect(0) Like (0)

Disclaimer: This article is published by a third party and represents the views of the author only and has nothing to do with this website. This site does not make any guarantee or commitment to the authenticity, completeness and timeliness of this article and all or part of its content, please readers for reference only, and please verify the relevant content. The publication or republication of articles by this website for the purpose of conveying more information does not mean that it endorses its views or confirms its description, nor does it mean that this website is responsible for its authenticity.

Ictcoder Free Source Code HertzBeat Hertzbeat – High performance monitoring alarm system https://ictcoder.com/hertzbeat-hertzbeat-high-performance-monitoring-alarm-system/

lllll

Share free open-source source code

Previous article： Free Git code hosting service, YYDS out of the box

Next article： C++ serializes open source libraries and can be converted in three lines of code

Q&A

Ordering Process

1. Automatic: After making an online payment, click the (Download) link to download the source code; 2. Manual: Contact the seller or the official to check if the template is consistent. Then, place an order and make payment online. The seller ships the goods, and both parties inspect and confirm that there are no issues. ICTcoder will then settle the payment for the seller. Note: Please ensure to place your order and make payment through ICTcoder. If you do not place your order and make payment through ICTcoder, and the seller sends fake source code or encounters any issues, ICTcoder will not assist in resolving them, nor can we guarantee your funds!

View details

Transactions and Disputes

1. Default transaction cycle for source code: The seller manually ships the goods within 1-3 days. The amount paid by the user will be held in escrow by ICTcoder until 7 days after the transaction is completed and both parties confirm that there are no issues. ICTcoder will then settle with the seller. In case of any disputes, ICTcoder will have staff to assist in handling until the dispute is resolved or a refund is made! If the buyer places an order and makes payment not through ICTcoder, any issues and disputes have nothing to do with ICTcoder, and ICTcoder will not be responsible for any liabilities!

View details

Matters needing attention

1. ICTcoder will permanently archive the transaction process between both parties and snapshots of the traded goods to ensure the authenticity, validity, and security of the transaction! 2. ICTcoder cannot guarantee services such as "permanent package updates" and "permanent technical support" after the merchant's commitment. Buyers are advised to identify these services on their own. If necessary, they can contact ICTcoder for assistance; 3. When both website demonstration and image demonstration exist in the source code, and the text descriptions of the website and images are inconsistent, the text description of the image shall prevail as the basis for dispute resolution (excluding special statements or agreements); 4. If there is no statement such as "no legal basis for refund" or similar content, any indication on the product that "once sold, no refunds will be supported" or other similar declarations shall be deemed invalid; 5. Before the buyer places an order and makes payment, the transaction details agreed upon by both parties via WhatsApp or email can also serve as the basis for dispute resolution (in case of any inconsistency between the agreement and the description of the conflict, the agreement shall prevail); 6. Since chat records and email records can serve as the basis for dispute resolution, both parties should only communicate with each other through the contact information left on the system when contacting each other, in order to prevent the other party from denying their own commitments. 7. Although the probability of disputes is low, it is essential to retain important information such as chat records, text messages, and email records, in case a dispute arises, so that ICTcoder can intervene quickly.

View details

ICTcoder reminds and declares

1. As a third-party intermediary platform, ICTcoder solely protects transaction security and the rights and interests of both buyers and sellers based on the transaction contract (product description, agreed content before the transaction); 2. For online trading projects not on the ICTcoder platform, any consequences are unrelated to this platform; regardless of the reason why the seller requests an offline transaction, please contact the administrator to report.

View details