Syslog

Most recent version: v2.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.

    • 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).

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.

v1.2.0

Released on 10/01/2024

  • Added new Write timeout (ms) configuration parameter.

v0.9.0

Released on 09/23/2024

  • Configuration page metadata expanded.

v0.8.0

Released on 08/13/2024

  • Compression enabled.

v0.7.1

Released on 08/12/2024

  • Added string to timestamp selection options.

v0.7.0

Released on 08/05/2024

  • Updated timestamp field valid types.

v0.3.0

Released on 05/06/2024

v0.2.0

Released on 04/28/2024

Bug fixes

v0.1.0

Released on 04/28/2024

Bug fixes

v0.0.1

Released on 04/28/2024

Initial version

Last updated

Was this helpful?