24 lines
1.2 KiB
Markdown
24 lines
1.2 KiB
Markdown
## Zipkin receiver
|
|
The Zipkin receiver makes the OAP server work as an alternative Zipkin server implementation. It supports Zipkin v1/v2 formats through HTTP service.
|
|
Make sure you use this with `SW_STORAGE=zipkin-elasticsearch` option to activate Zipkin storage implementation.
|
|
Once this receiver and storage are activated, SkyWalking's native traces would be ignored, and SkyWalking wouldn't analyze topology, metrics, and endpoint
|
|
dependency from Zipkin's trace.
|
|
|
|
Use the following config to activate it.
|
|
```yaml
|
|
receiver-zipkin:
|
|
selector: ${SW_RECEIVER_ZIPKIN:-}
|
|
default:
|
|
host: ${SW_RECEIVER_ZIPKIN_HOST:0.0.0.0}
|
|
port: ${SW_RECEIVER_ZIPKIN_PORT:9411}
|
|
contextPath: ${SW_RECEIVER_ZIPKIN_CONTEXT_PATH:/}
|
|
jettyMinThreads: ${SW_RECEIVER_ZIPKIN_JETTY_MIN_THREADS:1}
|
|
jettyMaxThreads: ${SW_RECEIVER_ZIPKIN_JETTY_MAX_THREADS:200}
|
|
jettyIdleTimeOut: ${SW_RECEIVER_ZIPKIN_JETTY_IDLE_TIMEOUT:30000}
|
|
jettyAcceptorPriorityDelta: ${SW_RECEIVER_ZIPKIN_JETTY_DELTA:0}
|
|
jettyAcceptQueueSize: ${SW_RECEIVER_ZIPKIN_QUEUE_SIZE:0}
|
|
```
|
|
|
|
NOTE: Zipkin receiver requires `zipkin-elasticsearch` storage implementation to be activated.
|
|
Read [this](backend-storage.md#elasticsearch-with-zipkin-trace-extension) doc to learn about Zipkin as a storage option.
|