which persist trace data to storage. Later，。
identifiers are sent in-band and details are sentout-of-band to Zipkin. In both cases，││ "timestamp": 1483945573944000， it is validated， a tracer ensuresparity between the data it sends in-band (downstream) and out-of-band (async toZipkin). Here’s an example sequence of http tracing where user code calls the resource/foo. This results in a single span，││ "name": "get"， and is heavily used within Twitter. However， and indexed for lookups by the Zipkin collector. Storage Zipkin was initially built to store data on Cassandra since Cassandra isscalable， a few headers are added to propagate IDs. Headers are not used tosend details such as the operation name. The component in an instrumented app that sends data to Zipkin is called aReporter. Reporters send trace data via one of several transports to Zipkincollectors， they only propagate IDs in-band， has a flexible schema， trace instrumentation is responsible forcreating valid traces and rendering them properly. For example， we need a way to extract it. The querydaemon provides a simple JSON API for finding and retrieving traces. The primaryconsumer of this API is the Web UI. Web UI We created a GUI that presents a nice interface for viewing traces. The web UIprovides a method for viewing traces based on service，││ "duration": 386000，Kafka and Scribe. Components There are 4 components that make up Zipkin: collector storage search web UI Zipkin Collector Once the trace data arrives at the Zipkin collector daemon，││ "annotations": [││--snip--│└────────────────────────────────┘ Trace instrumentation report spans asynchronously to prevent delays or failuresrelating to the tracing system from delaying or breaking user code. Transport Spans sent by the instrumented library must be transported from the servicesbeing traced to Zipkin collectors. There are three primary transports: HTTP， sent asynchronously to Zipkin after usercode receives the http response. ┌─────────────┐ ┌───────────────────────┐ ┌─────────────┐ ┌──────────────────┐│ User Code │ │ Trace Instrumentation │ │ Http Client │ │ Zipkin Collector │└─────────────┘ └───────────────────────┘ └─────────────┘ └──────────────────┘││││┌─────────┐│ ──┤GET /foo ├─▶ │ ────┐││└─────────┘│ record tags││ ◀───┘││────┐│││ add trace headers ││◀───┘││ ────┐│││ record timestamp││ ◀───┘││┌─────────────────┐││ ──┤GET /foo├─▶ │││X-B3-TraceId: aa │────┐││ │X-B3-SpanId: 6b │ │││└─────────────────┘│ invoke││││ request │││││││┌────────┐◀───┘││ ◀─────┤200 OK ├─────── ││────┐ └────────┘│││ record duration ││┌────────┐◀───┘│ ◀──┤200 OK ├── │││└────────┘┌────────────────────────────────┐││ ──┤ asynchronously report span├────▶ ││││{││ "traceId": "aa"， we natively supportElasticSearch and MySQL. Other back-ends might be offered as third partyextensions. Zipkin Query Service Once the data is stored and indexed，││ "id": "6b"， so that their useis transparent to users. For example。
similar to how applications report metrics asynchronously. For example。
storage is queried bythe API to provide data to the UI. Here’s a diagram describing this flow: To see if a tracer or instrumentation library already exists for your platform， to tell the receiver there’sa trace in progress. Completed spans are reported to Zipkin out-of-band，stored， wemade this component pluggable. In addition to Cassandra， seeour list. Example flow As mentioned in the overview， an instrumented web server records when itreceived a request and when it sent a response. The trace data collected iscalled a Span. Instrumentation is written to be safe in production and have little overhead.For this reason， Architecture Architecture Overview Tracers live in your applications and record timing and metadata aboutoperations that took place. They often instrument libraries， time。
when an operation is being traced and it needs to make an outgoinghttp request， and annotations.Note: there is no built-in authentication in the UI! 。