Skip to main content

Telemetry

Every node reports to the Orbinum telemetry dashboard by default — block height, finalized height, peer count, transaction pool, propagation time, version and approximate location. Your node appears within seconds of starting, under the name in VALIDATOR_NAME / RPC_NAME.

It is an outbound connection: no port to open, no firewall rule, and it works on a node whose RPC is loopback-only.

Two hosts, on purpose

Nodes submit to wss://telemetry.orbinum.io/submit/. The dashboard you open in a browser is telemetry.orbinum.network. The mismatch is not a typo — do not point one at the other.

The value​

node-deploy already sets this per role:

TELEMETRY_URL=--telemetry-url "wss://telemetry.orbinum.io/submit/ 1"   # validators
TELEMETRY_URL=--telemetry-url "wss://telemetry.orbinum.io/submit/ 0"   # RPC and archive

Three parts of that string are load-bearing:

  • The quotes stay. The node parses "<url> <level>" as a single argument. Without them the level is read as a separate flag and startup fails.
  • The trailing slash stays. /submit without it does not upgrade.
  • The digit is the verbosity level, not a placeholder.

Levels​

Run at 0. Level 1 is for nodes in the validator set.

A message is sent when its own level is at or below the configured one, so 1 sends everything 0 sends, plus the consensus feed:

LevelMessagesWhat they carry
0system.connected, system.interval, block.import, notify.finalized, txpool.import, sysinfo.hwbenchName, version, chain, OS/arch, startup time; every ~5 s peers, best and finalized height, tx count, bandwidth; each imported and finalized block; the startup hardware benchmark
1afg.authority_set, afg.finalized_blocks_up_to, afg.received_propose / prevote / precommit / commit, afg.applying_*_authority_set_change, slots.pre_sealed_block, slots.discarding_proposal_took_too_long, prepared_block_for_proposingYour GRANDPA authority id and the current set, each finality advance, the votes you see, every block you author and seal, and proposals you drop for running past the slot

Levels above 1 (4 warn, 5 debug, 9 trace) exist in the software but are not used on Orbinum.

Optional for RPC and development nodes; validators must stay on telemetry — see Must stay on.

Changing it needs a recreate, not a restart​

restart keeps the old arguments; recreate after editing the value — see Config changes need a recreate:

docker compose up -d --force-recreate

Opting out​

Set the variable empty and recreate. That genuinely silences the node: the chain spec carries "telemetryEndpoints": [], so there is no fallback destination.

That emptiness is deliberate. The spec previously inherited Parity's endpoint from its source, which meant opting out quietly redirected the same data to telemetry.polkadot.io rather than stopping it.