W3C tracestate — List Members, Limits and Rejects (txt)
tracestate header values covering vendor-prefixed keys, optional whitespace, the exact 32-member limit and a 33-member case that must lose its last member rather than its first — plus duplicate keys, uppercase keys, a bare key and an over-long key that must be rejected.
# W3C Trace Context `tracestate` header values, one per line. '#' lines are commentary.
# --- valid ---
shop=t61rcWkgMzE,congo=t61rcWkgMzE
rojo=00f067aa0ba902b7,congo=t61rcWkgMzE
vendor1@shop=abc123,vendor2@shop=def456
# optional whitespace around list members is allowed and must be stripped
shop=one , congo=two
# up to 32 list members are allowed
v00=value00,v01=value01,v02=value02,v03=value03,v04=value04,v05=value05,v06=value06,v07=value07,v08=value08,v09=value09,v10=value10,v11=value11,v12=value12,v13=value13,v14=value14,v15=value15,v16=value16,v17=value17,v18=value18,v19=value19,v20=value20,v21=value21,v22=value22,v23=value23,v24=value24,v25=value25,v26=value26,v27=value27,v28=value28,v29=value29,v30=value30,v31=value31
# --- invalid or lossy ---
# 33 list members: the tail must be dropped, not the head
v00=value00,v01=value01,v02=value02,v03=value03,v04=value04,v05=value05,v06=value06,v07=value07,v08=value08,v09=value09,v10=value10,v11=value11,v12=value12,v13=value13,v14=value14,v15=value15,v16=value16,v17=value17,v18=value18,v19=value19,v20=value20,v21=value21,v22=value22,v23=value23,v24=value24,v25=value25,v26=value26,v27=value27,v28=value28,v29=value29,v30=value30,v31=value31,v32=value32
# duplicate keys
shop=one,shop=two
# uppercase key
SHOP=one
# empty value with no '='
shop
# key longer than 256 characters
kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk=one
Specifications
- Valid Cases
- 5
- Invalid Cases
- 5
- Max List Members
- 32
- Over Limit Case
- 33
- Spec
- W3C Trace Context Level 1
Testing contract
Reference control- Scenario
- Parse each header value and apply the specification's mutation rules.
- Expected result
- The 32-member line survives intact, the 33-member line drops its last member while keeping v00 first, and the five malformed lines are rejected.
What is a .txt file?
TXT is a plain-text file containing unformatted character data with no styling or structure beyond line breaks. Its interpretation depends on character encoding, most commonly UTF-8, and on line-ending convention. It is the most universal and portable text container.
How to use this file
Use an example TXT to test encoding detection, line-ending (LF versus CRLF) handling, and any tool that reads or streams raw text input.
How to use this file for testing
“W3C tracestate — List Members, Limits and Rejects (txt)” is a deterministic Novus Examples fixture for Observability, Schema validation, Config parsing. Structured and plain-text telemetry with known timestamps, levels, request identifiers, and error states for testing log ingestion, correlation, dashboards, and alert pipelines.
Documented properties for this file: TXT · 1,602 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Telemetry fixtures use fixed trace IDs, span IDs, and timestamps so ingestion is reproducible run to run. Point your collector, parser, or query layer at the file and assert the documented span tree, metric families, or severity mix; service and host names are invented.
Related files
- yamlService Level Objectives — Two SLOs in One Multi-Document YAML (yaml)Two SLOs — availability and latency — in one multi-document YAML separated by ---, each defined as a ratio of good events to total over a rolling 28-day window. The latency SLO measures the le="1" bucket against the count, which is the correct way to do it from a histogram.
- jsonOTLP Trace — All-Zero Trace and Span IDs, Intentionally Invalid (json)A trace whose trace ID and root span ID are all zeroes — the value an uninitialised context produces. Intentionally invalid: the specification defines all-zero IDs as invalid, so a conformant receiver must reject the spans instead of creating a permanent bucket that every broken service writes into.
- jsonOTLP Trace — Duplicate Span IDs, Intentionally Invalid (json)Two different spans share one span ID inside a single trace, which the specification forbids. Intentionally invalid: it is the fixture for the de-duplication path, where a naive store silently overwrites one span with the other and loses a subtree.
- jsonOTLP Trace — Empty but Valid Batch (json)A structurally valid OTLP export containing no spans at all — what an exporter sends when every span in the interval was sampled out. The empty-input case that ingestion code routinely mistakes for an error.
- jsonOTLP Trace — Negative and Zero Durations, Intentionally Invalid (json)One span ends 8.4 ms before it started and another has identical start and end timestamps. Intentionally invalid: negative durations poison latency aggregates — a single one can drag a p99 below zero — so this is the fixture for the validation that must sit in front of any duration metric.
- jsonOTLP/JSON Trace — 13-Span Checkout Request (json)A complete OTLP/JSON trace export: one checkout request across five services as 13 spans, four levels deep, with HTTP, database, RPC and messaging semantic-convention attributes, span events and a producer span. Trace and span IDs are fixed, so ingesting it twice produces identical output.
Generated by generation/observability.py. Free for any use, no attribution required — license.