​

Real-time events

​

Where the WebSocket lives

​

Connecting

import { io } from 'socket.io-client';

const socket = io('https://<your-console-host>/rt', {
  path: '/rt',
  withCredentials: true, // browser: sends the httpOnly session cookie set at sign-in
  transports: ['websocket'],
});

socket.on('event', (event) => {
  console.log(event.type, event.data);
});

​

Authentication

• Browser clients — the handshake carries your session’s httpOnly cookie automatically (withCredentials: true); there’s nothing to pass explicitly. This is what the console itself uses.
• Non-browser clients (a script, a service) — pass a bearer token explicitly instead of relying on a cookie. Check with support for the current token-issuance path if you’re building outside the browser.

​

Event envelope

{
  "type": "ml.training.completed",
  "data": {
    "model_type": "gpu_anomaly",
    "duration_ms": 7512,
    "model_id": 42
  },
  "timestamp": "2026-04-29T16:41:38.412Z",
  "trace_id": "7a0db7e045..."
}

​

Event catalog

​

Using events in a React app

const PREFIX_TAG_MAP: Record<string, string[]> = {
  'instance.':       ['instance'],
  'metrics.':        ['metric'],
  'cost.':           ['cost'],
  'alert.':          ['alert'],
  'recommendation.': ['recommendation'],
  'runaway_loop.':   ['agent', 'recommendation'],
  'ml.':             ['ml-model'],
};

socket.on('event', (e) => {
  const tags = tagsForEvent(e.type);
  if (tags) queryClient.invalidateQueries({ queryKey: tags });
});

​

Reliability guarantees

• In-process priority. Events dispatch to local subscribers synchronously in the publish path with no Redis dependency. A single-instance deployment works end-to-end with no broker.
• Redis for durability (when configured). Events are also LPUSH’d onto per-type queues for cross-instance replay. A bounded LRU of recently-dispatched event IDs prevents double delivery.
• Best-effort on Redis failure. If Redis is unreachable, events still reach all in-process subscribers (and thus the Socket.IO bridge). Only cross-instance replay is lost.
• Per-type ordering. Events within a single type are ordered. Across types, no ordering guarantees.
• Per-tenant rate limits. Socket.IO emit rate is capped per tenant to protect noisy-neighbor scenarios. Default 100 events/sec/tenant; raise on enterprise tier.

​

Webhooks

​

Debugging connection issues

• Wrong path. The upgrade must go to /rt on your console host, not a separate subdomain and not the Socket.IO default path (/socket.io/).
• Expired session. If your cookie or token has expired, reconnect after re-authenticating. The console handles this automatically on route navigation.
• A proxy stripping Connection: Upgrade / Upgrade: websocket headers. If you’re connecting through a corporate proxy, confirm it forwards WebSocket upgrade headers on /rt.

​

MCP

​

Tool surface

​

Scope-guarded by RBAC

​

Authenticating

​

Use cases

• CFO / finance — point Claude Desktop at TensorCost MCP and ask “what drove last week’s Bedrock bill?” The model uses get_cost_summary + list_recommendations to compose the answer.
• Platform engineer — wire your internal agent to MCP to check fleet health or workload cost during an incident.
• Partner integration — build a Datadog / Grafana panel that consumes get_cost_summary and get_fleet_health for embedded TensorCost views.