imptcp: Plain TCP Syslog — rsyslog 8.24.0 documentation

# imptcp: Plain TCP Syslog

Provides the ability to receive syslog messages via plain TCP syslog. This is a specialised input plugin tailored for high performance on Linux. It will probably not run on any other platform. Also, it does not provide TLS services. Encryption can be provided by using stunnel.

This module has no limit on the number of listeners and sessions that can be used.

Author: Rainer Gerhards <rgerhards@adiscon.com>

## Configuration Directives

This plugin has config directives similar named as imtcp, but they all have PTCP in their name instead of just TCP. Note that only a subset of the parameters are supported.

### Module Parameters

These parameters can be used with the “module()” statement. They apply globaly to all inputs defined by the module.

`Threads <number>`

  Number of helper worker threads to process incoming messages. These threads are utilized to pull data off the network. On a busy system, additional helper threads (but not more than there are CPUs/Cores) can help improving performance. The default value is two, which means there is a default thread count of three (the main input thread plus two helpers). No more than 16 threads can be set (if tried to, rsyslog always resorts to 16).

`processOnPoller on/off`

  Defaults to on

  Instructs imptcp to process messages on poller thread opportunistically. This leads to lower resource footprint(as poller thread doubles up as message-processing thread too). “On” works best when imptcp is handling low ingestion rates.

  At high throughput though, it causes polling delay(as poller spends time processing messages, which keeps connections in read-ready state longer than they need to be, filling socket-buffer, hence eventually applying backpressure).

  It defaults to allowing messages to be processed on poller (for backward compatibility).

### Input Parameters

These parameters can be used with the “input()” statement. They apply to the input they are specified with.

`port <number>`

  Mandatory

  Select a port to listen on. It is an error to specify both path and port.

`path <name>`

  A path on the filesystem for a unix domain socket. It is an error to specify both path and port.

`unlink on/off`

  Default: off

  If a unix domain socket is being used this controls whether or not the socket is unlinked before listening and after closing.

`name <name>`

  Sets a name for the inputname property. If no name is set “imptcp” is used by default. Setting a name is not strictly necessary, but can be useful to apply filtering based on which input the message was received from. Note that the name also shows up in impstats logs.

`ruleset <name>`

  Binds specified ruleset to this input. If not set, the default ruleset is bound.

`address <name>`

  Default: all interfaces

  On multi-homed machines, specifies to which local address the listerner should be bound.

`AddtlFrameDelimiter <Delimiter>`

  This directive permits to specify an additional frame delimiter for plain tcp syslog. The industry-standard specifies using the LF character as frame delimiter. Some vendors, notable Juniper in their NetScreen products, use an invalid frame delimiter, in Juniper’s case the NUL character. This directive permits to specify the ASCII value of the delimiter in question. Please note that this does not guarantee that all wrong implementations can be cured with this directive. It is not even a sure fix with all versions of NetScreen, as I suggest the NUL character is the effect of a (common) coding error and thus will probably go away at some time in the future. But for the time being, the value 0 can probably be used to make rsyslog handle NetScreen’s invalid syslog/tcp framing. For additional information, see this forum thread. If this doesn’t work for you, please do not blame the rsyslog team. Instead file a bug report with Juniper!

  Note that a similar, but worse, issue exists with Cisco’s IOS implementation. They do not use any framing at all. This is confirmed from Cisco’s side, but there seems to be very limited interest in fixing this issue. This directive can not fix the Cisco bug. That would require much more code changes, which I was unable to do so far. Full details can be found at the Cisco tcp syslog anomaly page.

`SupportOctetCountedFraming on/off`

  Defaults to “on”

  The legacy octed-counted framing (similar to RFC5425 framing) is activated. This is the default and should be left unchanged until you know very well what you do. It may be useful to turn it off, if you know this framing is not used and some senders emit multi-line messages into the message stream.

`NotifyOnConnectionClose on/off`

  Defaults to off

  instructs imptcp to emit a message if a remote peer closes the connection.

`KeepAlive on/off`

  Defaults to off

  enable of disable keep-alive packets at the tcp socket layer. The default is to disable them.

`KeepAlive.Probes <number>`

  The number of unacknowledged probes to send before considering the connection dead and notifying the application layer. The default, 0, means that the operating system defaults are used. This has only effect if keep-alive is enabled. The functionality may not be available on all platforms.

`KeepAlive.Interval <number>`

  The interval between subsequential keepalive probes, regardless of what the connection has exchanged in the meantime. The default, 0, means that the operating system defaults are used. This has only effect if keep-alive is enabled. The functionality may not be available on all platforms.

`KeepAlive.Time <number>`

  The interval between the last data packet sent (simple ACKs are not considered data) and the first keepalive probe; after the connection is marked to need keepalive, this counter is not used any further. The default, 0, means that the operating system defaults are used. This has only effect if keep-alive is enabled. The functionality may not be available on all platforms.

`RateLimit.Interval [number]`

  Default is 0, which turns off rate limiting

  Specifies the rate-limiting interval in seconds. Set it to a number of seconds (5 recommended) to activate rate-limiting.

`RateLimit.Burst [number]`

  Default is 10,000

  Specifies the rate-limiting burst in number of messages.

`compression.mode [mode]`

  Default is none

  This is the counterpart to the compression modes set in omfwd. Please see it’s documentation for details.

## Caveats/Known Bugs

- module always binds to all interfaces

## Example

This sets up a TCP server on port 514:

    module(load="imptcp") # needs to be done just once
    input(type="imptcp" port="514")

This creates a listener that listens on the local loopback interface, only.

    module(load="imptcp") # needs to be done just once
    input(type="imptcp" port="514" address="127.0.0.1")

Create a unix domain socket:

    module(load="imptcp") # needs to be done just once
    input(type="imptcp" path="/tmp/unix.sock" unlink="on")

## Legacy Configuration Directives

`$InputPTCPServerAddtlFrameDelimiter <Delimiter>`

  Equivalent to: AddTLFrameDelimiter

`$InputPTCPSupportOctetCountedFraming on/off`

  Equivalent to: SupportOctetCountedFraming

`$InputPTCPServerNotifyOnConnectionClose on/off`

  Equivalent to: NotifyOnConnectionClose.

`$InputPTCPServerKeepAlive <on/**off**>`

  Equivalent to: KeepAlive

`$InputPTCPServerKeepAlive_probes <number>`

  Equivalent to: KeepAlive.Probes

`$InputPTCPServerKeepAlive_intvl <number>`

  Equivalent to: KeepAlive.Interval

`$InputPTCPServerKeepAlive_time <number>`

  Equivalent to: KeepAlive.Time

`$InputPTCPServerRun <port>`

  Equivalent to: Port

`$InputPTCPServerInputName <name>`

  Equivalent to: Name

`$InputPTCPServerBindRuleset <name>`

  Equivalent to: Ruleset

`$InputPTCPServerHelperThreads <number>`

  Equivalent to: threads

`$InputPTCPServerListenIP <name>`

  Equivalent to: Address

## Caveats/Known Bugs

- module always binds to all interfaces

## Example

This sets up a TCP server on port 514:

    $ModLoad imptcp # needs to be done just once
    $InputPTCPServerRun 514