CLI Reference

此内容尚不支持你的语言。

The IDE plugin handles everything automatically. Most users never touch the CLI. This page is for troubleshooting and advanced use cases.

When to Use the CLI

The CLI is useful when:

Scenario	Why CLI?
IDE can’t find your JVM	Run `galataj doctor` to diagnose
Running without an IDE	Headless servers, CI pipelines
Docker / Remote JVMs	Manual attach to containerized apps
Debugging issues	Check status, view logs
Automation	Scripted profiling workflows

These are the commands you’ll actually use:

Diagnose system issues. Run this first when something doesn’t work.

galataj doctor

✓ Java: Found (11.0.19)
✓ Controller JAR: Found
✓ Agent JAR: Found
✓ Controller: Running
✓ Ports: Available (9876, 9877)

Check what’s running. Shows controller status and attached JVMs.

galataj status

Controller: Running (PID: 12345)
HTTP Port: 9877
TCP Port: 9876

Attached JVMs: 1
- abc123 (PID: 67890) - MyApp

List available JVMs. Shows all Java processes that can be profiled.

galataj jvms

Found 2 JVM(s):

1. com.example.MyApp
   ID: abc123
   PID: 12345

2. order-service
   ID: def456
   Environment: docker

Attach profiler to a JVM. Use when the IDE can’t attach automatically.

# By PID
galataj attach --pid 12345

# By JVM ID (from 'galataj jvms')
galataj attach --jvm-id abc123

Stop profiling a JVM.

galataj detach --jvm-id abc123

Check CLI version.

galataj version

galataj license status

galataj license login YOUR-LICENSE-KEY

galataj license purchase

Advanced Commands (rarely needed)

Most users never need these - the IDE handles controller lifecycle automatically.

Start controller manually:

galataj controller start
galataj controller start --port 8888  # Custom port

Stop controller:

galataj controller stop

Variable	Description	Default
`GALATAJ_CONTROLLER_PORT`	HTTP API port	9877
`GALATAJ_CLI_PATH`	CLI path for IDE	auto-detect

Most commands support --json for scripting:

galataj jvms --json
galataj status --json
galataj license status --json