Get Namespace Errors
Changed onBatch error/failure counts for every collection & cluster in the namespace.
Returns one entry per resource that has at least one error/failure in the window, in a single response — replacing the per-resource /analytics/{collections,clusters}/{id}/failures fan-out (the Studio Monitoring "Errors & Health" N+1, which fired ~13+ calls per visit, most returning zero). Collection errors come from the extraction_events analytics collection; cluster failures from Mongo clustering_results. An empty collections/clusters list means that resource type is healthy for the window.
Recommended workflow: call this once for the aggregate health view, then call the per-resource /failures endpoint lazily ONLY for the (usually few) resources reporting errors to get the full error-type breakdown.
Example:
curl -X GET "https://api.mixpeek.com/v1/analytics/namespaces/errors?hours=24" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "X-Namespace: your-namespace"
Request
- Base URL: https://api.mixpeek.com
- URL: https://api.mixpeek.com/v1/analytics/namespaces/errors
- Auth: HTTP bearer and API key in header X-Namespace
Query parameters
Hours of history to analyze
Response
Successful Response
Changes
- warning
removed the optional property
from the response with the status - info
added the non-success response with the status
- info
added the non-success response with the status
- info
added the optional property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status
- warning
- info
the endpoint scheme security
BearerAuth AND NamespaceHeaderwas added to the API
- info