8 days ago
-
Which exact duration field feeds HTTP p50/p90/p95/p99, and does its interval end at first byte, upstream completion or full response completion? How are aborted/streamed requests counted?
-
Which requests are included/excluded from totalRequests and latency population: health, edge rejection, upstream failure, cancellation and zero-body responses? Are latency and 5xx denominators identical?
-
Are observations sampled or dropped; what completeness, ingestion-delay and finalization guarantees exist for returned buckets, especially partial edge buckets?
-
Is path the raw request path or a normalized application route template? What cardinality/redaction behavior applies to unknown or identifier-bearing paths?
1 Reply
Status changed to Awaiting Railway Response Railway • 8 days ago
8 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 8 days ago
8 days ago
- The fields are already aggregated. And IIRC, it's full response completion (from edge network to proxy to app's response time).
- The 5xx and latency denominators are identical.
- Results are bucketed at variable intervals depending on the time range being viewed.
- It's just a string filter that shows the path the user tried to access.