Repository navigation
Enable TCP keepalive on the scribe tail connection - #78
Merged
Merged
Conversation
The scribe hosts we use to tail are behind NLBs, which will drop connections after they've been idle for a while. This drop happens silently: we don't notice on our end and keep waiting forever - which results in folks being confused when the PaaSTA Slack buttons sometimes work and sometimes don't. To fix this, we can either start send heartbeat messages into this stream (lol) or send keepalive probes as AWS recommends to keep the connection open. ...and since keepalives are less hacky, that's what we'll do :p
nemacysts
force-pushed
the
luisp/scribe-tail-keepalive
branch
from
October 12, 2026 20:52
bacf0a7 to
924d3af
Compare
jall0h
approved these changes
Oct 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The scribe hosts we use to tail are behind NLBs, which will drop connections after they've been idle for a while.
This drop happens silently: we don't notice on our end and keep waiting forever - which results in folks being confused when the PaaSTA Slack buttons sometimes work and sometimes don't.
To fix this, we can either start send heartbeat messages into this stream (lol) or send keepalive probes as AWS recommends to keep the connection open.
...and since keepalives are less hacky, that's what we'll do :p