Metric Broker

A Tag is 16 bits: an x digit, a y digit (together, the dtype) and an id. Pick or type any part; the rest follows. Docs ↗

x digit

3 · sns · time in ns, set by the server, rounded down to the nanosecond · x in a pub: 0 B, in meas: 8 B

y digit

E · f32 · float, 4 B · kk 11 ww 10

id

01 · 1

on the wire

013 E little-endian: the id byte first, then the dtype

address

"7B19:3E01" the address of this Tag in your sandbox's Group 7B19: JSON and REST name one series this way 197B013 E on the wire: the Group's two bytes, then the Tag's (little-endian)

dtype

sns_f32 · pub 9 B · meas 17 B · mb_data_tf

Tags of this dtype

3E00–3EFF (15872–16127)

interpolation

step-hold · linear · spline Docs ↗

Type x and y the way people write them, and see the bytes the Tag's dtype puts on the wire. Docs ↗

Compose a message from ops and see it whole: count, then each op, every byte annotated. Next to it, the same message in JSON, and the size of each. Docs ↗

Paste a frame, as hex, bits or JSON, and get it back field by field. A malformed frame is decoded up to its first error, which is pointed at: the byte, the field and why. Docs ↗

Two real connections to the Metric Broker, one per encoding, on your sandbox's Group 7B19. Subscribe both, publish from one: the other receives the same measurement. Every frame below was on the wire. Docs ↗

{
  "measurements": [
    {
      "address": "7B19:3E01",
      "y": 21.5
    }
  ]
}