Pim van Pelt
badb684431
The previous wrapper skipped nginx's duplicate-listen check only
for listens that carried device=, so a `listen 80;` next to a
`listen 80 device=eth0 ...;` in the same server block was
rejected at config time. Under SO_BINDTODEVICE that restriction
tracked a real kernel constraint (device-tagged listens created
separate sockets, a bare listen alongside them was genuinely
ambiguous). Under the IP_PKTINFO model introduced in 450391a
the constraint no longer exists — all same-sockaddr listens
collapse to one wildcard kernel socket and attribution is a
per-connection cmsg readback — but the wrapper kept enforcing
the old rule by accident.
Extend the (cscf, sockaddr) dedup in the listen wrapper to
cover plain listens too: the first occurrence at a given
(server, sockaddr) pair calls nginx's handler and registers the
kernel socket, and every subsequent sibling — plain or
device-tagged — is accepted without tripping nginx's
duplicate-listen check. Device-tagged siblings additionally
push a binding into the attribution table as before; plain
siblings contribute only the seen-list entry. No code path
exercised by the existing 22 e2e tests changes behavior.
Update FR-1.5, the user-guide "shared port" section, the
module's top-of-function comments, and the test nginx.conf
comment to describe the relaxed rule. Bump VERSION and add a
debian/changelog entry for 0.7.1.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
87 lines
3.6 KiB
Plaintext
87 lines
3.6 KiB
Plaintext
nginx-ipng-stats-plugin (0.7.1-1) unstable; urgency=medium
|
|
|
|
* Pre-release v0.7.1.
|
|
- Listen wrapper now deduplicates on (server block, sockaddr)
|
|
across both plain and device-tagged listens. A plain
|
|
`listen 80;` and `listen 80 device=eth0 ...;` in the same
|
|
server block now coexist, matching the runtime reality under
|
|
the IP_PKTINFO attribution model (all same-sockaddr listens
|
|
collapse to one wildcard kernel socket). Docs updated to
|
|
drop the "must be device-tagged" restriction.
|
|
|
|
-- Pim van Pelt <pim@ipng.ch> Sun, 19 Apr 2026 10:00:00 +0200
|
|
|
|
nginx-ipng-stats-plugin (0.7.0-1) unstable; urgency=medium
|
|
|
|
* Pre-release v0.7.0.
|
|
- New ipng_stats_rescan_interval directive (default 60s, 0 to
|
|
disable). Per-worker timer that re-resolves every device= →
|
|
ifindex mapping, self-healing attribution after interface
|
|
teardown/recreate without requiring nginx -s reload.
|
|
- New nginx_ipng_ifindex_misses_total counter: connections whose
|
|
ingress ifindex didn't match any configured binding. Surfaces
|
|
stale mappings and genuinely-unconfigured interfaces.
|
|
- Expose the existing nginx_ipng_zone_full_events_total and
|
|
nginx_ipng_flushes_total meta counters in both the Prometheus
|
|
and JSON scrape outputs. JSON gains a top-level "meta" object
|
|
alongside "records" (schema unchanged, additive).
|
|
|
|
-- Pim van Pelt <pim@ipng.ch> Sat, 18 Apr 2026 19:36:36 +0200
|
|
|
|
nginx-ipng-stats-plugin (0.6.0-1) unstable; urgency=medium
|
|
|
|
* Pre-release v0.6.0.
|
|
|
|
-- Pim van Pelt <pim@ipng.ch> Sat, 18 Apr 2026 15:30:40 +0200
|
|
|
|
nginx-ipng-stats-plugin (0.5.0-1) unstable; urgency=medium
|
|
|
|
* Pre-release v0.5.0.
|
|
|
|
-- Pim van Pelt <pim@ipng.ch> Sat, 18 Apr 2026 14:38:25 +0200
|
|
|
|
nginx-ipng-stats-plugin (0.4.0-1) unstable; urgency=medium
|
|
|
|
* Pre-release v0.4.0.
|
|
|
|
-- Pim van Pelt <pim@ipng.ch> Sat, 18 Apr 2026 13:15:15 +0200
|
|
|
|
nginx-ipng-stats-plugin (0.3.0-1) unstable; urgency=medium
|
|
|
|
* Pre-release v0.3.0.
|
|
|
|
-- Pim van Pelt <pim@ipng.ch> Sat, 18 Apr 2026 11:47:26 +0200
|
|
|
|
nginx-ipng-stats-plugin (0.2.0-1) unstable; urgency=medium
|
|
|
|
* Reduce scrape cardinality.
|
|
- Status codes are collapsed to six class lanes
|
|
(1xx/2xx/3xx/4xx/5xx/unknown) on the counter key. Per-(source, vip)
|
|
counter cardinality is now bounded at six regardless of response mix.
|
|
- Histograms drop the code label entirely and aggregate across classes
|
|
per (source, vip).
|
|
- New nginx_ipng_latency_total counter (with code class label) exposes
|
|
per-class mean latency via latency_total / requests_total.
|
|
- New nginx_ipng_bytes_in and nginx_ipng_bytes_out histograms; bucket
|
|
bounds configurable via the new ipng_stats_byte_buckets directive.
|
|
- JSON schema bumped to 2. Records are now per-(source, vip) with an
|
|
inner `classes` map.
|
|
- Operators needing per-three-digit-code breakdowns should consume
|
|
ipng_stats_logtail off-host; the stats zone intentionally trades
|
|
that resolution for a smaller, bounded scrape.
|
|
|
|
-- Pim van Pelt <pim@ipng.ch> Fri, 17 Apr 2026 12:36:57 +0000
|
|
|
|
nginx-ipng-stats-plugin (0.1.0-1) unstable; urgency=medium
|
|
|
|
* Initial release.
|
|
- ngx_http_ipng_stats_module: per-VIP, per-device HTTP traffic
|
|
counters, attributed via SO_BINDTODEVICE on per-interface
|
|
listening sockets, exposed as Prometheus text and JSON from a
|
|
single scrape endpoint.
|
|
- Debian package libnginx-mod-http-ipng-stats builds against the
|
|
target release's nginx-dev headers with --with-compat and loads
|
|
into stock upstream nginx without recompiling nginx itself.
|
|
|
|
-- Pim van Pelt <pim@ipng.ch> Thu, 16 Apr 2026 00:00:00 +0000
|