Runtime SDKsSource locations and maps

Source locations and maps

Choose source paths and executable lines that each runtime can resolve, including TypeScript source-map handling.

Node source maps

Node agents scan LIVEPROBE_SOURCE_MAP_DIR, excluding hidden directories and node_modules. They upload Source Map v3 files once per service commit. The broker, not the agent, decodes mappings and returns generated script, line, and column coordinates.

  • Deploy external maps with the generated JavaScript.
  • Keep source paths stable between build and deployment.
  • Set the generated prefix with LIVEPROBE_DIST_LOCATION.
  • Use LIVEPROBE_APP_ROOT for monorepo subdirectories.

Python paths

Probe files must be full runtime-known paths or unambiguous suffixes. There is no Python map loader. Prefer repository-relative suffixes such as app/payments.py instead of machine-specific absolute paths.

JVM metadata

Java source resolution uses class-file LineNumberTable metadata. Local variables and per-frame locals additionally require LocalVariableTable. Compile production artifacts with suitable debug information.

Diagnose line-not-found

  1. Confirm the probe uses an executable one-based source line.
  2. Confirm the probe commit matches the deployed service commit.
  3. Inspect the path reported by the runtime or build output.
  4. For Node, verify map upload and source-map completion.
  5. For JVM, inspect class debug metadata and bridge connectivity.