# TCP Listener

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

<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;">04/28/2025</mark>

`SourceIp` was not properly displayed in the user interface despite being failing to properly render it in the front-end interface. With this fix, you can now accurately view the true network origin of TCP-transmitted data.

</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/11/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;">07/08/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/listeners/tcp-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.