Connection Health Monitoring

The Health Dashboard

Every configured connection in VersionForge displays a real-time health indicator on the Connections dashboard. At a glance, you can see which connections are operating normally, which are experiencing issues, and which are completely unavailable.

Health statuses:

| Status | Indicator | Meaning | |--------|-----------|---------| | Healthy | Green | The connection authenticated successfully, the endpoint is reachable, and the last sync completed without connector errors. | | Degraded | Amber | The connection is functional but experiencing issues: slow response times, approaching rate limits, or intermittent authentication failures. | | Down | Red | The connection cannot authenticate or the endpoint is unreachable. Syncs using this connection will fail. | | Unknown | Gray | Health has not been checked yet (new connection) or checks are disabled. |

How Health Checks Work

VersionForge runs automated health checks on every connection at regular intervals:

• Check frequency -- Every 6 hours by default. You can adjust this per connection in Connection Settings > Health Check Interval (minimum: 1 hour, maximum: 24 hours).
• What is checked:
  • Credential validation -- Can VersionForge authenticate with the stored credentials?
  • Endpoint reachability -- Does the API endpoint respond within the timeout window (default: 30 seconds)?
  • Rate limit status -- For connectors with known rate limit headers (Stripe, NetSuite), is the connection approaching its limit?
• Check method -- Health checks use lightweight, read-only API calls that do not count against sync quotas and have minimal impact on the source system.

Automatic Alerts

When a connection's health status changes, VersionForge sends an alert through your configured channels (Slack, email, or both). See Alert Configuration for setup details.

Alert behavior:

• Healthy to Degraded -- A warning alert is sent. No immediate action is required, but you should investigate.
• Healthy/Degraded to Down -- A critical alert is sent. Syncs using this connection will fail until the issue is resolved.
• Down to Healthy -- A recovery alert is sent confirming the connection is back online.

Health History

VersionForge tracks the health status of every connection over time. To view health history:

1. Navigate to Connections and click on the connection name.
2. Open the Health tab.
3. The health timeline shows status changes over the last 30 days, including:
   • Timestamp of each status change
   • Previous status and new status
   • Error details for degraded/down events (e.g., "HTTP 401 Unauthorized", "Connection timeout after 30s")

The health timeline helps you identify patterns: a connection that degrades every Monday morning at 8 AM may be hitting rate limits when other systems are also active.

Programmatic Health Checks

You can query connection health via the REST API:

# Get health status for all connections
curl -X GET https://your-instance.versionforge.com/api/v1/connections/health \
  -H "Authorization: Bearer YOUR_API_TOKEN"

Response:

{
  "connections": [
    {
      "id": "conn_abc123",
      "name": "NetSuite Production",
      "type": "netsuite",
      "status": "healthy",
      "lastChecked": "2026-04-12T14:30:00Z",
      "latencyMs": 245
    },
    {
      "id": "conn_def456",
      "name": "Workday HCM",
      "type": "workday",
      "status": "degraded",
      "lastChecked": "2026-04-12T14:30:00Z",
      "latencyMs": 12400,
      "issue": "Response time exceeds 10s threshold"
    }
  ]
}

Use this endpoint to build custom monitoring dashboards or integrate VersionForge health status into your existing observability tools (Datadog, PagerDuty, etc.).