STOMP Server UI

Server-side observer and publisher. The actual STOMP server remains the separate container listening on port 8080; this UI connects as an inspection subscription and auto-ACKs every message, so it stays compatible with the message-queue app's ack-gated delivery. If the server was started with --htpasswd, fill in Username/Password to authenticate.

Transport and negotiation

1. HTTP — browser requests WebSocket Upgrade

2. HTTP 101 — server accepts the protocol upgrade

3. WebSocket — bidirectional transport is open

4. STOMP 1.2 — CONNECT / CONNECTED / SUBSCRIBE

5. Heartbeats — LF frames keep the connection alive

Server WebSocket URLSubscription IDDestinationOSDF/Pelican origin path (optional)Username (if --htpasswd)Password

Filling in the OSDF/Pelican path overrides Destination above: it's converted to <subscription id>/<protocol>/<object path> (e.g. server-observer/osdf/vdc/public/pelican_protocol) -- the topic form the Pelican listing event source derives a federation directory to watch from. Leave it blank to subscribe to a plain destination instead.

Disconnected

Server metrics

Polled directly from the message-queue app's Prometheus /metrics endpoint (same host as the WebSocket URL above). This is independent of the STOMP connection above -- start it with "Watch metrics" below whether or not you've connected.

Connected clients: —
Active queues: —
Queued events: —
Subscriptions accepted: —
Subscriptions rejected: —
Events enqueued: —
Events dropped: —
Overflows (connected): —
Overflows (offline): —
Messages published: —
Retries attempted: —
Acks received: —
Avg ack latency: —
Queue errors: —
Metrics last updated: —

Not watching

Click "Watch metrics" to start polling.

Publish test event

This sends a STOMP SEND frame through the server. Connected clients subscribed to this destination will receive a MESSAGE.

Payload

Raw frames

No frames yet.

Activity

Ready.