Skip to content

feat(dgw): clarify agent tunnel status - #1960

Closed
irvingouj@Devolutions (irvingoujAtDevolution) wants to merge 2 commits into
feat/agent-tunnel-identity-lifecyclefrom
feat/agent-tunnel-management-status
Closed

feat(dgw): clarify agent tunnel status#1960
irvingouj@Devolutions (irvingoujAtDevolution) wants to merge 2 commits into
feat/agent-tunnel-identity-lifecyclefrom
feat/agent-tunnel-management-status

Conversation

@irvingoujAtDevolution

@irvingoujAtDevolution irvingouj@Devolutions (irvingoujAtDevolution) commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Clarifies the Agent Tunnel management status returned to administrators.

The API now distinguishes online, unresponsive, and offline Agents. Runtime route information remains available when known, while certificate fingerprints and internal route synchronization epochs are no longer exposed.

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

Expose online, unresponsive, and offline Agent states through the
management endpoints.

Keep routing information available when runtime state exists, and stop
publishing certificate fingerprints and route synchronization epochs.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Verify that a connected Agent with an expired heartbeat is reported as
unresponsive while retaining its last runtime snapshot.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@irvingoujAtDevolution irvingouj@Devolutions (irvingoujAtDevolution) changed the title feat/agent tunnel management status feat(dgw): clarify agent tunnel status Aug 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant