public final class SpanBytesDecoderDetector extends Object
For example, we can identify the encoding and also the format in http via the request path and content-type. However, in Kafka it could be that folks send mixed Zipkin data without identifying its format. For example, Kafka historically has no content-type and users don't always segregate different queues by instrumentation format.
| Modifier and Type | Method and Description |
|---|---|
static BytesDecoder<Span> |
decoderForListMessage(byte[] spans) |
static BytesDecoder<Span> |
decoderForMessage(byte[] span) |
public static BytesDecoder<Span> decoderForMessage(byte[] span)
IllegalArgumentException - if the input isn't a v1 json or thrift single-span messagepublic static BytesDecoder<Span> decoderForListMessage(byte[] spans)
IllegalArgumentException - if the input isn't a json, proto3 or thrift list message.Copyright © 2015–2019 OpenZipkin. All rights reserved.