ipng/nginx-ipng-stats-plugin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

PRE-RELEASE v0.6.0

Browse Source 
Describe the ipng_stats_logtail UDP feature in debian/control alongside
the per-VIP / per-device counter description, so the package metadata
reflects what the module actually ships.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Pim van Pelt
2026-04-18 15:31:31 +02:00
parent 055cf9f830
commit 59f3deef66
3 changed files with 17 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Makefile
View File

@@ -23,7 +23,7 @@ BUILD_DIR := $(CURDIR)/build
# the package version from there directly. The C code picks up VERSION # the package version from there directly. The C code picks up VERSION
# via the generated src/version.h (written by the version-header target # via the generated src/version.h (written by the version-header target
# below and depended on by the module build). # below and depended on by the module build).
VERSION := 0.5.0 VERSION := 0.6.0
NGINX_SRC ?= NGINX_SRC ?=

6
debian/changelog vendored
View File

@@ -1,3 +1,9 @@
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 nginx-ipng-stats-plugin (0.5.0-1) unstable; urgency=medium
* Pre-release v0.5.0. * Pre-release v0.5.0.

10
debian/control vendored
View File

@@ -34,6 +34,16 @@ Description: nginx dynamic module for per-VIP, per-device traffic counters
device= and ipng_source_tag= parameters to the nginx listen device= and ipng_source_tag= parameters to the nginx listen
directive, mapping interface names to source tags. directive, mapping interface names to source tags.
. .
The module also provides an ipng_stats_logtail http-level directive
that ships every request as a UDP datagram to a collector, using a
named nginx log_format (so $ipng_source_tag and $server_addr are
available alongside the standard access-log variables). Each worker
holds a private in-memory buffer flushed on size or timer, over a
per-worker SOCK_DGRAM socket resolved once at configuration time.
Delivery is fire-and-forget — zero disk I/O, no backpressure — and
an if=$variable parameter suppresses selected requests (e.g. health
checks) before the format is rendered.
.
Typical use cases include GRE tunnel fleets, VLAN trunks, or any Typical use cases include GRE tunnel fleets, VLAN trunks, or any
deployment where traffic arrives on distinct interfaces and deployment where traffic arrives on distinct interfaces and
per-interface observability is needed. per-interface observability is needed.