Skip to main content
This page describes the logging-based telemetry emitted by the platform. These are log events, not Prometheus metrics, and are intended for detailed debugging, performance analysis, and forensics. Log events are typically ingested into a log backend such as OpenSearch or Loki and queried via Grafana or a similar tool.

RDU manifest events

RDU manifest events are structured logs emitted per request by the model runtime. They contain token counts, high-level latencies, and a set of detailed timing fields. These events are typically indexed into a log index (for example, an OpenSearch index) and can be filtered by fields such as model, tenant, pod, and time range.

RDU manifest fields

These fields are logging events and may be subject to schema evolution.

Example queries

Examples assume a log backend that supports a query language (e.g., OpenSearch or Loki) and timestamps on each event. p95 total latency per model (last 15 minutes)
  • Filter: model:"<model_name>" AND @timestamp:[now-15m TO now]
  • Aggregate: percentile 95 on total_latency grouped by model.
TTFT vs total latency comparison
  • Group by model, compute p50/p90 for both time_to_first_token and total_latency.
Decode queue time hotspots
  • Filter: decode_queue_time > <threshold>
  • Group by model or tenant to identify where queueing is highest.
Speculative decoding acceptance rate
  • Filter: model:"<model_name>"
  • Aggregate: average acceptance_rate over time.