RootTrace

RootTrace / Integrations / Java APM

APM & OpenTelemetry

Java APM, or bring your OpenTelemetry.

Build the reference wrapper from this repository, or point an auto-instrumented Spring Boot service's OTLP exporter at RootTrace. No Maven artifact is currently published.

What RootTrace watches

Every reading is checked continuously; bad readings become grouped issues with the evidence attached. RootTrace also remembers whether it has seen the same incident before.

Warn and fail thresholds, prefilled

Sensible defaults out of the box, overridable per host with environment variables. No threshold spreadsheet required on day one.

Setup

java apm setup
# No Maven artifact is published. Build apm/java from this repository,
# or, with OpenTelemetry auto-instrumentation:
$ OTEL_EXPORTER_OTLP_PROTOCOL=http/json

Outbound HTTPS only: the wrapper aggregates in memory and posts to the API; nothing listens on your hosts and nothing touches production.

The Java wrapper is a source-only reference implementation; use OTLP/JSON for the supported package-manager path.

Questions, answered honestly

Do I have to change my code for OTLP?

No. An auto-instrumented JVM only needs exporter environment variables pointed at the RootTrace endpoint with a collector key.

Is this safe to run next to production?

The collector is read-only by architecture, not by policy: there is no write path, no remediation executor, and no privileged mode to switch on. It sends short-lived outbound HTTPS requests, opens no inbound ports, and redacts credential-like evidence before anything leaves the host.

Do I need a separate agent for this?

No. One RootTrace collector per host covers every integration on this site: databases, web servers, containers, endpoints, and the Linux host itself, all from one signed package or container. You point it at targets with environment variables; there is nothing else to deploy.

Free on 5 hosts. Live in minutes.

Create a workspace, install one collector, and watch issues explain themselves.