zipkin is a distributed link call monitoring system, which aggregates the call delay data of various business systems to achieve link call monitoring and tracking.
Zipkin is an open source project of Twitter that allows developers to collect monitoring data on Twitter's various services and provide query interfaces.
Zipkin is a distributed tracing system. It helps gather timing data needed to troubleshoot latency problems in microservice architectures. It manages both the collection and lookup of this data. Zipkin’s design is based on the Google Dapper paper.
This project includes a dependency-free library and a spring-boot server. Storage options include in-memory, JDBC (mysql), Cassandra, and Elasticsearch.
zipkin mainly involves four components collector storage search web UI
Collector receives data transmitted by each service
As a kind of Storage, Cassandra can also be mysql, etc. It is stored in memory by default. For configuring cassandra, please refer to here
Query is responsible for querying the data stored in Storage, providing a simple JSON API to obtain data, mainly for web UI use
Web provides a simple web interface
Zipkin uses Apache Cassandra as the data storage system, Apache ZooKeeper - the Hadoop configuration management software - for coordination, and Facebook's Scribe data aggregation system as the logging framework to transport the trace data.
zipkin action
Full link tracking tool (depending on dependencies)
View the execution speed of each interface and each service (locate the point of the problem or find the performance bottleneck)
How zipkin works
Create some tracking identifiers (tracingId, spanId, parentId), and finally build a request process tree
zipkin architecture
in:
Collector receives data transmitted by each service;
As a kind of Storage, Cassandra can also be mysql, etc. It is stored in memory by default. For configuring cassandra, please refer to here;
Query is responsible for querying the data stored in Storage, providing a simple JSON API to obtain data, mainly for web UI use;
Web provides a simple web interface;
The purpose of the zipkin distributed tracing system:
zipkin is a distributed link call monitoring system, which aggregates the call delay data of various business systems to achieve link call monitoring and tracking;
By collecting trace data, zipkin can help developers deeply understand how a specific request is executed in a distributed system;
If we now have a user request timeout, we can display the timeout request call chain in the UI; we can quickly locate what is causing the slow response service. If the details of this service are also very clear, then we can also locate which problem in the service caused the timeout;
The zipkin system allows developers to easily collect and analyze data through a web front-end, such as the processing time of each user request service, etc., and can easily monitor the bottlenecks in the system.