13 days ago
In Railway HTTP logs, does the requestId value for an HTTP request equal the X-Railway-Request-Id value returned in the HTTP response headers for that same request?
Specifically, are those two fields the same Railway request identifier in the same identity namespace, such that an exact value match means the response and HTTP-log record refer to the same request event?
If not, what is the relationship between them?
1 Replies
13 days ago
Yes. Our HTTP proxy generates the X-Railway-Request-Id value for each request and records that same value as requestId in the HTTP logs, so they are one Railway-generated correlation identifier. An exact match is a reliable way to tie a response to its HTTP log record for troubleshooting.
There are three limits to that. First, your application can add its own X-Railway-Request-Id header to a response. That does not replace our value, which comes first, but the response can end up with more than one value under that name, and client libraries handle repeated headers differently. Second, request IDs are correlation identifiers, not guaranteed globally unique keys across deployments or over time. Third, HTTP logs are operational data, not a guaranteed-complete ledger, so a single match does not prove that exactly one such request happened. You can filter logs by request ID with railway logs --http --request-id <id> (docs).
Status changed to Awaiting User Response Railway • 13 days ago
6 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 6 days ago