Skip to content

fix(compose): publish syslog and flow listeners through port keys - #400

Merged
catinspace-au merged 2 commits into
mainfrom
fix/receiver-udp-ports
Nov 15, 2026
Merged

catinspace-au merged 2 commits into
mainfrom
fix/receiver-udp-ports

Conversation

@catinspace-au

Copy link
Copy Markdown
Contributor

A Docker install could not take syslog or flow from outside the Compose network because the receiver published only 8080 and 9090.

Six port keys publish syslog over UDP, TCP and TLS, and NetFlow, IPFIX and sFlow over UDP. They use the same make fragment as the Beats and HEC keys. Each port stays unpublished until its key is set.

The configuration doc lists the receiver settings that enable the listeners. It also states that rootless Docker cannot bind a host port under 1024.

A Docker install could not take syslog or flow from outside the Compose network because the receiver published only 8080 and 9090.

Six port keys publish syslog over UDP, TCP and TLS, and NetFlow, IPFIX and sFlow over UDP. They use the same make fragment as the Beats and HEC keys. Each port stays unpublished until its key is set.

The configuration doc lists the receiver settings that enable the listeners. It also states that rootless Docker cannot bind a host port under 1024.
When syslog is enabled, its UDP and plain TCP listeners always bind. The receiver refuses syslog without accept_unauthenticated, even when only the TLS port is published. The architecture page's receiver row now lists syslog and flow among the listeners a port key publishes.
@catinspace-au
catinspace-au merged commit 0339b29 into main Nov 15, 2026
16 checks passed
@catinspace-au
catinspace-au deleted the fix/receiver-udp-ports branch November 15, 2026 17:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant