Detailed architecture open-falcon

First, the introduction
of millet open source monitoring tools, go Based Language
II Chart
Detailed architecture open-falcon

1.falcon-agent:
data acquisition components, built-in http interfaces defined data collection reported to transfer
2.transfer
Agent establish a long link with the transfer, will report data to transfer, transfer default listening: the 8433 port, agent will pass jsonrpc way to push up the data, the data passed to transfer Judge, and Graph
3.graph
Graph component stores drawing data, historical data .transfer will receive data to Graph, listening port 6071
4.query
query drawing data interfaces, as graph fragment storage, if to be transmitted to the Dashboard, the need to collect data and polymerized in the query presented to the user
5.dashboard
Dashboard is a user-oriented query interface, where the user can see all the data push the graph, and view its trend
6.judge
judge alarms do judgment, need to read first from the alarm database portal strategy, but more judge instances, the database will have to read a lot of pressure, so you can make heartbeat become db cache cache , heartbeat cache data read from the database into memory, Judge rpc call the heartbeat of the interface, access to alarm strategy, Police incident into redis
7.alarm
treatment judge credited redis alarm event
8.sender
Call and mail-privider sms-privider provided by various companies, in accordance with a degree of concurrency, redis read from the message, and message transmission, generating alarms Alarm messages and alarm messages are written directly to redis, transmitted from the SENDER
. 9 .portal
configure alert policies written to the database
10.hbs
heartbeat server, falcon-agent heartbeats per minute will be sent to the heartbeat server, reporting their own version, hostname, ip and so on. Pull the plug and collect special items, etc. to be executed from the heartbeat. This information is required to access the Portal's database heartbeat to get. Judge judgment alarms do need to start reading the alarm database portal strategy, but more Judge instances, the database will have to read a lot of pressure, so you can make heartbeat become db cache buffer, heartbeat to read data from the database cache memory, Judge rpc call the heartbeat of the interface, access to alarm policy

Guess you like

Origin blog.51cto.com/haoyonghui/2463957