Control
Observability
Every request carries a correlation_id, and the Executive Summary shows usage, models, latency and provider health on one screen.
Executive Summary
| Card | What it shows |
|---|---|
| Usage trend | Daily input / output tokens; up to the last 30 days |
| Model breakdown | Requests, token share, spend, latency (avg / p95) |
| Latency | Average, p50, p95 (latency_ms) |
| Top users | Top 5 people by tokens, based on X-FFM-User |
| Provider health | Failed request rate by model and provider |
| Personal data protection | Event and detection counts, by outcome and type |
The cards group the usage record the gateway writes for every request by day, model and person. Until at least 20 requests have accumulated, p95 shows "—". The data comes from the GET /admin/dashboard/overview endpoint and is available only to the system_admin role.
Tracing with correlation_id
A request's audit, usage and log records are all linked by the same correlation_id. When you investigate an error or a complaint, this ID takes you to every record for that request.
| AUDIT LOG | OBSERVABILITY | |
|---|---|---|
| Question | Who did what? | What happened where? |
| Scope | Auditing, compliance, permanent record | Usage, latency, where errors occur |
| Sampling | Never | Allowed |
| Shared key | correlation_id | correlation_id |
OpenTelemetry and license
BaseLLM can send its traces and metrics to your own monitoring system over OpenTelemetry (OTLP); Prometheus can also read the metrics at /metrics. That address runs on a port separate from the API.
- Enterprise and trial
on: Traces and metrics are sent. - Individual
off: Nothing is sent;/metricsanswers 403. - When the license expires
stops: Sending stops within a minute.