Distributed tracing that follows every request across your services
Ingest spans and traces, see each request as a waterfall, map your services automatically, and find slow hops with p50/p95/p99 latency analytics.
Find the slow hop in a request that touches ten services
In a microservices architecture, a single user request can cross an API gateway, three services, a queue, and two databases before a response comes back. When that request is slow or fails, per-service logs only show you fragments. Without distributed tracing, the question "where did the time go?" turns into hours of correlating timestamps across systems by hand.
AllStak is a distributed tracing tool that puts the whole journey on one screen. Spans flow in from AllStak SDKs or any OpenTelemetry instrumentation via the OTLP traces endpoint, and each request renders as a waterfall: every service, every call, every millisecond. A service map shows how your systems actually talk to each other, and trace analytics with p50/p95/p99 latency percentiles tell you which endpoints are slow for real users — all in the same platform as your errors and logs.
Everything you need to trace requests across microservices
From span ingestion to latency percentiles, AllStak gives you the views that turn a distributed mystery into a single, readable timeline.
Spans & traces ingestion
Send spans from AllStak SDKs or any OpenTelemetry-instrumented service over the OTLP traces endpoint, and they assemble into complete end-to-end traces.
Waterfall trace view
Each trace renders as a waterfall of spans with timing, so you see exactly which call in which service consumed the time — no timestamp archaeology.
Service map
A map built from your real traffic shows how services depend on each other, so you understand the blast radius of a slow or failing dependency at a glance.
p50 / p95 / p99 latency analytics
Trace analytics break latency down by percentile, so you optimize for the slow tail your users actually feel, not a misleading average.
OpenTelemetry compatible
Already instrumented with OTel? Point your exporter at AllStak's OTLP traces endpoint and keep your vendor-neutral instrumentation exactly as it is.
Traces next to errors & logs
Tracing lives in the same platform as error tracking, logs, and uptime, so you move from a slow trace to the exception behind it without switching tools.
Start tracing in minutes
- 1Create a free project
Sign up at app.allstak.sa, create a project, and copy your API key. No credit card required on the free tier.
- 2Instrument your services
Use AllStak SDKs for your stack, or keep your existing OpenTelemetry setup and point the OTLP exporter at AllStak's traces endpoint.
- 3Explore traces & the service map
Open any request as a waterfall of spans, follow it across services, and watch the service map build itself from your real traffic.
- 4Hunt latency with percentiles
Use trace analytics to rank endpoints by p95 and p99, find the slow hop, ship the fix, and verify the percentile drop in the same view.
Why teams choose AllStak for distributed tracing
- See the whole request journey on one waterfall instead of correlating logs across ten services by hand.
- Optimize what users actually feel with p50/p95/p99 percentiles instead of averages that hide the slow tail.
- Understand your architecture as it really is with a service map built from live traffic, not an outdated diagram.
- Keep your OpenTelemetry instrumentation — AllStak accepts OTLP traces, so switching in doesn't mean re-instrumenting.
- One platform, one bill: tracing sits next to errors, logs, uptime, and infrastructure instead of a separate APM vendor.
- SAR pricing and data residency in Saudi Arabia, built for Saudi and GCC teams.
Distributed tracing FAQ
What is distributed tracing?
Distributed tracing follows a single request as it travels across multiple services, recording a span for each operation along the way. The spans assemble into a trace you can read as a waterfall, showing exactly where time was spent and where failures occurred — essential once your system is more than one service.
Does AllStak work with OpenTelemetry?
Yes. AllStak accepts OTLP trace export over HTTP, so any service instrumented with OpenTelemetry SDKs can send traces by pointing its exporter at AllStak. You keep vendor-neutral instrumentation and avoid lock-in. See the setup guide at /docs/guides/opentelemetry.
How is AllStak different from Datadog APM?
Datadog prices APM hosts, ingestion, and retention separately, and costs climb quickly as you scale. AllStak gives you waterfall traces, a service map, and percentile analytics inside one all-in-one platform with errors, logs, uptime, and infrastructure — with predictable SAR pricing and data residency in Saudi Arabia.
How long does setup take?
If you already use OpenTelemetry, it's a config change: point your OTLP exporter at AllStak and traces start flowing. Starting from scratch with an AllStak SDK typically takes minutes per service — install, init with your key, and deploy.
Is there a free tier for distributed tracing?
Yes. Create a free project and start sending spans without a credit card. When your trace volume grows, upgrade to a predictable paid plan with SAR pricing — no per-host APM surcharges.
Explore more
Start tracing requests for free
Instrument with AllStak SDKs or OpenTelemetry, open your first waterfall trace, and find the slow hop — traces, errors, and logs on one platform with one predictable bill.