APM & OpenTelemetry

Python APM with zero dependencies.

One pip install and an init call. The wrapper aggregates transactions, spans, and errors in memory and posts one payload per flush. No sidecar, no agent process, Python 3.9+.

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.

Endpoint percentilesp50/p95/p99 latency and throughput per endpoint, with slowest endpoints ranked.
Grouped errorsThe same exception across requests becomes one issue with a count, not a thousand log lines.
Traces & spansWaterfalls with dependency timing: see the query, the cache call, and the external API inside each request.
Deploy correlationChange events line up against latency and error charts, so a bad deploy is caught automatically.

Warn and fail thresholds, prefilled

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

Endpoint latency and error-rate anomalies open issues automatically

Setup

python apm setup

$ pip install roottrace-apm
# in your app:
$ import roottrace_apm as apm
$ apm.init(service="checkout-api", token="rtc_...")

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

Zero-dependency and Apache-2.0 licensed: roottrace-apm on PyPI · source on GitHub.

Questions, answered honestly

Which frameworks work?

Any Python service. The wrapper is framework-agnostic, and FastAPI services already instrumented with OpenTelemetry can send OTLP/JSON to RootTrace instead.

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.

Create free workspace Schedule a demo