Thuum Playground

Metric Broker

A programmer's calculator for the Metric Broker: build Tags, encode values, compose and decode frames byte by byte, then publish, subscribe and query the real broker.

Group C84A Open a second window ↗ New sandbox Docs ↗

Fields: count op group id x digit y digit x y code

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

dtype tag hex

x sns time in ns, set by the server, rounded down to the nanosecond

The server sets x when the pub arrives, rounded down to the nanosecond.

If the pub arrives at

Required.

y f32 float, 4 B

Number

on the wire (4 B, little-endian) CDCCCC3D

as read (most significant first) 3D CC CC CD

in JSON 0.10000000149011612 Docs ↗

You may write what you typed: the broker rounds it to the nearest f32, and its replies carry this.

0 sign 01111011 exponent (8 bits) 10011001100110011001101 mantissa (23 bits) = 0x3DCCCCCD

kind: normal
sign: 0 ⇒ +
exponent (8 bits): 123 − 127 ⇒ 2^-4
significand: 1 + 5033165 / 2²³ = 1.60000002384185791015625
value stored: +2^-4 × 1.60000002384185791015625 = 0.100000001490116119384765625
typed: 0.1
stored − typed: 0.000000001490116119384765625

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 ↗

[0] op ack group tag sns_f32 x none: the server sets it y

address "C84A:3E01" in JSON: Group and Tag in one field
[1] op ack group

bytes 14 B json 79 B bytes is 82% smaller

bytes · the binary encoding, byte by byte

0200014AC8013 E0000BC41054AC8

[0] pub · 9 B
count	0200	2 bytes 0–1
op	01	pub byte 2
group	4AC8	51274 bytes 3–4
tag	013 E	3E01 · sns_f32 · id 1 x 3 sns y E f32 id 01 bytes 5–6
x	—	none: the server sets it
y	0000BC41	23.5 bytes 7–10
[1] sub-group · 3 B
op	05	sub-group byte 11
group	4AC8	51274 bytes 12–13

json · the same message as text Docs ↗

[

{ "op": "pub", "address": "C84A:3E01", "y": 23.5 },

{ "op": "sub-group", "group": "C84A" }

]

[0] pub
op		pub
address	4AC8013 E the same value as bytes	"C84A:3E01" group C84A (51274) x 3 sns y E f32 id 01 sns_f32
x	—	none: the server sets it
y	0000BC41 the same value as bytes	23.5
[1] sub-group
op		sub-group
group	4AC8 the same value as bytes	"C84A" ⇄ C84A (51274)

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 ↗

Frame

Read as

bytes · 14 B

0200010C00013 E0000BC41050C00

[0] pub · 9 B
count	0200	2 bytes 0–1
op	01	pub byte 2
group	0C00	12 bytes 3–4
tag	013 E	3E01 · sns_f32 · id 1 x 3 sns y E f32 id 01 bytes 5–6
x	—	none: the server sets it
y	0000BC41	23.5 bytes 7–10
[1] sub-group · 3 B
op	05	sub-group byte 11
group	0C00	12 bytes 12–13

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

bytes Not connected

sent: 0 frames · 0 B
received: 0 frames · 0 B

json Not connected

sent: 0 frames · 0 B
received: 0 frames · 0 B

Send ops

[0] op ack group tag sns_f32 x none: the server sets it y

address "C84A:3E01" in JSON: Group and Tag in one field

Your Tokens only reach Group C84A: any other Group is refused by the broker itself (forbidden).

Connect first: the buttons above open each connection.

Send a frame by hand

A frame as you type it, sent as is, malformed or not: see what the broker does with it. A bad bytes frame closes the connection (1007); text on a bytes connection, or binary on a json one, closes it too (1003). Docs ↗

a binary frame of 5 B

Measurements received

No measurements yet: subscribe a connection to the Group, then publish.

REST

Docs ↗

tag (hex) address C84A:3E01 · sns_f32

x: none: the server sets it

POST /api/thuum/metric/data

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

Through the portal, with a Token for Group C84A only.

Frames

Every frame sent and received, newest first. Open one to see it byte by byte.

Nothing sent or received yet.

A shared demo on Thuum's own Domain: data is kept for 24 hours, at most 1000 points per Group. Don't put anything private here. Docs ↗