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

This article introduces the relevant knowledge of "what are the main core parts of Zipkin". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

OpenZipkin is mainly composed of four core parts.

Collector: responsible for collecting the data collected at the burial point of the probe Reporter, validating and processing and establishing the index.

Storage: stores the link data called by the service. Cassandra is used by default because Cassandra is heavily used within Twitter, and you can also replace it with Elasticsearch or MySQL.

API: link data that is formatted and indexed is provided as an API service, such as being called by UI.

UI: displays the link data of service invocation graphically.

The specific process is to introduce the service tracking code before and after the HTTP Client of the business, so that before the HTTP method "/ foo" is called, the trace information: TraceId:aa, SpanId:6b, annotation:GET / foo, and the timestamp:1483945573944000 of the current time are generated. After the result of the call is returned, the time-consuming duration is recorded, and then the trace information and duration are asynchronously uploaded to Zipkin Collector.

This is the end of the content of "what are the main core parts of Zipkin"? thank you for your reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

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.