Connection Health

✓ functional

Every saved connection's observed health - badge, ages, last error, and a measured test latency.

Connection Health puts every saved connection in one overlay so you can see, at a glance, which ones are reachable. Each row shows a colored healthy / failed / untested badge, the profile name, an engine and routing subline (Direct or Via Relay), how long ago it last connected and was last tested, a redacted summary of its last error, and a client-measured test latency. Rows sort needs-attention first: failed, then untested, then healthy.

  • Per-row Test - re-check a single connection on demand; the row shows "Testing…" until the result lands.
  • Test All - sweep every connection sequentially and watch the badges settle, with a running tally of passed and failed. Profiles that need an interactive sign-in (Entra browser or device code, AWS or GCP IAM) are skipped and counted, so the sweep never pops sign-in windows.
  • Redacted errors - enough of the last failure to act on, without leaking secrets into the row.
  • Real routes - Via-Relay connections are tested over their actual relay route, not a shortcut, so the badge means what it says.
SQLly
SQLly Connection Health overlay
Connection Health: a row per saved connection with status badge, last-connected and last-tested ages, last error, and measured latency.

Results persist to the same connection store the Server Explorer reads, so the badges here and the tree agree afterward.