Metrics API
Retrieve agent performance data, historical metrics, and music industry analytics.System stats
The in-process counters (
messages and errors) are held in memory and reset when the web application restarts. They are not persisted to a database.Response
Response fields
The
health field is computed from CPU and memory thresholds:
Error response
On failure, the endpoint returns HTTP500 with zeroed counters and health: "unhealthy":
Errors
Platform metrics
This endpoint is served by the web application, not the backend API service. It is not available on the backend base URL.
averageResponseTime, successRate, errorRate, cpu, memory) is fetched from the backend metrics service when at least one active agent exists; otherwise these fields fall back to computed defaults or 0. The messages fields are not tracked in the frontend database and always return 0.
Response
Response fields
Errors
Historical metrics
The per-user metrics endpoints below are served by the backend API service, not the web application. They are available at the backend base URL, which may differ from the web API base URL depending on your deployment.
container_metrics database table, aggregated by hour. If no database history exists for the requested range, the endpoint falls back to a single live container sample.