Why
The OTLP/JSON adapter is covered by the protocol fixture, JavaScript SDK output, Collector normalization, and a deterministic two-resource harness. It still needs evidence from an external application-shaped export.
Needed fixture
An anonymized decoded OTLP/JSON Event batch that exercises real resource attributes, event attributes, timestamps, and trace context without customer or company data.
Questions
- Is millisecond truncation acceptable when exact nanoseconds remain under
otel?
- Are nested semantic attribute paths readable in laws?
- Is cross-request ordering available or explicitly absent?
- Which records are ordinary logs rather than Events?
Sanitize all identifying data before attaching a fixture.
Why
The OTLP/JSON adapter is covered by the protocol fixture, JavaScript SDK output, Collector normalization, and a deterministic two-resource harness. It still needs evidence from an external application-shaped export.
Needed fixture
An anonymized decoded OTLP/JSON Event batch that exercises real resource attributes, event attributes, timestamps, and trace context without customer or company data.
Questions
otel?Sanitize all identifying data before attaching a fixture.