Module json 

OTLP/HTTP with a JSON body.

JSON is a normative encoding of OTLP, not an extra: the browser SDK emits it, and it is what anyone reaches for with curl. The three endpoints in crate::receiver dispatch on content-type and land here.

No new dependency. The document is parsed by the same yaml_rust2 loader that reads queries and config (api::parse), because YAML 1.2 is a superset of JSON — so this file is only the mapping from a parsed document onto the prost structs. It also means a KYAML body works, which is principle 5 falling out for free rather than being built.

Two places the OTLP JSON mapping is not the canonical protobuf one, and both are why an off-the-shelf reflective decoder is wrong here:

• trace_id, span_id and parent_span_id are hex, not base64. A 32-character hex string is also valid base64, so a canonical decoder does not fail on one — it silently produces 24 bytes of nonsense. Every other bytes field really is base64.
• 64-bit integers are strings. time_unix_nano arrives as "1544712660300000000" because a JSON number cannot hold it exactly. Numbers are accepted too; emitters disagree.

Everything here is lenient in the directions the spec allows and strict where being lenient would store the wrong bytes: a field name may be either lowerCamelCase or the original proto name, an enum may be its name or its number, but an id of the wrong length is an error rather than a truncation.

Constants

SEVERITY 🔒

SPAN_KIND 🔒

STATUS_CODE 🔒

TEMPORALITY 🔒

Functions

any_value 🔒

base64 🔒

Standard base64 with padding, which is what proto3 JSON uses for every bytes field that is not an id. URL-safe input is accepted because it costs two match arms and a rejected attribute value is a lost attribute value.

boolean 🔒

buckets 🔒

data_points 🔒

dropped 🔒

enumerate 🔒

An enum, as its proto name or as its number. names[i] is the name of value i; every OTLP enum reached from here numbers from zero with no gaps.

exemplars 🔒

exp_histogram_points 🔒

f 🔒

Look up one field.

float 🔒

A double. proto3 JSON spells the three special values as strings, and lets any number arrive as a string as well.

floats 🔒

hex 🔒

A trace or span id: lowercase or uppercase hex, exactly want bytes.

histogram_points 🔒

i32f 🔒

int 🔒

A 64-bit integer, as a JSON number or — the proto3 JSON default, because a double cannot hold one exactly — as a string.

key_values 🔒

list 🔒

Absent, null and “present but empty” are the same thing to every caller here: proto3 has no way to tell them apart on the wire either.

log_record 🔒

logs

metric_of 🔒

metrics

missing 🔒

number_points 🔒

number_value 🔒

The asDouble / asInt oneof, shared by NumberDataPoint and Exemplar.

opt_float 🔒

optional double in the proto, so absent and 0 are different values and the difference is visible in a histogram.

resource 🔒

s 🔒

scope 🔒

scope_logs 🔒

scope_metrics 🔒

scope_spans 🔒

span 🔒

summary_points 🔒

temporality 🔒

top 🔒

The one top-level member of an export request, in either dialect.

traces

u32f 🔒

uint 🔒

Unsigned 64-bit. Values above i64::MAX are legal for fixed64/uint64 and arrive as strings, so they are parsed as u64 rather than routed through int, which would reject them.

uints 🔒

Type Aliases

R 🔒