Skip to main content
HyperProbe lets you inspect live production applications the way a debugger inspects local code — without pausing execution, redeploying, or adding log statements. You place probes on specific lines of code from VS Code, and the SDK agent running inside your application instruments those lines in real time. Captured data flows back to your editor automatically.

Quickstart

Install the extension and SDK, then capture your first snapshot in minutes.

How it works

Learn how probes travel from VS Code through the agent and back to your editor.

VS Code extension

Install and configure the HyperProbe extension to set probes from your editor.

Node.js SDK

Add the @hyperprobe/node-sdk agent to your Node.js application.

Probe types

HyperProbe gives you two types of probes for now, each designed for a specific kind of production observability:
Probe typeWhat it captures
SnapshotLocal variables, watch expressions, and the full call stack at a specific line
LogA dynamic log line with interpolated variable values, injected without a redeploy

Safety guarantees

HyperProbe is designed to be safe in production environments:
  • Non-blocking instrumentation. The agent never uses debugger statements or pauses the event loop. All capture happens asynchronously using the V8 inspector (Node.js) or byte manipulation (Java).
  • Configurable data limits. Captured snapshots are bounded by depth, array length, string length, and object property count. You can tune these limits or accept the defaults.
  • Automatic cooldown. If the agent detects that instrumentation overhead exceeds your configured threshold, it suspends all probes and automatically resumes after a cooldown period.
  • Hit limits. Every probe has a maximum hit count. Once reached, the agent stops collecting for that probe, preventing runaway capture.
HyperProbe’s safety monitor tracks event loop lag and instrumentation pause time continuously. If either metric exceeds your configured limits, the agent enters a protected state and backs off automatically.

Who HyperProbe is for

HyperProbe is useful when you need to understand what is happening inside a production system and adding log statements, triggering a redeploy, or attaching a traditional debugger is not an option. It fits teams running Node.js or JVM applications who want production observability that does not require changing their deployment pipeline.