[Case]--Log Management Analysis Platform Case

I. Introduction

The system architecture of the project we are currently in contact with is as above, which belongs to the distributed microservice architecture. Characteristics such as scale and QPS determine that it is not a large-scale, high-concurrency, high-performance enterprise-level distributed microservice architecture. Therefore, the technology stack selection required by some business scenarios is also based on local conditions.
Insert image description here

Current project requirements require corresponding log management and analysis capabilities. Here we not only need to collect/search system logs (info, warn, error, etc.), but also need to process logs for special scenarios based on different business operation requirements, such as interface call record details. , interface call warning [set the threshold for the number of times a single interface is called, the threshold for the number of times a single interface is called by a single user, etc.], log report statistics, etc.

The popular ELK logging platform, why not choose it? <

Guess you like

Origin blog.csdn.net/xunmengyou1990/article/details/131501123