v0.11.0: HTTP details on links where Cilium parses L7

Requests, response classes, p50/p95 latency and the busiest paths per link,
from Hubble L7 flows (method, path, status, latency only; headers are never
requested). The two inner legs of a proxied connection (Envoy -> pod, and the
pod's answers to the node on an ephemeral port) are no longer counted as
links.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Виталий Чефанов
2026-09-25 02:13:10 +03:00
co-authored by Claude Opus 5.5
parent c50020e420
commit 4c5eb288cb
11 changed files with 587 additions and 17 deletions
+11 -1
View File
@@ -73,6 +73,16 @@ The collector runs in one of three modes, see `traffic.mode`:
History is kept in memory: after a pod restart the windows fill again. The status line says how much of the window has actually been seen.
## HTTP details
Where Cilium parses HTTP on a port, the map adds to that link the number of requests, responses by class (2xx, 3xx, 4xx, 5xx), p50 and p95 latency and the ten busiest paths. A link with 5xx responses is drawn in the warning colour. Paths are grouped: the query string is dropped and segments that look like IDs (numbers, UUIDs, long hex strings) become `:id`, so `/api/users/42?x=1` and `/api/users/43` are one row `/api/users/:id`.
Cilium parses HTTP only on ports named in an L7 rule of a `CiliumNetworkPolicy`; the module does not create such policies. To enable it for one service without restricting its traffic, see [the example](EXAMPLES.md#http-details-for-one-service). Keep in mind:
- the connections to that port go through the Envoy proxy on the node: a fraction of a millisecond per request and CPU of the Cilium agent in proportion to the request rate;
- the port must speak plain HTTP/1.x or HTTP/2 (h2c): Envoy cannot see inside TLS, so put the rule on the backend port behind the Ingress, not on 443. gRPC is parsed, but its status is in the trailers and every call shows as 200; a gRPC stream or a WebSocket is one request, not a series of messages;
- request and response headers reach Hubble, including `Authorization` and cookies. The module asks Hubble for the method, path, status and latency only; the headers are not read, stored or shown. Other Hubble clients (the Hubble UI, `hubble observe`) do see them.
## Requirements
- Deckhouse Kubernetes Platform 1.72 or newer.
@@ -107,4 +117,4 @@ The pod exposes Prometheus metrics on port `9090` (`cluster_map_*`: Hubble strea
- One replica: traffic history lives in the process. A second replica would keep its own history and double the load on hubble-relay.
- Visibility is by namespace: a user who can list pods in a namespace sees all its cards, including the manifests of its Deployments and Services, even if their role would not let them read those objects one by one.
- Alerts need the `prometheus` module, which creates `ClusterAlert` objects. Without it the map shows problems from object state and events only.
- Traffic is L3/L4. HTTP-level details (paths, status codes) need Cilium L7 visibility and are not shown yet.
- HTTP details only where a CiliumNetworkPolicy turns on L7 parsing, see [HTTP details](#http-details). Other protocols are shown at L3/L4.