Skip to main content
GET
/
browsers
/
{id}
/
telemetry
/
stream
JavaScript
import Kernel from '@onkernel/sdk';

const client = new Kernel({
  apiKey: process.env['KERNEL_API_KEY'], // This is the default and can be omitted
});

const response = await client.browsers.telemetry.stream('id');

console.log(response.event);
{
  "seq": 2,
  "event": {
    "ts": 123,
    "type": "<string>",
    "category": "<string>",
    "source": {
      "event": "<string>",
      "metadata": {}
    },
    "data": {
      "session_id": "<string>",
      "target_id": "<string>",
      "frame_id": "<string>",
      "loader_id": "<string>",
      "url": "<string>",
      "nav_seq": 123,
      "level": "<string>",
      "text": "<string>",
      "args": [
        "<string>"
      ],
      "stack_trace": {
        "callFrames": [
          {
            "functionName": "<string>",
            "scriptId": "<string>",
            "url": "<string>",
            "lineNumber": 123,
            "columnNumber": 123
          }
        ],
        "description": "<string>",
        "parent": "<unknown>"
      }
    },
    "truncated": true
  }
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

​
Last-Event-ID
string

Last event sequence number for SSE reconnection (sent by SSE clients on reconnect)

Path Parameters

​
id
string
required

Browser session ID

Response

SSE stream of telemetry events

Envelope wrapping a browser telemetry event with its monotonic sequence number. Each SSE data: frame carries one envelope as JSON. The seq value is also emitted as the SSE id: field so clients can pass it as Last-Event-ID on reconnect.

​
seq
integer<int64>
required

Process-monotonic sequence number assigned by the browser VM. Pass as Last-Event-ID on reconnect to resume without gaps. Gaps in received seq values indicate dropped events.

Required range: x >= 1
​
event
console_log · object
required

Union type representing any browser telemetry event. Discriminated on type. Each event's category determines when it is captured. The CDP collector-health events (monitor_disconnected, monitor_reconnected, monitor_reconnect_failed, monitor_init_failed) use the monitor category, which is not user-configurable: it flows automatically whenever any CDP category (console, network, page, interaction) is captured, and is silent otherwise. monitor_screenshot uses the opt-in screenshot category. All other event types are controlled by their per-category enable/disable flags.