Syslog Data Sink
Most recent version: v3.0.0
Learn more about this Data sink type in this article.
v2.0.0
Released on 04/10/2025
- Full rework: split message creation and storage from delivering/flushing it. - Executegenerates the Syslog message and adds it to a- []bytebuffer.
- 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 - Executeto wait only for that much time before returning a- Recoverableerror.- There are no possible duplicated events due to this timeout since it only triggers when - Executeis trying to write data to the buffer, can't and request a blocking flush that takes too much (but may eventually complete anyway).
 
 
v1.3.0
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. 
Last updated
Was this helpful?

