Backup & Restore
Backing up and restoring every persistent store in a GENIE.AI deployment — ArangoDB knowledge base, PostgreSQL (Kong + Keycloak), Redis cache, document-repository uploads, and supporting volumes.
Deployment gets GENIE.AI running; this section keeps it running. It is for operators and administrators responsible for a live deployment: backing up data, applying updates, scaling, and diagnosing problems.
For real-time health, dashboards, and alerting, see Observability — this section assumes you already have the observability stack on and are watching it.
/api/admin/logs/* endpoints, the MELT seam, and the VL fallback
configuration./api/health and
/api/admin/system-health endpoints, Docker Swarm healthcheck wiring,
Kubernetes probe recipes, and failure-mode troubleshooting.Backing up and restoring every persistent store in a GENIE.AI deployment — ArangoDB knowledge base, PostgreSQL (Kong + Keycloak), Redis cache, document-repository uploads, and supporting volumes.
W3C traceparent propagation across the RAG pipeline, the span taxonomy, and automatic PII filtering.
Updating models, service images, and the GENIE.AI stack — and which changes require re-ingesting the knowledge base.
Common GENIE.AI operational problems, where to look first, and pointers to the deeper troubleshooting notes in the deployment guides.
Operator-facing Logs tab in the GENIE.AI admin UI — VictoriaLogs-backed log search, summaries, and the MELT seam.
The per-chunk ingestion progress log surfaced by dataprep — how to read it, where it lives, and what its messages mean.
Operational health endpoints — the public /api/health probe and the admin /api/admin/system-health diagnostic — with wiring examples for Swarm, Kubernetes, and Prometheus.
Defense-in-depth controls built into the GENIE.AI backend and frontend — the sensitive-path blocker, Helmet security headers, robots.txt policy, and the user-profile static file surface.
How to scale every service in the GENIE.AI stack — stateless services scale freely, stateful services need replicas with shared storage, AI services are GPU-bound.