Observability
Remem provides health and operational endpoints for a single-node deployment. The Enterprise Edition also packages Prometheus and Grafana support; Community remains usable with standard HTTP checks and structured logs.
Health checks
Section titled “Health checks”curl http://localhost:4545/api/v1/healthcurl http://localhost:4545/api/v1/ready/health reports process health. /ready reports whether the server has opened
its storage and completed startup. GET /api/v1/health/deep performs an
authenticated storage and index check.
Statistics
Section titled “Statistics”curl http://localhost:4545/api/v1/stats \ -H "Authorization: Bearer $REMEM_SERVER_API_KEY"Use the response to monitor corpus size, archived data, and retrieval indexes.
Lifecycle, relationship discovery, and index repair run as durable background jobs. Inspect their status through the administrative job endpoints and use the job history when diagnosing a delayed repair or maintenance run.
Request tracing and logs
Section titled “Request tracing and logs”Every request includes an X-Request-ID header. Provide one to correlate a
request across a reverse proxy and your application logs; otherwise Remem
generates one.
Configure log level and format in remem.toml:
[log]level = "info"format = "json"Enterprise observability
Section titled “Enterprise observability”Prometheus metrics and pre-built Grafana dashboards are part of the Enterprise Edition packaging. They are not required for Community deployments, which can use the health, readiness, statistics, and job endpoints above.