hubble
v1.18.0 open-sourceThe section your link pointed to isn't on hubble's page any more, so we've brought you to the top.
Hubble - Network, Service & Security Observability for Kubernetes using eBPFeBPFA Linux technology for running verified programs inside the kernel without changing its source. Tools use it to observe processes, enforce rules and process network traffic.
hubble observe --print-policy-names make release hubble observe --cel-expression 'flow.IP.source == "10.0.0.5" && flow.l4.TCP.destination_port == 443' hubble observe --http-url '/api/v1/users' --http-headers 'Authorization: Bearer <token>' hubble observe --request-timeout 5s hubble observe --cluster prod-eu-west-1 hubble list namespaces hubble observe --input-file capture.json hubble observe --protocol sctp hubble observe --uuid 123e4567-e89b-12d3-a456-426614174000 hubble observe --direction egress HUBBLE_COMPAT=legacy-json-output hubble observe HUBBLE_COMPAT=legacy-json-output hubble flow --output json hubble observe -o json | jq '.flow.source' hubble observe --first hubble observe --from-identity reserved:world hubble observe -o jsonpb > flows.pb hubble status --output json hubble observe --tcp-flags=syn hubble record hubble observe --http-method POST --http-path /api/v1/nodes hubble observe --tls --client-cert ~/.hubble/cert.pem --client-key ~/.hubble/key.pem hubble observe --from-l4-port 80 --policy-verdict error
Summary
hubble is an open-source network and security observability tool for Kubernetes, built on Cilium and eBPF to give visibility into how services communicate. It runs as a command-line client (hubble observe) against flow data collected in a cluster, letting practitioners filter live traffic by policy name, drop reason, CELCELCommon Expression Language, an open-source expression language maintained by Google, used to embed lightweight, safe policy evaluation logic into tools without running a full scripting engine. expression, or source and destination cluster in multi-cluster setups. It is aimed at platform and network engineers running Cilium who need to debug connectivity issues, audit which CiliumNetworkPolicy allowed or blocked a flow, or monitor DNS and HTTP error rates across services, rather than at general application developers. It sits in the network-observability space, purpose-built around Cilium's eBPF datapath rather than a general packet capturepacket captureA packet capture, recorded network packets that can be inspected later. Analysts use it to reconstruct communication and investigate protocol behavior or suspicious traffic. tool. Started in 2019, it remains active with 57 contributors, 77 commits in the past year, and a release 77 days ago.
Hubble - Network, Service & Security Observability for Kubernetes using eBPF
How hubble helps
Why is a connection between two of my services failing, and is it DNS, TCP, or the application?
inspects the flow record for that pair and shows where it broke — DNS resolution failure, a TCP reset or timeout, or an HTTP error code — rather than just confirming the connection dropped
Which network policy blocked a specific flow, and did anything actually allow it?
shows the name of the CiliumNetworkPolicy that permitted or denied each flow it observed, so a blocked request can be traced to the rule that caused it
Which services have talked to each other, and how often?
builds a live map of source and destination pairs from observed traffic, showing which services depend on which and at what frequency
Which pods have hit DNS failures recently?
filters the flow stream for failed DNS lookups within a recent time window and lists the pods affected
Is a problem confined to one cluster or crossing between clusters?
filters observed flows by source or destination cluster, so traffic can be isolated to the cluster where it originates or lands
How do I isolate exactly the flows relevant to an incident out of everything the cluster is generating?
matches flows against a custom expression written against fields like IP, port, and direction, narrowing the stream to only the traffic in question
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for hubble, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail hubble puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
cilium.io, every changeCilium's home page and 40 more pages as they looked each month from September 2021 to October 2026: 50 renders, 1 change of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
17 entries
No entries match these filters.
- July 20261
- August 20251
- May 20251
- February 20251
- November 20241
- July 20241
- May 20241
- January 20241
- July 20231
- January 20232
- June 20221
- November 20211
- September 20211
- May 20211
- October 20201
- May 20201
Project health
Issue, contributor and maintainer activity in cilium/hubble, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.
- Contributors 3 −5 vs prior 12 months
- Maintainers 2 +1 joined · −2 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 56% of issues opened, last 12 months
- Median time to close 17 days first maintainer reply 4.1 days
- Open backlog 43 of 229 issues ever filed
- Issues opened / month 0 · 1 communitymaintainers
- Open backlog 43
- Contributors / month 0
- Commits / month 0
- Stars 4,353
- questions 10%
- other 90%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.