Zipkin Description
It is used to gather timing data required to troubleshoot latency issues in service architectures. This data can be collected and searched. You can jump to a trace ID if you have it in a log. You can also query by attributes like service, operation name and tags. You will receive a summary of some interesting data, such as how much time you spent on a particular service and whether or not the operation failed. Zipkin UI displays a dependency graph that shows how many traced requests passed through each application. This can be used to identify aggregate behavior, such as error paths or calls made to deprecated service.