heart-beat

Ecosystem health monitor - watches all services, auto-restarts crashes

Updated: March 29, 2026

heart-beat

The ecosystem health monitor daemon - Tier 0 service

Heart-Beat is the first service that starts and the last to shut down. It continuously monitors all F3L1X services, detects crashes, and can auto-restart failed realms.


What It Does

Heart-Beat serves as:

  1. Health Monitor - Pings all registered services on their health endpoints
  2. Auto-Restart - Detects crashed services and restarts them automatically
  3. Dependency Graph - Knows which services depend on which for startup ordering
  4. Status API - Provides a REST endpoint consumed by Dashboard and realm-startup
  5. CLI Status - python manage.py status --refresh for a terminal health table

Think of Heart-Beat as the heartbeat monitor in an ICU - it watches everything and alerts when something goes wrong.


Key Capabilities

Continuous Monitoring

Heart-Beat polls all registered services every few seconds:

Check What It Verifies
HTTP Health Service responds to /api/health/ with 200
Port Availability Service is listening on its assigned port
Response Time Service responds within timeout threshold
Process Status Service process is running

Auto-Restart

When a service fails health checks:
1. Heart-Beat logs the failure
2. After consecutive failures, triggers restart
3. Verifies the service comes back healthy
4. Notifies Dashboard of the incident

Status API

The /api/status/ endpoint returns the full ecosystem health as JSON, consumed by:
- F3L1X Dashboard (real-time status panel)
- Realm-Startup (boot verification)
- Worker-Bee (ecosystem health checks)


Accessing Heart-Beat

CLI Status

python manage.py status --refresh

Shows a table of all monitored services with health status.

REST API

Endpoint Purpose
/api/status/ Full ecosystem health JSON
/api/status/{realm}/ Single realm health

Important Notes

Tier 0 Service

Heart-Beat is Tier 0 - it starts before everything else during boot and shuts down last. If Heart-Beat is not running, you have no health monitoring.

Dashboard Integration

The F3L1X Dashboard proxies Heart-Beat data at /api/realms/ecosystem-health/ for the real-time status panel.


  • F3L1X Dashboard - Displays Heart-Beat health data
  • Realm-Startup - Uses Heart-Beat for boot verification
  • Worker-Bee - Cross-references Heart-Beat for ecosystem checks
  • All realms - Monitored by Heart-Beat

Further Reading

Want to query this documentation programmatically? The F3L1X MCP server gives any AI agent search_docs, get_doc_page, and get_realm_doc tool access to the full docs library — available on the Elevated plan.