HTTP Requests and routing
Find completed HTTP requests and inspect the route to a service.
Requests is available in self-hosted alpha.20 and later. Open Requests for traffic across applications you can read, or a service's Requests tab for its current ingress routes and workload endpoints.
Find a failed request#
Filter by project, environment, application, service, method or status. Search matches literal host and path text. Select a record to inspect HTTP status, timings, response bytes, TLS metadata and the selected backend. A negative HAProxy timing means Not measured; timings can overlap and should not be added together.
The route view observes current Kubernetes ingress rules and EndpointSlices. A historical record keeps the backend that handled that request. A current endpoint is not evidence that it handled an older request.
Know what the log covers#
Only completed HTTP traffic through the configured managed HAProxy ingress is captured. Internal service traffic, raw TCP, direct pod access and dashboard API traffic bypassing that ingress are outside this view. Long-lived connections appear after completion.
Query strings, headers, cookies, authorization values and bodies are excluded. Client addresses are masked before HAProxy writes the log. Paths are retained, so do not place credentials or personal information in URL paths. Copy returns the retained record; there is no payload replay.
Retention and availability#
Retention is at most 24 hours and the newest 100,000 records across the installation. Busy installations may have a shorter window. Collection is bounded and log rotation, downtime or bursts can cause gaps. This is an operational debugging view, not a billing counter or compliance archive.
Reading requires scoped logs access. Unknown backends are visible only to an unrestricted installation administrator. A custom ingress logging configuration can make collection unavailable; Hakopod refuses to replace unowned formats. Serving traffic and collecting records are separate operations.
Read the versioned Requests reference for collection limits, operator setup and API fields.