clarify per-platform behavior in UI

elastic · Jun 6, 2023 · c08703d · c08703d
1 parent 2a87148
commit c08703d
Showing 1 changed file with 4 additions and 3 deletions.
diff --git a/specs/agents/tracing-spans.md b/specs/agents/tracing-spans.md
@@ -38,10 +38,11 @@ If a span is created without a valid `name`, the string `"unnamed"` SHOULD be us
 Span execution within a transaction or span can be synchronous (the caller waits for completion), or asynchronous (the caller does not wait
 for completion).
 
-In UI
+In UI:
+
 - when `sync` field is not present or `null`, we assume it's the platform default and no badge is shown.
-- when `sync` field is set to `true`, a `blocking` badge is shown in traces.
-- when `sync` field is set to `false`, an `async` badge is shown in traces.
+- when `sync` field is set to `true`, a `blocking` badge is shown in traces where the platform default is `async`: `nodejs`, `rum` and `javascript`
+- when `sync` field is set to `false`, an `async` badge is shown in traces where the platform default is `blocking`: other agents
 
 ### Span outcome