Endpoint introspection
Detailed request/response payloads and custom context tags — the exact state of your application for every trace, not just aggregates.
Specialized · Performance
Understand exactly where time is spent.
P50/P95/P99 percentiles for every endpoint, span waterfall traces, and per-endpoint drill-downs. Know exactly what's slow and why.
Service facts
The dispatcher's sheet, per endpoint
How Traceway decides what counts as slow.
- 5signals, one score
- An inverted apdex variant, error rate floor, P99 latency floor, client error floor, and volume error floor — combined into a 0-100 Impact Score.
- 3percentiles per endpoint
- P50, P95, and P99 with throughput and error-rate breakdowns and historical trend comparison.
- ≤750 msapdex anchor
- Good under 750 ms, tolerable to 1500 ms, bad above or on 5xx — override the slow threshold per endpoint.
Worst-first
If any signal is bad, the endpoint surfaces.
The Impact Score takes the max across all five indicators, so a single degraded signal can't hide inside an average. Performance dashboards are included in every plan — and in the MIT build on your own metal.
- Impact Score
- 0-100, max of fiveAdjust the slow-endpoint threshold per route to tune the apdex calculation for different latency profiles.
- Drill-down
- Any requestRequest/response payloads, waterfall spans with attributes, and custom context tags; filter by status, latency, or tag.
- Waterfall
- Operation-level timingSee which database query, external API call, or middleware adds the latency; expand spans for logs and attributes.
- Alerts
- 5 channelsSlack, GitHub Issues, email, Pushover, or custom webhooks when the Impact Score or error rate crosses a threshold.
On this line
One score. Five signals. Zero guesswork.
Per-endpoint analytics at a glance, and the full trace behind any single request when you need it.
Percentile analytics
Quickly see which routes are fast and which need attention, with per-endpoint slow-threshold overrides.
Span waterfall
Break every request into its component operations with precise timing for each span.
Apdex on your terms
A deliberate knob, so /api/health and /api/checkout are judged on their own terms.
Housekeeping
Server metrics moved.
CPU, memory, goroutines, and GC live on the Metrics page now. Performance stays focused on latency, percentiles, and waterfall span analysis.
Next stop
Measure. Find. Fix.
Performance dashboards included in every plan.