a month ago
Right now, debugging a failure across multiple services in a project can be difficult. You have to manually piece together logs across services, based on timestamp, to be able to figure out what went wrong.
We're adding built-in distributed tracing powered by OpenTelemetry. Instrument your app with any OTEL SDK and export traces directly to Railway with zero config. Credentials are injected automatically into your Railway service. Railway's edge layer will generate the root span for incoming requests and propagate trace context across your services, so you get a full request waterfall out of the box. The dashboard gets a new traces view where you can search by trace ID, filter spans across services, and see exactly where time is spent. MCP tools will also support querying traces, so AI agents can debug issues more effectively too.
Would love to hear what matters most to you — what's your biggest pain point debugging across services today?
0 Threads mention this feature
6 Replies
Status changed to In Progress Railway • 28 days ago
19 days ago
This just landed in Priority Boarding for early access. Give it a try and let us know what you think!
Status changed to Completed Railway • 19 days ago
16 days ago
Traces enabled, impatiently waiting for traces ui now :3
mrt
Traces enabled, impatiently waiting for traces ui now :3
14 days ago
Great! You should be able to see the traces UI by clicking on the "Tracing" tab next to the "Logs" tab at the project level, in the left hand sidebar.
lucacasonato
Great! You should be able to see the traces UI by clicking on the "Tracing" tab next to the "Logs" tab at the project level, in the left hand sidebar.
14 days ago
I don't have this tab (yet?)
Tabs are: architecture, observability, logs, sandboxes, settings
But I do see traces from the cli:
railway trace list --since 30m
Traces for service app-v2 in environment feat/cap-v2 since 30m (newest first):
Started Duration Spans Errors Root Trace ID
2026-09-28 10:57:01 30.0ms 1 0 railway-origin-proxy › origin_proxy.request xxx
2026-09-28 10:57:00 8.4ms 1 0 railway-origin-proxy › origin_proxy.request xxx
2026-09-28 10:57:00 38.4ms 1 0 railway-origin-proxy › origin_proxy.request xxx
2026-09-28 10:57:00 8.4ms 1 0 railway-origin-proxy › origin_proxy.request xxx
2026-09-28 10:57:00 30.7ms 1 0 railway-origin-proxy › origin_proxy.request xxx
2026-09-28 10:57:00 30.1ms 1 0 railway-origin-proxy › origin_proxy.request xxx
2026-09-28 10:57:00 4.0ms 1 0 railway-origin-proxy › origin_proxy.request xxx
2026-09-28 10:57:00 5.1ms 1 0 railway-origin-proxy › origin_proxy.request xxx
2026-09-28 10:56:59 182.2ms 4 0 railway-edge › edge.request xxx
2026-09-28 10:56:59 153.9ms 4 0 railway-edge › edge.request xxx
2026-09-28 10:56:59 217.1ms 4 0 railway-edge › edge.request xxx
Attachments
mrt
I don't have this tab (yet?) Tabs are: architecture, observability, logs, sandboxes, settings  But I do see traces from the cli: ``` railway trace list --since 30m Traces for service app-v2 in environment feat/cap-v2 since 30m (newest first): Started Duration Spans Errors Root Trace ID 2026-09-28 10:57:01 30.0ms 1 0 railway-origin-proxy › origin_proxy.request xxx 2026-09-28 10:57:00 8.4ms 1 0 railway-origin-proxy › origin_proxy.request xxx 2026-09-28 10:57:00 38.4ms 1 0 railway-origin-proxy › origin_proxy.request xxx 2026-09-28 10:57:00 8.4ms 1 0 railway-origin-proxy › origin_proxy.request xxx 2026-09-28 10:57:00 30.7ms 1 0 railway-origin-proxy › origin_proxy.request xxx 2026-09-28 10:57:00 30.1ms 1 0 railway-origin-proxy › origin_proxy.request xxx 2026-09-28 10:57:00 4.0ms 1 0 railway-origin-proxy › origin_proxy.request xxx 2026-09-28 10:57:00 5.1ms 1 0 railway-origin-proxy › origin_proxy.request xxx 2026-09-28 10:56:59 182.2ms 4 0 railway-edge › edge.request xxx 2026-09-28 10:56:59 153.9ms 4 0 railway-edge › edge.request xxx 2026-09-28 10:56:59 217.1ms 4 0 railway-edge › edge.request xxx ```
14 days ago
You need to enable Priority Boarding -> Tracing in https://railway.com/account/feature-flags to view the tracing UI.
