Early Access · beta. Help test and shape the 1.0 release. Where the project stands →

MessageFoundry™
Admin & monitoring console

Watch every interface, live

View connection health and throughput, trace messages, and replay failed deliveries. The browser console connects to the engine through its local API.

Get started See the whole toolkit →
The MessageFoundry monitoring console showing the live Connections dashboard: a left sidebar (Connections, Alerts, Dead Letters, Log Search, Engine Status, Users) and a table of interfaces with a status badge each — RUNNING, DEGRADED, FAILED, STOPPED — plus direction, method, per-connection logs, idle time, and counts for errored, read and written messages, queue depth, and backlog. The header shows the signed-in admin and a 2-second auto-refresh.
Every counter here is live from the engine — messages read, written, and errored per connection, plus queue depth and backlog — refreshed every couple of seconds, so what the dashboard shows is what the engine is actually doing. Nothing is counted that wasn't durably stored first: messages are persisted before they're acknowledged, then delivered at-least-once, so a failed delivery surfaces as a dead letter rather than a silent drop. How throughput really works →
Connection dashboard

Every interface, at a glance

The dashboard shows inbound and outbound connections in a table that refreshes automatically. Check status, throughput, and queued messages.

Open connection logs or start and stop a connection. Your role controls which actions you can use.

  • Status at a glance — RUNNING, DEGRADED, FAILED, or STOPPED — and a SIM tag when a destination is running in simulation.
  • Throughput, per connection — messages read, written, and errored, so a climbing error count is obvious immediately.
  • Queue depth & backlog — see exactly where messages are piling up, and how far behind a slow peer has fallen.
  • Per-connection logs — jump straight from a row to that interface's log stream.
  • Start / Stop / Actions — operate interfaces in place, permission-gated.
  • Auto-refresh — the view updates every couple of seconds; no reloading.
When something needs attention

Investigate failed messages

Open a connection with errors to inspect the affected messages.

Alerts

View active alert rules and the conditions they monitor.

Dead Letters

Inspect messages that exhausted their retries. Fix the cause, then replay stored messages from the list.

Trace a message

Find a message and inspect its outcome: routed, filtered, or unrouted. Review its delivery and audit records, read HL7 fields, or replay it.

Operate with confidence

Engine health and access, built in

  • Engine Status — the engine's health at a glance, with a heartbeat indicator that's green when all is well.
  • Users & sessions — manage accounts, roles, and active sessions from the console; every action is recorded in the tamper-evident audit log.

A pure API client

The console uses the local API for all engine access. Authentication, roles, and audit checks run there. The console does not access the database directly.

Monitoring is read-only; actions like start/stop and replay are permission-gated. The same API powers the CLI and the VS Code editor — see how it fits together.

Connect the console to your engine

Open the console to inspect connection status and message outcomes.

Get started See the whole toolkit →