Service dependencies from the native topology (callCount is 0: the topology carries no
counts). OAP 10.4 does not implement Zipkin /dependencies, so the zipkin backend throws
UnsupportedError; OTLP spans create no topology edges.
One trace in the SPEC model, null when it does not exist. Zipkin rejects non-hex ids with
ValidationError.
Operation names of a service (Zipkin span names and/or native endpoint names), sorted.
Service names (sorted, unique). New services appear about 30–35 s after their first data (OAP flushes its name index periodically).
SPEC search. Zipkin: service → serviceName, operation → spanName (lower-cased like
OAP stores names), tags → annotationQuery (k=v and …; keys must be in
SW_ZIPKIN_SEARCHABLE_TAG_KEYS), durations in µs, endTs = end (default now), lookback
= end - start. Native: queryTraces with operation as endpoint name and durations in ms.
Polls getTrace until the trace has minSpans spans (TimeoutError otherwise).
Native ids are used verbatim; hex ids are normalized.
TraceQueryClient for SkyWalking. OTLP spans (what
initTracingsends) are stored in OAP's Zipkin model and read via the Zipkin query API (:9412/zipkin, needsSW_QUERY_ZIPKIN); SkyWalking agent segments are read via GraphQL. The backend comes fromSkyWalkingConfig.traceBackend:zipkinnativeauto(default)getTracesearchTracesqueryTraceslistServices,listOperationsgetDependenciesUnsupportedErrorNative traces keep their opaque ids (
<hex>.<n>.<ms>); native span ids are"<segmentId>-<spanId>". Obtain it fromSkyWalkingClient.traces.