Skip to main content
The usage analytics endpoint provides comprehensive metrics about inference requests processed by your on-premises container. Use this endpoint to monitor request volumes, success rates, performance statistics, and current system status.
This endpoint is only available in on-premises deployments and requires a valid license.

Endpoint

Query Parameters

The time range cannot exceed 7 days. Requests with larger ranges will return a 400 error.

Authentication

This endpoint requires a valid on-premises license. If your license is invalid or expired, the endpoint returns a 423 (Locked) status code.

Response Structure

The endpoint returns a comprehensive analytics object with five main sections:

Period

The effective time range for the query (normalized to UTC):

Summary

Aggregate statistics across all request types:

By Request Type

Per-type breakdown of the same metrics:

Performance

Processing time and queue wait statistics (only includes successful requests):
Performance metrics are null when there are no successful requests in the time range. Failed requests are excluded from performance calculations.

Current Status

Live snapshot of in-progress and queued requests (not filtered by time range):

Examples

Basic Usage (Default 24-Hour Window)

Custom Time Range

Monitoring Dashboard Example

Error Responses

400 Bad Request

Invalid query parameters:

423 Locked

License validation failed:

Implementation Notes

  • Only completed requests (with end_time set) are included in summary statistics
  • Failed requests are counted in totals but excluded from performance metrics
  • Performance percentiles use linear interpolation for accurate calculation
  • Queue wait time is calculated as start_time - submission_time
  • Processing time is calculated as end_time - start_time
  • Naive datetimes (without timezone) are treated as UTC
  • The current_status section provides a live snapshot and is not filtered by the time range

Use Cases

Capacity Planning

Monitor request volumes and processing times to plan infrastructure scaling:

Performance Monitoring

Track processing times to identify performance degradation:

Queue Monitoring

Monitor queue depth to detect bottlenecks:

Next Steps

On-Prem API

Full API reference for the on-prem container.

Running the Container

Get the on-prem container up and running.

Error Codes

Understand HTTP error codes and troubleshooting.

On-Prem Overview

Compare open-source and paid on-prem options.