NetObserv vs Apache Superset

NetObserv ships roughly monthly as a coordinated bundle — operator, eBPF agent, flowlogs-pipeline and console plugin move together in each release. The functional work over these six releases splits three ways: a TLS visibility feature that arrived as a knob in 1.11.3 and has been extended with metrics and alerts since, a Network Health layer built on Prometheus recording rules rather than alerts alone, and steady hardening of the agent-to-pipeline path (mTLS, hot-reload filters, packet translation and sampling fixes). Prometheus is now on by default.

The project is moving from flow collection toward opinionated health signalling — recording rules, runbook links in alerts, ingress 5xx and latency templates, health metadata driving console plugin config. That is the shape of a tool trying to answer 'is the network healthy' rather than only 'what traffic occurred'. In parallel, supply-chain and workflow security is getting real attention: SBOM generation and artifact signing, SHA-pinned GitHub Actions, pwn-request workflow checks and a pprof exposure fix all landed in the last two releases. The operator was also renamed from network-observability-operator to netobserv-operator.

Expect the TLS thread to keep extending — the sequence so far is fields, then metrics, then alerts, so dashboards and health rules built on TLS data are the natural next step. Continued investment in the Network Health rule set is the other safe bet, since it is where the last three releases have concentrated their non-dependency commits.