Tracing an AI request through Cloudflare and its origin
Follow a slow AI request from Cloudflare to an instrumented origin, configure sampling, and verify that the trace preserves the evidence needed to investigate.
Understand what your systems are telling you, and what they are not.
Follow a slow AI request from Cloudflare to an instrumented origin, configure sampling, and verify that the trace preserves the evidence needed to investigate.
API Gateway now supports API keys for MCP tools/list. Discovery and execution keep separate authentication rules, and the MCP feature remains in Preview.
Build a latency SLI from Prometheus histogram buckets, include failed requests, and compare classic and native queries with a worked search-service example.
Cloud Tasks now lets each job override queue retry settings. A job’s expiry and the outcome of earlier attempts still determine whether another delivery is useful.
Apigee separates model latency and token use from MCP tool traffic. Tool filters narrow a slow-assistant investigation, while proxy policies determine which charts populate.
A synthetic order-service incident follows a shared handoff through page edits, new findings and shift change, including the review and access work involved.
Google API Gateway’s streaming preview delivers response chunks while a model is still generating. Creation-time settings and request deadlines shape the migration.
Tail sampling selects recorded traces by error, latency and other evidence. A checkout timeout shows how routing, waiting time and memory affect the trace a responder can retrieve.
Standard maintenance has ended for Google’s legacy agents. Migration to Ops Agent changes some metric fields, including disk labels used by existing queries.
A durable queue can preserve telemetry through an outage, then take longer to catch up. Arrival rate, export capacity and event age explain what recovery looks like.
Zero errors, no traffic and absent series produce different PromQL results. Synthetic tests show how ratios, fallback zeros and absence checks behave for a checkout service.
Kubernetes attributes connect agent calls to pods, workloads and paging routes. A processor migration can break those connections while telemetry still flows.