Log Monitoring System (copy) preface: The Age of the university, the Good times. Know the wow~, not the level of the Ashes players. (Level 80 starts to play.) Played the FB inside feel the copy is best to play. Undead FS side dish than one. The <PVP is too low. >,so is going to take this system as a hit FB.
Initial issues to solve: 1. For achievement ~ (the current project's journal uses the liunx grep command, which executes a log of the read item once in 3 minutes.) Cons: Non-real-time, take up 1 CPUs, full of 100%~~) 2. Good want frost sad. (The interface item now needs to invoke a lot of data from the system and then save the data to the local database.) Currently, these two operations are performed synchronously. Database IO has a bottleneck and intends to take the operation of the database separately to the project. )
Staff configuration: Logback + flume + Kafka + Storm
Basic ideas:
1, Logback in the project as the output of the log, Appender point to Flume, active push log
2., fluem as a log collection block, to get the log after. Sink directed to a different place
3, Flume sink directed to Kafka as Kafka producer, released a topic
4, Strom spout use Kafka spout, subscribed Kafka as topic, rewrite Bolt as the logic of processing
Just started to engage in the eradication of the group in Ing. Progress-Perfect update ...
