Syslog
Most recent version: v2.0.0
Last updated
Was this helpful?
Most recent version: v2.0.0
Last updated
Was this helpful?
Learn more about this Data sink type in .
Released on 04/10/2025
Full rework: split message creation and storage from delivering/flushing it.
Execute generates the Syslog message and adds it to a []byte buffer.
The goroutine has a ticker that flushes the buffer in a non-blocking way when the amount of data written reaches a threshold.
The buffer is also flushed in a blocking way when Execute() cannot store the event because the buffer is full or when Beep() ticks.
There is a new Delivery Timeout parameter that allows the Execute to wait only for that much time before returning a Recoverable error.
There are no possible duplicated events due to this timeout since it only triggers when Execute is trying to write data to the buffer, can't and request a blocking flush that takes too much (but may eventually complete anyway).
Released on 02/10/2025
New configuration parameter Time To Live for the connections to recycle them after it passes.
New configuration parameter Idle timeout.
New configuration parameter Dial timeout.
New configuration parameter Test mode/dry run. When true, messages will be built and processed but not sent to the destination.
Fixed TLS connection not using the dial timeout.