From f29d75b98ab1602f4c8bf422720ee981997013b4 Mon Sep 17 00:00:00 2001 From: Marcin Grzejszczak Date: Fri, 11 Mar 2016 10:26:40 +0100 Subject: [PATCH] Added additional explanation to exportable param --- docs/src/main/asciidoc/features.adoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/src/main/asciidoc/features.adoc b/docs/src/main/asciidoc/features.adoc index f6a7dcfda..d440d0ada 100644 --- a/docs/src/main/asciidoc/features.adoc +++ b/docs/src/main/asciidoc/features.adoc @@ -13,7 +13,9 @@ notice the `[appname,traceId,spanId,exportable]` entries from the MDC: - *spanId* - the id of a specific operation that took place - *appname* - the name of the application that logged the span - *traceId* - the id of the latency graph that contains the span - - *exportable* - whether the log should be exported to Zipkin or not + - *exportable* - whether the log should be exported to Zipkin or not. When would you like the span not to be + exportable? In the case in which you want to wrap some operation in a Span and have it written to the logs + only. * Provides an abstraction over common distributed tracing data models: traces, spans (forming a DAG), annotations, key-value annotations. Loosely based on HTrace, but Zipkin (Dapper) compatible.