Files

T

Sergey Antropoff 48df10b17e Prepare 0.1.0 for lab release: durable handlers, HTTP Compose, CI, and pulumi-tests.

- Harden DB-backed handlers and seed profiles; align client wire shapes for
  cluster resources, QEMU config, and node SSL fields
- Serve plain HTTP on Compose :8006; keep TLS optional (--profile tls) and
  terminate HTTPS at Kubernetes Ingress
- Add pulumi-tests (full contract surface majors 6–9 + BPG lifecycle) and
  make pulumi-tests
- Ship bilingual docs, CHANGELOG, SECURITY, CONTRIBUTING, and GitHub Actions
  (make ci + Compose/Helm validation)

2026-07-18 04:18:05 +03:00

1.2 KiB

Raw Blame History

Language / Язык: English | Русский

Observability

Health

Path	Meaning
`GET /health/live`	Process liveness
`GET /health/ready`	Database reachable and migrations current; HTTP 503 when not

Example:

curl -s http://localhost:8006/health/live
curl -s http://localhost:8006/health/ready

Request correlation

Incoming requests accept or generate an ID via REQUEST_ID_HEADER (default X-Request-ID). Structured logs include correlation fields and redact known secret patterns.

Metrics / tracing

There is no Prometheus /metrics scrape endpoint and no bundled OpenTelemetry exporter in the current application. Architecture notes that mention them describe target design, not shipping telemetry.

Do not confuse Proxmox API paths under /cluster/metrics with simulator process telemetry — those handlers simulate PVE metrics-server configuration state inside PostgreSQL.

Compatibility evidence

Operational compatibility reports:

/admin/compatibility
/admin/compatibility.md
/admin/compatibility.html

Also available through the Web UI compatibility panel.

1.2 KiB Raw Blame History