Skip to content

Commit 3cf6426

Browse files
ivoanjoivoanjo
committed
Minor: Clarify trace-id/span-id are expected in W3C Trace Context format
1 parent 580100a commit 3cf6426

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

‎oteps/profiles/4947-thread-ctx.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -75,8 +75,8 @@ This is the attached thread record itself. SDK-side implementations may choose t
7575

7676
| Name | | Data type | Notes |
7777
| :-------------- | :--------- | :--------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------- |
78-
| trace-id | | uint8[16] | Zeroes can be used to indicate none active. If either of trace-id/span-id are set, both must be set. |
79-
| span-id | | uint8[8] | |
78+
| trace-id | | uint8[16] | In W3C Trace Context format. Zeroes can be used to indicate none active. If either of trace-id/span-id are set, both must be set. |
79+
| span-id | | uint8[8] | In W3C Trace Context format. |
8080
| valid | | uint8 | This value is set to 1 when the record is valid. Consumers should ignore this record if any other value is set when they read. |
8181
| _reserved | | uint8 | One spare byte here to align attrs-data-size at two byte boundary. |
8282
| attrs-data-size | | uint16 | Size of `attr-data`. This lets the reader know when it has consumed all `attr-data` records within the TLS buffer. |

0 commit comments

Comments
 (0)