Apm
APM — Distributed Tracing
- *rea:*Observability
- *ath:*
observe/apm(engine) +platform/apm(SaaS) - *ind:*Distributed tracing / Application Performance Monitoring
Role in the stack
APM is the distributed tracing and performance monitoring layer of Koder. Services emit spans via OTLP, Zipkin, Jaeger or simple JSON; APM stitches them into traces, visualizes them as waterfalls, builds service dependency maps, and computes P50P95P99 latency per service. It is the go-to tool when latency spikes or an error flood appears.
The opencore engine lives in tenant SaaS version.observe/apm; platform/apm is the multi
Features
- *ulti-format ingestion*— OTLP (OpenTelemetry), Zipkin v2, Jaeger, and simple JSON
- *aterfall visualization*— Gantt-chart view of all spans in a trace with timing
- *ervice dependency map*— Visual graph of service
toservice calls with error rates - *atency analytics*— P50P95P99 percentiles, throughput, error rates per service
- *ulti
tenant*— Orgbased isolation with API key authentication - *QLite storage*— Zero-dependency persistence with retention cleanup
Primary couplings
| Consumer | Relationship |
|---|---|
engines/sdk/go, engines/sdk/js, engines/sdk/python |
Instrumentation clients that send spans |
platform/dash |
Dashboards query APM for latency panels |
platform/kortex |
DevOps brain consumes APM for anomaly detection |