impl: notify user when agent can't be contacted #249
Merged
Conversation
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
At a recent customer incident the Coder server could not ping the agent for a short brief of time because of intermittent network issues. The user had no idea they have network issues and was expecting the ssh sessions to work flawlessly. This PR lays the groundwork for monitoring the connection by checking the status for workspace, agent and agent lifecycle and make an educated guess when the network runs into issues. - resolves #246
Collaborator
Author
|
code-asher
approved these changes
Jan 20, 2026
f0ssel
approved these changes
Jan 21, 2026
We notify the user only once, for all workspaces if there is a network disconnection detected.
code-asher
approved these changes
Jan 21, 2026
src/test/kotlin/com/coder/toolbox/util/ConnectionMonitoringServiceTest.kt
Outdated
Show resolved
Hide resolved
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.
At a recent customer incident the Coder server could not ping the agent for a short brief of time because of intermittent network issues. The user had no idea they have network issues and was expecting the ssh sessions to work flawlessly.
This PR lays the groundwork for monitoring the connection by checking the status for workspace, agent and agent lifecycle and make an educated guess when the network runs into issues.