BeamConsole

BeamConsole is an embeddable, read-only process flight recorder and process map for Phoenix and BEAM applications. It makes supervision, process relationships, lifecycle changes, per-process activity, and node-wide runtime health visible without application-specific instrumentation.

Installation

Add BeamConsole to a Phoenix application:

def deps do
  [
    {:beam_console, "~> 0.4.0"}
  ]
end

Import and mount it from the host router. The route is disabled outside development by default.

defmodule MyAppWeb.Router do
  use MyAppWeb, :router

  import BeamConsole.Router

  scope "/" do
    pipe_through :browser
    beam_console "/beam"
  end
end

Visit /beam after restarting the host application. A different Phoenix server port can be supplied through the host application's usual endpoint environment configuration; BeamConsole does not own the HTTP listener.

Plain Elixir applications

The dependency also starts its bounded collector and recorder in applications without Phoenix. Those applications can consume normalized snapshots and recorder queries directly; the embedded web interface is available only when Phoenix and LiveView are installed by the host.

{:ok, latest_snapshot} = BeamConsole.subscribe()
:ok = BeamConsole.refresh()

receive do
  {:beam_console_snapshot, sequence} ->
    snapshot = BeamConsole.latest_snapshot()
    :ok = BeamConsole.acknowledge(sequence)
end

status = BeamConsole.Recorder.status()
events = BeamConsole.Recorder.events(limit: 100)

paused = BeamConsole.Recording.pause()
resumed = BeamConsole.Recording.resume()

Call BeamConsole.unsubscribe/0 when a long-lived manual subscriber no longer needs updates. Subscribers are also removed automatically when their process terminates.

What it shows

• Process Map: a stable, focused supervision graph with optional process links and monitors, plus a searchable process explorer.
• Lifecycle: observed process starts, terminations, and replacement correlations with explicit evidence and coverage language.
• Activity: reductions per second, mailbox growth, memory movement, and ranked process movers.
• Runtime: BEAM memory categories, run queue, atom count and utilization, runtime inventory, collector duration, applications, ETS tables, and connected-node inventory.
• Inspector: allowlisted process, application, and node details. Process relationships are clickable when their target is present in the latest sample.

Applications are grouped into host, dependencies, OTP, and tooling categories. Every tree branch can be collapsed and its state remains stable while LiveView updates.

Recording model

The default :subscribers mode records while at least one BeamConsole page is connected. The header control pauses and resumes lifecycle recording explicitly. A connected dashboard continues receiving live runtime samples while recording is paused. Retained samples remain bounded by age, item count, chart point count, and estimated bytes.

To begin recording when the application starts, even before anyone opens the page:

config :beam_console, :recorder,
  mode: :always

In :always mode, sampling and lifecycle recording remain active with zero connected pages. The collector and recorder both derive their demand from this mode, so ordinary subscriber disconnects and supervised collector or recorder restarts do not silently return recording to subscriber-only behavior. An explicit operator pause takes precedence: lifecycle watches stop immediately, and background sampling stops when no viewer remains. The shared pause state survives independent collector and recorder restarts until recording is resumed; a full application restart restores the configured default.

One runtime scan already in flight when recording is paused may still complete and update the latest snapshot. It cannot restart a zero-viewer background scan loop. Manual refresh remains a bounded one-shot, while recorder-driven reconciliation is suppressed until recording resumes.

Lifecycle recording is observational rather than a lossless trace. Sampling gaps, partial supervision traversal, process limits, watch limits, and dropped history are surfaced in the interface instead of being hidden.

Access control

BeamConsole deliberately does not ship a production authentication system. The host application owns exposure, authentication, and authorization. Do not expose runtime metadata publicly.

Use the host browser pipeline for plug-based authorization. For LiveView authorization, pass existing on_mount hooks to the embedded live session:

beam_console "/beam",
  enabled: true,
  on_mount: [{MyAppWeb.UserAuth, :ensure_admin}]

When an authorization hook needs host session values, merge a static string-keyed map or a session callback. The callback receives the connection as its first argument.

beam_console "/beam",
  enabled: true,
  session: {MyAppWeb.BeamConsoleSession, :build, []},
  on_mount: [{MyAppWeb.UserAuth, :ensure_admin}]

defmodule MyAppWeb.BeamConsoleSession do
  def build(conn) do
    %{"current_user_id" => Plug.Conn.get_session(conn, :current_user_id)}
  end
end

Host authorization hooks run before BeamConsole's internal mount hook. Reserved transport and mount keys cannot be overridden by the host session callback.

LiveView sessions are signed but not encrypted. Return only the minimal identifiers and authorization context required by the hook; never return secrets, credentials, or the complete host session.

Router options

Endpoint URL paths and Phoenix forwarding prefixes from conn.script_name are applied automatically to navigation and asset paths. Set :socket_path to the endpoint socket's externally reachable path when a proxy also prefixes WebSocket or long-poll requests.

For example, a host that exposes a long-poll-only socket at /internal/live mounts BeamConsole with matching connection settings:

beam_console "/beam",
  socket_path: "/internal/live",
  transport: "longpoll"

Configuration

Collector settings are bounded and reject unknown keys:

config :beam_console, :collector,
  interval: 2_000,
  scan_timeout: 1_500,
  process_limit: 20_000,
  supervisor_limit: 2_000,
  relationship_limit: 200

Recorder retention can also be tuned explicitly:

config :beam_console, :recorder,
  retention_ms: 15 * 60_000,
  frame_limit: 450,
  event_limit: 1_000,
  chart_points_limit: 240,
  byte_limit: 8 * 1_024 * 1_024

Safety boundary

BeamConsole does not fetch process messages, dictionaries, stacktraces, binaries, or arbitrary process state. It does not use :sys, tracing, remote RPC, or process mutation. Browser inputs are matched against fixed allowlists and opaque entity IDs are revalidated against the latest snapshot.

Compared with Observer and Phoenix LiveDashboard

Observer is a broad Erlang runtime desktop tool. Phoenix LiveDashboard is a Phoenix-focused operational dashboard built around metrics and framework integrations. BeamConsole is narrower: it is an embeddable, process-first tool focused on supervision topology, observed crash-and-replacement history, process relationships, and bounded activity over time.

Demo

The database-free sample application lives in examples/demo and uses BeamConsole through a path dependency.

cd examples/demo
mix deps.get
mix phx.server

Visit /lab for deterministic sample controls or /beam for BeamConsole.

License

BeamConsole is available under the Apache License 2.0. See LICENSE and THIRD_PARTY_NOTICES.