# Syslog Data Sink

Learn more about this Data sink type in [this article](/the-workspace/data-sinks/data-sink-integrations/send-data-using-syslog.md).

<details>

<summary>v3.0.1</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">02/23/2026</mark>

* We've fixed the deadline for when a connection closes or recycles. This can cause issues if the connection is sending data using GZIP compression.
* Resolved issues with the last flush time.

</details>

<details>

<summary>v3.0.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">10/03/2025</mark>

* The message/content on RFC5424 and RFC3164 is now required.

</details>

<details>

<summary>v2.0.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">04/10/2025</mark>

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

</details>

<details>

<summary>v1.3.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">02/10/2025</mark>

* 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.

</details>

<details>

<summary>v1.2.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">10/01/2024</mark>

* Added new **Write timeout (ms)** configuration parameter.

</details>

<details>

<summary>v0.9.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">09/23/2024</mark>

* Configuration page metadata expanded.

</details>

<details>

<summary>v0.8.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">08/13/2024</mark>

* Compression enabled.

</details>

<details>

<summary>v0.7.1</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">08/12/2024</mark>

* Added string to timestamp selection options.

</details>

<details>

<summary>v0.7.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">08/05/2024</mark>

* Updated timestamp field valid types.

</details>

<details>

<summary>v0.3.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">05/06/2024</mark>

Minor bug fixing

</details>

<details>

<summary>v0.2.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">04/28/2024</mark>

Minor bug fixing

</details>

<details>

<summary>v0.1.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">04/28/2024</mark>

Minor bug fixing

</details>

<details>

<summary>v0.0.1</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">04/28/2024</mark>

Initial version

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.onum.com/data-sinks/syslog-data-sink.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.