BTrace Getting Started Guide

What is BTrace?

BTrace is a safe, dynamic tracing tool for the Java platform. It allows you to dynamically instrument running Java applications without stopping them, recompiling code, or adding logging statements. BTrace works by injecting tracing code into the bytecode of target applications at runtime.

Use BTrace when you need to:

Debug production issues without redeploying
Profile application performance in real-time
Track method calls, arguments, and return values
Monitor memory allocations and object creation
Investigate thread behavior and synchronization
Capture stack traces at specific points

Prerequisites

Java 8 or higher (BTrace supports Java 8-20)
Basic knowledge of Java programming
Target Java application running with appropriate permissions

Installation

Download and Install

Download the latest release from GitHub releases

Extract the distribution:

bash

# For .tar.gz
tar -xzf btrace-<version>.tar.gz

# For .zip
unzip btrace-<version>.zip

Set environment variables (optional but recommended):

bash

export BTRACE_HOME=/path/to/btrace
export PATH=$BTRACE_HOME/bin:$PATH

Package Manager Installation

RPM-based systems (RedHat, CentOS, Fedora):

bash

sudo rpm -i btrace-<version>.rpm

Debian-based systems (Ubuntu, Debian):

bash

sudo dpkg -i btrace-<version>.deb

JBang Installation (Recommended for Quick Start)

JBang makes it incredibly easy to use BTrace without manual installation. It automatically downloads and caches BTrace from Maven Central.

Install JBang (one time):

bash

# macOS / Linux
curl -Ls https://sh.jbang.dev | bash -s - app setup

# Windows (PowerShell)
iex "& { $(iwr https://ps.jbang.dev) } app setup"

# Or use package managers
brew install jbangdev/tap/jbang    # macOS
sdk install jbang                   # SDKMAN

Use BTrace with JBang (no separate BTrace installation needed):

bash

# Attach to running application (replace <version> with desired version, e.g., 2.3.0)
jbang io.btrace:btrace-client:<version> <PID> <script.java>

# Add the BTrace JBang catalog (one time), then use the shorter alias
jbang catalog add --name btraceio https://raw.githubusercontent.com/btraceio/jbang-catalog/main/jbang-catalog.json
jbang btrace@btraceio <PID> <script.java>

Extract agent JARs (if needed for --agent-jar/--boot-jar flags):

bash

# Extract to a directory of your choice
jbang io.btrace:btrace-client:<version> --extract-agent ~/.btrace

# This creates:
#   ~/.btrace/btrace-agent.jar
#   ~/.btrace/btrace-boot.jar

# Then use them explicitly:
jbang btrace@btraceio --agent-jar ~/.btrace/btrace-agent.jar \
             --boot-jar ~/.btrace/btrace-boot.jar \
             <PID> <script.java>

Alternative: Use JARs from Maven local repository: After jbang downloads BTrace, find the JARs in your local Maven repository (default ~/.m2):

bash

# JARs are cached at:
~/.m2/repository/io/btrace/btrace-agent/<version>/btrace-agent-<version>.jar
~/.m2/repository/io/btrace/btrace-boot/<version>/btrace-boot-<version>.jar

# Use them directly:
jbang btrace@btraceio --agent-jar ~/.m2/repository/io/btrace/btrace-agent/<version>/btrace-agent-<version>.jar \
             --boot-jar ~/.m2/repository/io/btrace/btrace-boot/<version>/btrace-boot-<version>.jar \
             <PID> <script.java>

Benefits:

No manual download or installation
Automatic version management via Maven coordinates
Works across all platforms (Windows, macOS, Linux)
Perfect for CI/CD pipelines and containers

Verify Installation

bash

btrace -h
# or with JBang
jbang btrace@btraceio -h

You should see the BTrace help message with available options.

2-Minute Oneliner Quick Start

New in BTrace: DTrace-style oneliners let you debug without writing script files!

Quick Examples

bash

# Find your Java application's PID
jps

# Trace method entry with arguments
btrace -n 'TestApp::processData @entry { print method, args }' <PID>

# Find slow methods (>50ms)
btrace -n 'TestApp::* @return if duration>50ms { print method, duration }' <PID>

# Count method invocations
btrace -n 'TestApp::doWork @entry { count }' <PID>

# Print stack traces
btrace -n 'TestApp::processData @entry { stack(5) }' <PID>

Oneliner Syntax:

class-pattern::method-pattern @location [filter] { action }

Locations: @entry, @return, @error
Actions: print, count, time, stack
Filters: if duration>NUMBERms, if args[N]==VALUE

For complete oneliner documentation, see Oneliner Guide.

Want full BTrace power? Continue to the full 5-minute quick start below.

5-Minute Quick Start

Let's trace a simple Java application to see BTrace in action with full Java scripts.

Step 1: Prepare a Test Application

Create a simple Java program (TestApp.java):

java

public class TestApp {
    public static void main(String[] args) throws Exception {
        System.out.println("TestApp started. Press Enter to begin...");
        System.in.read();

        while (true) {
            doWork();
            Thread.sleep(1000);
        }
    }

    private static void doWork() {
        String result = processData("example", 42);
        System.out.println("Processed: " + result);
    }

    private static String processData(String name, int value) {
        return name + "-" + value;
    }
}

Compile and run it:

bash

javac TestApp.java
java TestApp

Step 2: Create Your First BTrace Script

Create a BTrace script (TraceMethods.java) to trace method calls:

java

import org.openjdk.btrace.core.annotations.BTrace;
import org.openjdk.btrace.core.annotations.OnMethod;
import static org.openjdk.btrace.core.BTraceUtils.println;
import static org.openjdk.btrace.core.BTraceUtils.str;

@BTrace
public class TraceMethods {
    @OnMethod(clazz = "TestApp", method = "processData")
    public static void onProcessData(String name, int value) {
        println("Called processData: name=" + name + ", value=" + str(value));
    }
}

Step 3: Attach BTrace to the Running Application

Find the process ID of your TestApp:
bash
```
jps
```
Output will show something like:
```
12345 TestApp
12346 Jps
```
Attach BTrace:
bash
```
btrace 12345 TraceMethods.java
```
Press Enter in the TestApp window to start processing

Observe the output in the BTrace terminal:

Called processData: name=example, value=42
Called processData: name=example, value=42
...

Detach BTrace: Press Ctrl+C in the BTrace terminal and type exit

Congratulations! You've successfully traced your first Java application with BTrace.

Quick Start: Histogram Metrics Extension

Capture latency distributions and simple stats without external systems using the built-in histogram metrics extension (HdrHistogram-based).

Ensure you built the distribution so extensions are available under BTRACE_HOME/extensions/.
Create a probe that injects MetricsService (no special flags needed):

java

import static org.openjdk.btrace.core.BTraceUtils.*;

import org.openjdk.btrace.core.annotations.*;
import org.openjdk.btrace.metrics.MetricsService;
import org.openjdk.btrace.metrics.histogram.*;
import org.openjdk.btrace.metrics.stats.*;

@BTrace
public class LatencyProbe {
   @Injected
   private static MetricsService metrics;
   private static HistogramMetric h;
   private static StatsMetric s;

   @OnMethod(clazz = "TestApp", method = "processData")
   public static void onEntry() {
      if (h == null) {
         h = metrics.histogramMicros("testapp.process");
         s = metrics.stats("testapp.process.stats");
      }
   }

   @OnMethod(clazz = "TestApp", method = "processData", location = @Location(Kind.RETURN))
   public static void onReturn(@Duration long durNs) {
      long us = durNs / 1000;
      h.record(us);
      s.record(us);
   }

   @OnTimer(1000)
   public static void report() {
      HistogramSnapshot hs = h.snapshot();
      StatsSnapshot ss = s.snapshot();
      println("=== Metrics Report ===");
      println("Count: " + ss.count());
      println("Mean: " + ss.mean() + " μs");
      println("Min: " + ss.min() + " μs");
      println("Max: " + ss.max() + " μs");
      println("P50: " + hs.p50() + " μs");
      println("P95: " + hs.p95() + " μs");
      println("P99: " + hs.p99() + " μs");
      println("======================");
   }
}

Attach to your running app:

bash

btrace <PID> LatencyProbe.java

See the full tutorial section: “Using the Histogram Metrics Extension (btrace-metrics)” in docs/BTraceTutorial.md for configuration and details.

Four Ways to Run BTrace

BTrace offers multiple deployment modes to suit different use cases:

1. JBang Mode (Easiest - Recommended)

Use JBang to run BTrace without installation:

bash

jbang io.btrace:btrace-client:<version> <PID> <script.java>

# One-time catalog setup for the short alias
jbang catalog add --name btraceio https://raw.githubusercontent.com/btraceio/jbang-catalog/main/jbang-catalog.json

When to use:

Quick start without installation
CI/CD pipelines
Trying BTrace for the first time
Containers and cloud environments

Examples:

bash

# Basic usage
jbang btrace@btraceio 12345 MyTrace.java

# With verbose output
jbang btrace@btraceio -v 12345 MyTrace.java arg1 arg2

# Extract agent JARs, then use them explicitly
jbang btrace@btraceio --extract-agent ~/.btrace
jbang btrace@btraceio --agent-jar ~/.btrace/btrace-agent.jar \
             --boot-jar ~/.btrace/btrace-boot.jar \
             12345 MyTrace.java

# Or use JARs from Maven local repository (after jbang downloads them)
jbang btrace@btraceio --agent-jar ~/.m2/repository/io/btrace/btrace-agent/<version>/btrace-agent-<version>.jar \
             --boot-jar ~/.m2/repository/io/btrace/btrace-boot/<version>/btrace-boot-<version>.jar \
             12345 MyTrace.java

Benefits:

Zero installation required
Works everywhere (Windows, macOS, Linux, containers)
Automatic version management
Perfect for reproducible builds

2. Attach Mode (Most Common)

Attach to an already running Java process:

bash

btrace [options] <PID> <script.java> [script-args]

When to use:

Debugging production issues
Ad-hoc performance analysis
You don't want to restart the application

Example:

bash

btrace -v 12345 MyTrace.java arg1 arg2

Common options:

-v - Verbose output
-p <port> - Specify port for communication
-o <file> - Redirect output to file
--agent-jar <path> - Override agent JAR auto-discovery
--boot-jar <path> - Override boot JAR auto-discovery

3. Java Agent Mode (Pre-compiled Scripts)

Start a Java application with BTrace agent and a pre-compiled script:

bash

java -javaagent:btrace-agent.jar=script=<script.class>[,arg1=value1]... YourApp

When to use:

Tracing from application startup
Capturing initialization issues
Controlled environments

Example:

bash

# First compile the script
btracec MyTrace.java

# Then run with agent
java -javaagent:/path/to/btrace-agent.jar=script=MyTrace.class MyApp

4. Launcher Mode (btracer)

Use the btracer wrapper to compile and attach in one step:

bash

btracer <script.class> <java-app-with-args>

When to use:

Local development and testing
Quick experiments
You have control over application launch

Example:

bash

# First compile the script
btracec MyTrace.java

# Launch app with trace
btracer MyTrace.class java -cp myapp.jar com.example.Main

Your First BTrace Scripts

Example 1: Trace Method Entry

java

import org.openjdk.btrace.core.annotations.*;
import static org.openjdk.btrace.core.BTraceUtils.*;

@BTrace
public class MethodEntry {
    @OnMethod(clazz = "com.example.MyClass", method = "myMethod")
    public static void onEntry() {
        println("Method called!");
    }
}

Example 2: Trace Method Arguments

java

import org.openjdk.btrace.core.annotations.*;
import static org.openjdk.btrace.core.BTraceUtils.*;

@BTrace
public class MethodArgs {
    @OnMethod(clazz = "com.example.MyClass", method = "calculate")
    public static void onCalculate(int x, int y) {
        println("calculate called with: x=" + str(x) + ", y=" + str(y));
    }
}

Example 3: Trace Method Return Value

java

import org.openjdk.btrace.core.annotations.*;
import static org.openjdk.btrace.core.BTraceUtils.*;

@BTrace
public class MethodReturn {
    @OnMethod(clazz = "com.example.MyClass", method = "calculate", location = @Location(Kind.RETURN))
    public static void onReturn(@Return int result) {
        println("calculate returned: " + str(result));
    }
}

Example 4: Measure Method Duration

java

import org.openjdk.btrace.core.annotations.*;
import static org.openjdk.btrace.core.BTraceUtils.*;

@BTrace
public class MethodDuration {
    @OnMethod(clazz = "com.example.MyClass", method = "slowMethod")
    public static void onEntry(@Duration long durationNanos) {
        if (durationNanos > 0) {
            println("slowMethod took: " + str(durationNanos / 1000000) + " ms");
        }
    }
}

Advanced: JFR Integration

BTrace integrates with Java Flight Recorder (JFR) to create high-performance events with <1% overhead. JFR events are recorded natively by the JVM and can be analyzed with JDK Mission Control.

Requirements: OpenJDK 8 (with backported JFR) or Java 11+ (not available in Java 9-10)

Example: Create JFR Event

java

import org.openjdk.btrace.core.annotations.*;
import org.openjdk.btrace.core.jfr.JfrEvent;
import static org.openjdk.btrace.core.BTraceUtils.*;

@BTrace
public class MyJfrTrace {
    // Define JFR event factory
    @Event(
        name = "MethodCall",
        label = "Method Call Event",
        description = "Tracks method calls with duration",
        category = {"myapp", "performance"},
        fields = {
            @Event.Field(type = Event.FieldType.STRING, name = "method"),
            @Event.Field(type = Event.FieldType.LONG, name = "duration")
        }
    )
    private static JfrEvent.Factory callEventFactory;

    @TLS private static long startTime;

    @OnMethod(clazz = "com.example.MyClass", method = "process")
    public static void onEntry() {
        startTime = timeNanos();
    }

    @OnMethod(clazz = "com.example.MyClass", method = "process",
             location = @Location(Kind.RETURN))
    public static void onReturn(@ProbeMethodName String method) {
        // Create and commit JFR event
        JfrEvent event = Jfr.prepareEvent(callEventFactory);
        if (Jfr.shouldCommit(event)) {
            Jfr.setEventField(event, "method", method);
            Jfr.setEventField(event, "duration", timeNanos() - startTime);
            Jfr.commit(event);
        }
    }
}

Viewing JFR Events

After running the script, JFR events are recorded in the flight recorder:

bash

# Run BTrace script
btrace <PID> MyJfrTrace.java

# Start flight recording (if not already running)
jcmd <PID> JFR.start name=my-recording

# Dump recording to file
jcmd <PID> JFR.dump name=my-recording filename=recording.jfr

# Analyze with Mission Control
jmc recording.jfr

Benefits over println:

<1% overhead vs. 1-50% for println
Native JVM recording (no string formatting)
Can be analyzed offline
Timeline visualization in Mission Control

For complete JFR documentation, see BTrace Tutorial Lesson 5 and FAQ: JFR Integration.

BTrace in Containers and Kubernetes

BTrace works in containerized environments with some considerations.

Docker Containers

Attach to running container:

bash

# Find container ID/name
docker ps

# Execute BTrace in container
docker exec -it <container-id> btrace <PID> script.java

Prerequisites:

JDK (not JRE) must be installed in container
BTrace must be available in container or mounted
Same user permissions as target JVM

Example Dockerfile with official BTrace images:

dockerfile

# Option 1: Copy BTrace into your application image (recommended)
FROM btrace/btrace:latest AS btrace
FROM bellsoft/liberica-openjdk-debian:11-cds

COPY --from=btrace /opt/btrace /opt/btrace
ENV BTRACE_HOME=/opt/btrace
ENV PATH=$PATH:$BTRACE_HOME/bin

# Your application...
COPY target/myapp.jar /app/
ENTRYPOINT ["java", "-jar", "/app/myapp.jar"]

Alternative: Manual installation (if not using official images):

dockerfile

FROM bellsoft/liberica-openjdk-debian:11-cds
RUN curl -L https://github.com/btraceio/btrace/releases/download/v2.2.2/btrace-2.2.2.tar.gz \
    | tar -xz -C /opt/
ENV BTRACE_HOME=/opt/btrace-2.2.2
ENV PATH=$PATH:$BTRACE_HOME/bin

See docker/Readme.md for more Docker usage patterns.

Kubernetes Pods

Attach to pod:

bash

# Find pod and process ID
kubectl get pods
kubectl exec <pod-name> -- jps

# Run BTrace
kubectl exec -it <pod-name> -- btrace <PID> script.java

Copy script to pod first (if needed):

bash

kubectl cp MyTrace.java <pod-name>:/tmp/
kubectl exec -it <pod-name> -- btrace <PID> /tmp/MyTrace.java

Trace multiple pods:

bash

# Get all pods for a deployment
PODS=$(kubectl get pods -l app=myapp -o jsonpath='{.items[*].metadata.name}')

# Attach to each pod
for POD in $PODS; do
  echo "Tracing $POD..."
  kubectl exec $POD -- btrace 1 script.java &
done

Sidecar Pattern

Add BTrace as a sidecar container for persistent availability:

yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: myapp
spec:
  template:
    spec:
      shareProcessNamespace: true  # Important: enables cross-container process visibility
      containers:
      - name: app
        image: myapp:latest

      - name: btrace
        image: btrace/btrace:latest-alpine  # Official BTrace Alpine image
        command: ["/bin/sh", "-c", "while true; do sleep 30; done"]
        volumeMounts:
        - name: btrace-scripts
          mountPath: /scripts
      volumes:
      - name: btrace-scripts
        configMap:
          name: btrace-scripts

Note: Requires shareProcessNamespace: true to allow sidecar to see app container processes.

Using the sidecar:

bash

# Execute BTrace from sidecar
kubectl exec <pod-name> -c btrace -- btrace $(pgrep -f myapp) /scripts/trace.btrace

# View output
kubectl logs <pod-name> -c btrace

Common Issues in K8s

PID Discovery: Use jps or ps aux to find Java process ID
Port Conflicts: BTrace uses port 2020 by default; use -p flag if needed
Security Policies: Pod Security Policies may block ptrace; adjust as needed
Resource Limits: BTrace overhead may trigger CPU/memory limits

For comprehensive troubleshooting, see Troubleshooting: Kubernetes.

Common Pitfalls and Solutions

1. Permission Denied / Attachment Fails

Problem: Unable to attach to target VM

Solutions:

Ensure BTrace and target app run as the same user
JDK 8-20: Check if target JVM has -XX:+DisableAttachMechanism (remove it)
JDK 21+: Add -XX:+EnableDynamicAgentLoading to target JVM to suppress warnings and ensure compatibility
Verify JDK (not JRE) is installed

Note: Starting with JDK 21, dynamic agent loading triggers warnings. In a future JDK release, it will be disabled by default, requiring -XX:+EnableDynamicAgentLoading to use BTrace's attach mode. See Troubleshooting: JVM Attachment Issues for details.

2. Script Verification Errors

Problem: BTrace script verification failed

Common causes:

Using forbidden operations (creating new threads, I/O operations)
Calling non-BTrace methods
Using synchronization primitives

Solution: Use only BTrace-safe operations from BTraceUtils class.

3. No Output from Script

Problem: Script attaches but produces no output

Checklist:

Verify class and method names are correct (case-sensitive)
Check if the method is actually being called in the target app
Use regular expressions carefully: /com\\.example\\..*/ not /com.example.*/
Ensure println() is imported from BTraceUtils

4. Script Not Finding Classes

Problem: Script doesn't match any classes

Solutions:

Use fully qualified class names: "com.example.MyClass" not "MyClass"
For inner classes use $: "com.example.Outer$Inner"
Test with wildcards: "/com\\.example\\..*/"

5. Performance Impact

Problem: BTrace slows down the application

Solutions:

Use sampling: @Sampled annotation
Add level filtering: @Level annotation
Limit scope: trace specific methods, not all methods
Avoid tracing high-frequency methods

6. Unicode or Special Characters in Output

Problem: Garbled output with special characters

Solution: Set encoding:

bash

btrace -Dfile.encoding=UTF-8 <PID> script.java

Next Steps

Now that you have BTrace running, explore these resources:

BTrace Tutorial - Progressive lessons covering all features
Quick Reference - Annotation and API cheat sheet
Sample Scripts - 50+ real-world examples
Troubleshooting Guide - Solutions to common problems
BTrace Wiki - Comprehensive user guide

Tips for Success

Start simple: Begin with basic method tracing before complex instrumentation
Test locally: Verify scripts on test applications before production use
Use samples: Browse the 50+ sample scripts for patterns
Monitor overhead: Always measure BTrace's performance impact
Keep scripts focused: One script per specific issue
Version control: Save useful scripts for reuse

Getting Help

Slack: btrace.slack.com
Gitter: gitter.im/btraceio/btrace
GitHub Issues: github.com/btraceio/btrace/issues
Wiki: github.com/btraceio/btrace/wiki

BTrace Getting Started Guide

BTrace Getting Started Guide

What is BTrace?

Prerequisites

Installation

Download and Install

Package Manager Installation

JBang Installation (Recommended for Quick Start)

Verify Installation

2-Minute Oneliner Quick Start

Quick Examples

5-Minute Quick Start

Step 1: Prepare a Test Application

Step 2: Create Your First BTrace Script

Step 3: Attach BTrace to the Running Application

Quick Start: Histogram Metrics Extension

Four Ways to Run BTrace

1. JBang Mode (Easiest - Recommended)

2. Attach Mode (Most Common)

3. Java Agent Mode (Pre-compiled Scripts)

4. Launcher Mode (btracer)

Your First BTrace Scripts

Example 1: Trace Method Entry

Example 2: Trace Method Arguments

Example 3: Trace Method Return Value

Example 4: Measure Method Duration

Advanced: JFR Integration

Example: Create JFR Event

Viewing JFR Events

BTrace in Containers and Kubernetes

Docker Containers

Kubernetes Pods

Sidecar Pattern

Common Issues in K8s

Common Pitfalls and Solutions

1. Permission Denied / Attachment Fails

2. Script Verification Errors

3. No Output from Script

4. Script Not Finding Classes

5. Performance Impact

6. Unicode or Special Characters in Output

Next Steps

Tips for Success

See Also

Getting Help