Track outgoing queue disconnects#5331
Merged
Merged
Conversation
cloutiertyler
approved these changes
Jun 15, 2026
aasoni
approved these changes
Jun 15, 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
3 participants
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.
Description of Changes
Adds a Prometheus counter for client disconnects caused by the outgoing WebSocket message queue reaching capacity.
The new metric is
spacetime_client_outgoing_queue_disconnects_total{db=...}. It increments only on theTrySendError::Fullpath that kicks a client after its bounded outgoing queue fills.API and ABI breaking changes
None.
Expected complexity level and risk
Testing
cargo fmt --allLC_ALL=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 LANG=en_US.UTF-8 cargo check -p spacetimedb-coregit diff --check