5 hours ago
What do NO_SOCKET and complete mean in network-flow logs? Can existing logs distinguish a platform-initiated disconnect from packets arriving after an application closes its socket, and show TCP FIN/RST direction or the first drop time?
1 Reply
5 hours ago
Each network flow row is a summary of one connection over a capture window. It includes flowState (for example complete), direction, protocol, source and destination address and port, peer, byte and packet counts, L4 latency, dropCause (for example NO_SOCKET) and the captureStart and captureEnd times. You can filter on the drop cause with --drop-cause or @drop_cause:NO_SOCKET, as shown in the railway logs reference.
The rows have no TCP flags, so they can't show a FIN or RST or which side sent it. There's also no per-packet timestamp, so the most precise you can get for a drop is the capture window of the row that carries it. On their own, these logs can't separate a disconnect started on our side from packets that arrive after your application has closed its socket. For that, you'd need a packet capture or connection-close logging inside your application, recorded with timestamps in UTC.
Status changed to Awaiting User Response Railway • about 5 hours ago