Distributed Tracing with OpenTelemetry

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?

Completed

0 Threads mention this feature

3 Replies

We've started building this! Will share updates as we go.


Status changed to In Progress Railway • 13 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 • 4 days ago


mrt
PRO

8 hours ago

Traces enabled, impatiently waiting for traces ui now :3


Welcome!

Sign in to your Railway account to join the conversation.

Loading...