checkId: check.servicegraph.backend plugin: stellaops.doctor.servicegraph severity: fail tags: [servicegraph, backend, api, connectivity]

Backend API Connectivity

What It Checks

Reads StellaOps:BackendUrl (or the bare BackendUrl fallback), appends /health, and performs an HTTP GET through IHttpClientFactory.

Condition	Result
Successful response (2xx) under 2000 ms	`pass`
Latency exceeds 2000 ms	`warn`
Non-success status code (4xx/5xx) or connection error	`fail`

The backend API is the control-plane entry point for many Stella Ops flows. If it is unreachable, Console features and cross-service orchestration degrade quickly — releases stall, evidence cannot be written, and operators lose visibility into pipeline state.

Common Causes

StellaOps__BackendUrl points to the wrong host, port, or scheme
The backend service is down or returning 5xx
DNS, proxy, or network rules block access from the Doctor service

How to Fix

Docker Compose

services:
  doctor-web:
    environment:
      StellaOps__BackendUrl: http://platform-web:8080

docker compose -f devops/compose/docker-compose.stella-ops.yml exec doctor-web curl -fsS http://platform-web:8080/health
docker compose -f devops/compose/docker-compose.stella-ops.yml logs --tail 100 platform-web

Bare Metal / systemd

curl -fsS http://<backend-host>:<port>/health
journalctl -u <backend-service> -n 200

Kubernetes / Helm

kubectl exec deploy/doctor-web -n <namespace> -- curl -fsS http://<backend-service>.<namespace>.svc.cluster.local:<port>/health
kubectl logs deploy/<backend-service> -n <namespace> --tail=200

Verification

stella doctor run --check check.servicegraph.backend

check.servicegraph.endpoints — validates the rest of the service graph once the main backend is reachable
check.servicegraph.timeouts — slow backend responses often trace back to timeout tuning