Timeseries queries
Time-bucketed agent metrics over a window. Every timeseries query must includeinterval (or the deprecated intervalInSeconds). Each example below posts JSON to:
Authorization: Bearer <your_api_key> and Content-Type: application/json. To keep the snippets short, only the JSON body is shown; the wrapper is identical to the Overview Quick Start.
Agent metrics include every Gateway request by default. Rows that didn’t go through an agent will have
agentName, agentFramework, and agentServerType set to null and show up as null buckets in groupBy output. IS_NULL is not supported on these three fields; to scope to specific known agents, use agentName IN [...] or one of the STRING_* operators.Hourly volume per agent
Hourly volume per agent
Per-agent invocation count over time:
Hourly p99 latency per agent
Hourly p99 latency per agent
Watch latency regressions per agent:
Hourly failures over time
Hourly failures over time
Track failures per agent bucket-by-bucket:
Hourly framework mix
Hourly framework mix
Per-framework volume over time:
5-minute latency in an incident window
5-minute latency in an incident window
Fine-grained breakdown to investigate a regression:
Daily invocations over a week
Daily invocations over a week
Daily agent traffic across a 7-day window:
Hourly per-team activity
Hourly per-team activity
Per-team agent usage over time:
Hourly p99 latency for a known set of agents
Hourly p99 latency for a known set of agents
Use
agentName IN [...] to scope the timeseries to specific agents: