# Syslog Listener

Learn more about this Listener type in [this article](/the-workspace/listeners/listener-integrations/collect-data-using-syslog.md).

<details>

<summary>v1.1.2</summary>

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

Solved panic throwing with malformed Syslog messages. Improperly formatted Syslog messages previously caused the application to crash, whereas now it will properly validate and safely processe malformed Syslog data.

</details>

<details>

<summary>v1.1.1</summary>

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

Fixed a serialization problem with the IP of UDP messages.

</details>

<details>

<summary>v1.0.2</summary>

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

* The `sourceIp` and `sourcePort` fields are unmarshaled correctly now. This fix resolves an issue where the system previously failed to properly extract or convert the sourceIp and sourcePort fields during data parsing (unmarshaling). Now, these network identifier fields are correctly interpreted from their serialized format into their proper data types and structures, ensuring accurate representation of connection origins.
* IP is now sent as a string to speed up marshaling/unmarshaling.&#x20;

</details>

<details>

<summary>v1.0.1</summary>

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

RFC5424 events with missing messages are unmarshaled correctly now. This fix addresses a parsing issue with RFC5424-formatted syslog events that lack message content. With this update, the unmarshaling process now correctly handles these edge cases, ensuring that valid syslog events are properly processed even when they contain only metadata without an actual message payload.&#x20;

</details>

<details>

<summary>v1.0.0</summary>

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

TLS metadata has been changed in order to use secrets.

</details>

<details>

<summary>v0.1.1</summary>

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

* Prioritized NTF when auto-detecting framing method. Onum now prioritizes Network Transmission Format (NTF) when identifying message framing methods in data streams. The hexadecimal delimiter `0C` (form feed character) will only be recognized as a frame boundary when it's immediately followed by whitespace.
* Added support for RFC3164 tag options, considering them part of the tag itself.
* The proceed reported between square brackets and immediately following the tag under RFC3164 is no longer mandatory.

</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;">07/09/2024</mark>

`address` has been removed from metadata parameters and now uses `0.0.0.0` by default.

</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;">02/22/2023</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/listeners/syslog-listener.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.