Distributed trace with Zipkin
- Zipkin is a distributed tracing system
- If you have a trace ID in a log file, you can directly found the
trace. Otherwise need to query based on attributes such as service,
operation name, tags and duration.
- The Zipkin UI also presents a dependency diagram showing how many
traced requests went through each application.
- The most popular ways to report data to Zipkin are via http or
Kafka, though many other options exist, such as Apache ActiveMQ,
gRPC and RabbitMQ.
- The data served to the UI is stored in-memory(internal memory)
- The InMemoryStorage component is packaged in zipkin's core
- InMemoryStorage neither persistent nor viable for realistic work
loads, only purpose for testing
- Data can be supported backend such as Apache Cassandra or
- You can also start Zipkin via Docker.
- Its minimum Java language level is 6
- Zipkin Slim is smaller and starts faster
- It supports in-memory and Elasticsearch storage
- It does NOT support messaging transports like Kafka or RabbitMQ