-
v0.1.17
StableAll checks were successfulci / go-test (push) Successful in 4m39sci / release-smoke (push) Successful in 4m43sci / integration (push) Successful in 4m36sci / parser-fixtures (push) Successful in 4m35srelease / metadata (push) Successful in 3srelease / build-artifacts (push) Successful in 5m3srelease / publish (push) Successful in 1m6sreleased this
2026-07-22 11:11:10 +02:00 | 0 commits to main since this releasev0.1.17 - 2026-07-22
Fixed
- Scoped NetFlow v9 and IPFIX templates by exporter UDP source port together
with the source/observation domain, preventing template state from crossing
exporter transport contexts. - Kept NetFlow v9 and IPFIX Options records metadata-only so scopes, exporter
addresses, application metadata, and option values cannot create false flow
byte, packet, address, port, sampling, or timestamp fields. - Preserved the explicit NetFlow v9 scope namespace
netflow.v9.scope.<scope-type>and kept scope fields out of ordinary
Information Element normalization. - Prevented enterprise IPFIX Information Elements from inheriting IANA aliases
solely because their numeric IDs match. - Removed proven false aliases where flow totals, exported counters, sampler
identifiers/modes, interfaces, timestamps, VLAN identifiers, or TCP fields
were promoted to unrelated canonical fields. - Added standards-compliant one-to-eight-byte IPFIX reduced-size integer
decoding, signed sign extension, fixed-zero-length template rejection, and
millisecond timestamp overflow protection. - Changed sFlow exporter identity to the datagram
agent_addressand sub-agent
context instead of the UDP relay address. - Restricted sFlow sampled-header tuple decoding to the declared Ethernet,
IPv4, or IPv6 header protocol and rejected invalid protocol/port promotion.
Compatibility
- Existing legitimate NetFlow v5, NetFlow v9, and IPFIX byte/packet decoding
remains unchanged. - NetFlow v9 application metadata remains available while Options records stay
outside traffic normalization. - sFlow sampling remains applied exactly once.
- The canonical audit, fixtures, pre/post evidence, runtime queries, and audit
matrix are recorded at
docs/audits/flowcollector-go/wire-to-canonical-conformance-20260722.mdin
the governed platform documentation tree.
Known limitations
- Some Cisco NetFlow v5 wire semantics, PEN 4300 aliases, NetFlow v9 vendor
extensions, and later sFlow extensions remainREFERENCE_MISSING. - NetFlow v9 Count, padding, packet-sequence, and non-standard withdrawal
behavior remains incomplete. - IPFIX UDP template lifecycle and NTP fractional timestamp behavior remains
incomplete. - sFlow counter samples are parsed but not runtime-dispatched; some interface
formats and extended records remain unsupported or unproven.
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
- Scoped NetFlow v9 and IPFIX templates by exporter UDP source port together
-
v0.1.16
StableAll checks were successfulci / go-test (push) Successful in 5m52sci / release-smoke (push) Successful in 5m59sci / integration (push) Successful in 5m49sci / parser-fixtures (push) Successful in 5m44srelease / metadata (push) Successful in 3srelease / build-artifacts (push) Successful in 7m1srelease / publish (push) Successful in 1m37sreleased this
2026-07-20 14:41:57 +02:00 | 3 commits to main since this releasev0.1.16 - 2026-07-20
Fixed
- Added deterministic
flow.in.netif.nameandflow.out.netif.namefallback
values formatted asindex: <id>whenever a valid non-zero numeric interface
index is present without an exported name. - Preserved exporter-provided friendly interface names and the existing
exporter-scoped SNMP behavior that replaces only matching numeric fallback
names with real interface metadata. - Applied the central interface-name fallback consistently to NetFlow v5,
NetFlow v9, IPFIX, and sFlow v5 events without changing the numeric interface
fields.
Compatibility
- Retained the proven directional VLAN fields
flow.in.vlan.tag.idand
flow.out.vlan.tag.id. - Did not add an unproven
vlan.tag.idalias. tcp.options.tagsremains unsupported pending parity evidence for the exact
VictoriaFlow bit ordering and canonical tag names; TCP flags are not used as
a substitute.
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
- Added deterministic
-
v0.1.15
StableAll checks were successfulci / go-test (push) Successful in 4m49sci / release-smoke (push) Successful in 4m41sci / integration (push) Successful in 4m34sci / parser-fixtures (push) Successful in 4m34srelease / metadata (push) Successful in 3srelease / build-artifacts (push) Successful in 5m13srelease / publish (push) Successful in 1m10sreleased this
2026-07-13 08:13:45 +02:00 | 5 commits to main since this releasev0.1.15 - 2026-07-13
Changed
- Made external
hosts.csvthe authoritative first hostname source for DNS
enrichment. - Changed DNS resolution order to
hosts.csv, positive cache, negative cache,
optional private PTR skip, and PTR lookup for remaining addresses. - Added canonical
ip,hostnameheader support while preserving comment-based
hosts files. - Documented
hosts.csvplusskip_private_ptr=trueas the recommended
production private-network deployment model. - Runtime validated using the dedicated
/opt/containers/flowcollector-gotest
deployment.
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
2 downloads
- Made external
-
v0.1.14
StableSome checks failedci / go-test (push) Successful in 4m36sci / release-smoke (push) Successful in 4m43sci / integration (push) Successful in 4m33sci / parser-fixtures (push) Successful in 4m32srelease / metadata (push) Successful in 3srelease / build-artifacts (push) Successful in 5m2srelease / publish (push) Failing after 1sreleased this
2026-07-12 17:34:38 +02:00 | 7 commits to main since this releasev0.1.14 - 2026-07-12
Fixed
- Hardened DNS enrichment caching and lookup behavior:
- added bounded positive and negative DNS caches
- added configurable negative-cache TTL and private PTR lookup control
- retained DNS enrichment compatibility fields while reducing repeated resolver pressure
- runtime validated using the dedicated
/opt/containers/flowcollector-gotest deployment
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
1 download
- Hardened DNS enrichment caching and lookup behavior:
-
v0.1.13
StableAll checks were successfulci / go-test (push) Successful in 4m39sci / release-smoke (push) Successful in 4m42sci / integration (push) Successful in 4m34sci / parser-fixtures (push) Successful in 4m33srelease / metadata (push) Successful in 3srelease / build-artifacts (push) Successful in 5m4srelease / publish (push) Successful in 1m16sreleased this
2026-07-09 11:07:48 +02:00 | 9 commits to main since this releasev0.1.13 - 2026-07-09
Fixed
- Fixed the GeoIP/CIDR enrichment interaction:
- GeoIP enrichment now operates independently of the CIDR plugin
- CIDR metadata no longer suppresses MaxMind GeoIP lookups
- CIDR-derived site metadata uses dedicated
flow.src.site.*/flow.dst.site.*fields - existing GeoIP compatibility fields remain fully functional
- runtime validated using the dedicated
/opt/containers/flowcollector-gotest deployment
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
1 download
- Fixed the GeoIP/CIDR enrichment interaction:
-
v0.1.12
StableAll checks were successfulci / go-test (push) Successful in 1m22sci / release-smoke (push) Successful in 5m50sci / integration (push) Successful in 4m23sci / parser-fixtures (push) Successful in 4m17srelease / metadata (push) Successful in 3srelease / build-artifacts (push) Successful in 5m18srelease / publish (push) Successful in 1m16sreleased this
2026-07-09 09:50:00 +02:00 | 11 commits to main since this releasev0.1.12 - 2026-07-09
Changed
- Separated CIDR site metadata from GeoIP enrichment:
- CIDR location metadata now writes to
flow.src.site.*/flow.dst.site.* - CIDR enrichment no longer writes
source.geo.*,destination.geo.*,flow.src.geo.*, orflow.dst.geo.* source.geo.*,destination.geo.*,client.geo.*, andserver.geo.*remain GeoIP/MaxMind-owned- legacy CIDR metadata
geo.*input keys are still accepted and mapped into the new site namespace
- CIDR location metadata now writes to
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
1 download
- Separated CIDR site metadata from GeoIP enrichment:
-
v0.1.11
StableAll checks were successfulci / go-test (push) Successful in 4m44sci / release-smoke (push) Successful in 4m51sci / integration (push) Successful in 4m41sci / parser-fixtures (push) Successful in 4m43srelease / metadata (push) Successful in 3srelease / build-artifacts (push) Successful in 5m13srelease / publish (push) Successful in 1m15sreleased this
2026-07-07 21:19:35 +02:00 | 12 commits to main since this releasev0.1.11 - 2026-07-07
Added
- Added optional external CSV-based
app.categoryfallback. - Existing
app_ports.csvremains fully backward compatible. - Registry/IPFIX/NBAR application categories always take precedence.
- Port-derived categories are only applied when
app.categoryis empty. - Protocol-specific mappings have precedence over protocol-agnostic mappings.
- Existing
app.name,flow.app.name, normalization, parser logic, GeoIP/ASN enrichment and compatibility fields remain unchanged.
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
2 downloads
- Added optional external CSV-based
-
v0.1.10
StableAll checks were successfulci / go-test (push) Successful in 4m35sci / release-smoke (push) Successful in 5m23sci / integration (push) Successful in 4m34sci / parser-fixtures (push) Successful in 4m32srelease / metadata (push) Successful in 3srelease / build-artifacts (push) Successful in 5m25srelease / publish (push) Successful in 1m48sreleased this
2026-07-07 09:22:27 +02:00 | 14 commits to main since this releasev0.1.10 - 2026-07-07
Added
- Added ElastiFlow compatibility field
l4.session.establishedfor migrated GeoIP dashboards. - Field is emitted only when session state can be determined from existing flow information.
- No guessed session state is emitted.
- Existing ECS behavior is unchanged.
- No additional enrichment or parser changes beyond the compatibility field.
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
2 downloads
- Added ElastiFlow compatibility field
-
v0.1.9
StableSome checks failedci / go-test (push) Successful in 4m35sci / release-smoke (push) Successful in 5m20sci / integration (push) Successful in 5m22sci / parser-fixtures (push) Successful in 5m20srelease / metadata (push) Successful in 3srelease / build-artifacts (push) Successful in 5m8srelease / publish (push) Failing after 1m26sreleased this
2026-07-07 07:57:55 +02:00 | 17 commits to main since this releasev0.1.9 - 2026-07-07
Added
- Added ElastiFlow client/server GeoIP and ASN compatibility fields:
flow.client.geo.*now mirrorsclient.geo.*flow.server.geo.*now mirrorsserver.geo.*flow.client.as.*now mirrorsclient.as.*flow.server.as.*now mirrorsserver.as.*flow.client.geo.loc.coordandflow.server.geo.loc.coorduse the existing"lat,lon"compatibility format- no additional GeoIP or ASN lookups are performed
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
1 download
- Added ElastiFlow client/server GeoIP and ASN compatibility fields:
-
v0.1.8
StableAll checks were successfulci / go-test (push) Successful in 4m42sci / release-smoke (push) Successful in 4m37sci / integration (push) Successful in 4m30sci / parser-fixtures (push) Successful in 4m30srelease / metadata (push) Successful in 3srelease / build-artifacts (push) Successful in 4m57srelease / publish (push) Successful in 1m28sreleased this
2026-07-06 21:51:15 +02:00 | 18 commits to main since this releaseDownloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
3 downloads
-
Source code (ZIP)