Shulou(Shulou.com)06/01 Report--

It is believed that many inexperienced people have no idea about what the open-falcon architecture is like. Therefore, this article summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

I. introduction

Xiaomi open source monitoring tool, based on go language implementation

II. Architecture diagram

1.falcon-agent:

Data acquisition component, built-in http interface, collect defined data and report it to transfer

2.transfer

Agent establishes a long link with transfer and reports the data to transfer,transfer by default. On port 8433, agent will push the data through jsonrpc, and transfer will pass the data to judge and graph.

3.graph

The graph component stores drawing data and historical data. Transfer will transmit the received data to graph with listening port 6071

4.query

Query interface for drawing data, because graph is stored in fragments. If you want to transfer it to dashboard, you need query to collect data and aggregate it before showing it to the user.

5.dashboard

Dashboard is a user-oriented query interface, where users can see all the data from push to graph and view their trend charts.

6.judge

In order to make an alarm judgment, Judge needs to read the alarm policy from the portal database first, but there are many Judge instances, so it will cause a lot of pressure to read the database, so you can make heartbeat become the db cache cache, heartbeat reads the data from the database to memory, Judge calls the rpc interface of heartbeat to get the alarm policy, and the alarm events are stored in redis.

7.alarm

Handle alarm events stored in redis by judge

8.sender

Call mail-privider and sms-privider provided by various companies, according to a certain degree of concurrency, read emails from redis, send text messages and send them. Alarm messages and emails generated by alarm can be directly written to redis and sent by sender.

9.portal

Configure alarm policies to write to the database

10.hbs

Heartbeat server, falcon-agent will send heartbeat to heartbeat server every minute and report its own version, hostname, ip and so on. Pull plug-ins and special collection items to be executed from heartbeat. This information requires heartbeat to access Portal's database to obtain. In order to make an alarm judgment, Judge needs to read the alarm policy from the portal database first, but there are many Judge instances, so it will cause a lot of pressure to read the database, so you can make heartbeat become the db cache cache, heartbeat reads the data from the database to memory, and Judge calls the rpc interface of heartbeat to get the alarm policy.

After reading the above, have you mastered the method of open-falcon architecture? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.