The integration suite runs against openzipkin/zipkin:3.6.1 (the Grow stack catalog tag) with
in-memory storage, AUTOCOMPLETE_KEYS=grow.test,http.method and COLLECTOR_GRPC_ENABLED=true
(test-only additions to the stack template). Zipkin 3.x servers with the same v2 API are expected to
work; the v1 API (removed from the Zipkin 3 query side) is not supported.
Every public function is called against the real service in the Docker suite. These behaviours
cannot be produced by the stock container; they are covered by unit tests with mocked HTTP:
Behaviour
Languages
Reason
AUTHENTICATION / PERMISSION_DENIED (401/403)
all
Zipkin has no authentication; only a gateway in front of it answers 401/403
RATE_LIMITED, Retry-After, retries with backoff
all
Zipkin has no rate limiting
health() with DOWN (HTTP 503)
all
in-memory storage cannot fail
VALIDATION for an oversized batch (HTTP 413)
all
needs a request above Armeria's 10 MiB limit
TLS, client certificates, proxy
all
the stock image serves plain HTTP
OTLP export (protocol: grpc / http/protobuf)
all
needs an OpenTelemetry Collector with a zipkin exporter; not part of the fixture
getDependencies on persistent storage
all
needs the zipkin-dependencies batch job; in-memory storage computes edges on read (tested)
getTraceMany chunking above 100 ids and re-ordering
all
storage dependent; tested with recorded fixtures
No function returns UNSUPPORTED against Zipkin 3.6.1. serverVersion() returns UNSUPPORTED
only when a server or gateway exposes no /info version.
The API is the same in every language; only the conventions differ (naming, durations, async
model). Deliberate differences:
Topic
Difference
Closed client
every call on a closed client fails with CANCELLED ("client is closed"); initTracing on a closed client fails with CONFIG — the same in all five languages
TracingConfig defaults (Rust, Java)
the shared TracingConfig cannot tell "unset" from "default". In Rust a field still at its TracingConfig::new value counts as unset (environment, then the Zipkin default); in Java the generic default protocol (http/protobuf), the default propagators and gzip compression count as unset. So protocol falls back to GROW_ZIPKIN_PROTOCOL or native. To force OTLP over HTTP in code use ZipkinTracingOptions::protocol(Protocol::HttpProtobuf) (Rust) or ZipkinTracing.Options.builder().protocol(Protocol.HTTP_PROTOBUF) (Java). TypeScript, Go and Python have real "unset" values
Normalized spans
TypeScript and Python return ZipkinTraceSpan (the SPEC span plus remoteEndpoint, shared, debug). The SPEC Span in Go, Rust and Java has no room for them (Java records), so these fields stay on the native ZipkinSpan (getTraceSpans)
getDependencies
TypeScript, Python and Rust return ZipkinDependencyLink (with errorCount) from one method that takes both window styles. Go has GetDependencies (category DependencyLink) and GetDependenciesAt(endTs, lookback) (ZipkinDependencyLink); Java has getDependencies(start, end) (category) and getDependencies(endTs, lookback) (Zipkin)
health() details
the storage detail is an object in TypeScript and compact JSON text in the other languages (their detail maps hold strings)
Event annotations
an event with attributes becomes the JSON text {"<name>":{…}}; the key order inside may differ (Rust sorts keys)
buildAnnotationQuery
tag terms follow the map order (insertion order in TypeScript, Python and Java; sorted in Go and Rust)
Environment in Java
Java cannot change the process environment, so loadEnv sets system properties instead and returns the names it set