# Listener Integrations

## Overview

Although there is a fixed number of Listener types available, the integration possibilities are endless. Onum is designed to be source-agnostic, ensuring you can ingest data from virtually any product or technology.

We achieve this through a strategic, two-pillar approach to our Listeners:

* First, we offer a growing suite of **dedicated Listeners for specific technologies** (such as Amazon S3, Microsoft Office, and others). These provide a streamlined configuration process for popular services.
* Second, and crucially, we provide **standard protocol Listeners** (including HTTP, TCP, and Syslog). This ensures that even if a product does not have a dedicated, named Listener, you can still seamlessly send data to Onum using these widely supported, industry-standard protocols. 

This dual model guarantees comprehensive coverage, making it clear that whether you need a highly specialized integration or simply a robust, standardized connection, Onum is ready to collect your data.

You can [contact us to request a specific Listener type](/support/support.md).

## Dedicated Listeners

Check the current suite of dedicated Listeners we offer in the Onum platform:

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><a href="/pages/bEzNdDj7xRBdPocrD3pa">Amazon Kinesis Data Stream Listener</a></td><td>Ingest data streams from Amazon Kinesis</td><td><a href="/files/S1da6eoD5qqvQkP21CbU">/files/S1da6eoD5qqvQkP21CbU</a></td></tr><tr><td><a href="/pages/HpteGRheaXQoEmmCRUUm">Amazon S3 Listener</a></td><td>Receive data from your Amazon S3 buckets</td><td><a href="/files/wW73FuASiITHyIo7xmgb">/files/wW73FuASiITHyIo7xmgb</a></td></tr><tr><td><a href="/pages/La49UhwnRbZrsdbLfZbd">Amazon SQS Listener</a></td><td>Inject queue messages from Amazon SQS</td><td><a href="/files/56yJw8vC7Adh8Y5xx91F">/files/56yJw8vC7Adh8Y5xx91F</a></td></tr><tr><td><a href="/pages/ZYgd6pn9EdNb51LPJYXS">Azure Blob Storage Listener</a></td><td>Collect data from a container in Azure Blob Storage</td><td><a href="/files/TV4gsDXI6CQSBqgD8W1m">/files/TV4gsDXI6CQSBqgD8W1m</a></td></tr><tr><td><a href="/pages/oBmyqX6w4PStpDWp8OZ6">Apache Kafka Listener</a></td><td>Send data from your Apache Kafka clusters</td><td><a href="/files/GEkBUyz7STYUNziiK8fE">/files/GEkBUyz7STYUNziiK8fE</a></td></tr><tr><td><a href="/pages/7L8Ddq3rpX6KWwzChMCP">Azure Event Hubs Listener</a></td><td>Receive messages from a hub in Azure Event Hubs</td><td><a href="/files/Y3PbyxLwcz5WcczRsWdB">/files/Y3PbyxLwcz5WcczRsWdB</a></td></tr><tr><td><a href="/pages/polEUVXaI68GJiIttQOP">Falcon LogScale Collector Listener</a></td><td>Collect data from your Falcon LogScale Collector</td><td><a href="/files/VlUWoeJrz6j8AiFfhIMB">/files/VlUWoeJrz6j8AiFfhIMB</a></td></tr><tr><td><a href="/pages/eKEBFW0Ox8xJ1UYgsTAq">Google Cloud Storage Listener</a></td><td>Source data from a Google Cloud Storage bucket</td><td><a href="/files/8T1EM1PQszYZmaHWuo1D">/files/8T1EM1PQszYZmaHWuo1D</a></td></tr><tr><td><a href="/pages/b3ocDEioU0a5KVyv260x">Google Pub/Sub Listener</a></td><td>Stream data from your Google Pub/Sub subscriptions</td><td><a href="/files/qNgDLiJOtLbWkKGSiP5Z">/files/qNgDLiJOtLbWkKGSiP5Z</a></td></tr><tr><td><a href="/pages/XXVcVckxEerXauycFaIU">Microsoft 365 Listener</a></td><td>Send content from your Microsoft 365 products</td><td><a href="/files/xSN5NhCOzhWgOMDj8KGj">/files/xSN5NhCOzhWgOMDj8KGj</a></td></tr></tbody></table>

## Standard Protocol Listeners

Click to see how to configure each of our Listeners for standard protocols:

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><a href="/pages/z9UnPDZ5hcK8k5mCnoTS">Cisco NetFlow Listener</a></td><td>Listen for NetFlow packet records</td><td><a href="/files/hutRwyJri9hOeNbfZSZ8">/files/hutRwyJri9hOeNbfZSZ8</a></td></tr><tr><td><a href="/pages/bYe8dii2N7FlzyVDRGEr">HTTP Listener</a></td><td>Listen for HTTP requests</td><td><a href="/files/nKwyFKoHDkNi27jXBqjL">/files/nKwyFKoHDkNi27jXBqjL</a></td></tr><tr><td><a href="/pages/VjzHpXKPWB86bE028vTs">HTTP Pull Listener</a></td><td>Pull JSON data from HTTP endpoints</td><td><a href="/files/hutRwyJri9hOeNbfZSZ8">/files/hutRwyJri9hOeNbfZSZ8</a></td></tr><tr><td><a href="/pages/tWFHTOiNlJ1Re3x7dyvY">OpenTelemetry Listener</a></td><td>Process OpenTelemetry metrics, traces and logs</td><td><a href="/files/hutRwyJri9hOeNbfZSZ8">/files/hutRwyJri9hOeNbfZSZ8</a></td></tr><tr><td><a href="/pages/r68csbvPagM5bgFGuQZB">SNMP Trapd Listener</a></td><td>Receive SNMP traps from network devices</td><td><a href="/files/hutRwyJri9hOeNbfZSZ8">/files/hutRwyJri9hOeNbfZSZ8</a></td></tr><tr><td><a href="/pages/Ivxxpe9YxnRKxZQeYS6r">Syslog Listener</a></td><td>Process Syslog messages</td><td><a href="/files/nKwyFKoHDkNi27jXBqjL">/files/nKwyFKoHDkNi27jXBqjL</a></td></tr><tr><td><a href="/pages/AgkSpgmoO4qcQrvTuSFl">TCP Listener</a></td><td>Read data from a TCP stream of bytes</td><td><a href="/files/nKwyFKoHDkNi27jXBqjL">/files/nKwyFKoHDkNi27jXBqjL</a></td></tr></tbody></table>

## Other Listeners

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><a href="/pages/uBQTqwPlMdYSdWG5xjer">Relational Databases Listener</a></td><td>Read data from your databases</td><td><a href="/files/jxk2RxyJcyHOq5zzoQSi">/files/jxk2RxyJcyHOq5zzoQSi</a></td></tr><tr><td><a href="/pages/Y5V0l4FTaDfS55RxLREN">Tick Listener</a></td><td>Emit synthetic events on a defined schedule</td><td><a href="/files/HMhoAPmZ2oO3QHGSQxTz">/files/HMhoAPmZ2oO3QHGSQxTz</a></td></tr></tbody></table>


---

# 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/the-workspace/listeners/listener-integrations.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.