Listener Integrations
Collect data in real-time, no matter the source
Overview
Although there are only a limited number of Listener types available for use in Onum, 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.
Dedicated Listeners
Check the current suite of dedicated Listeners we offer in the Onum platform:

Ingest data streams from Amazon Kinesis

Receive data from your Amazon S3 buckets

Inject queue messages from Amazon SQS

Send data from your Apache Kafka clusters

Receive messages from a hub in Azure Event Hubs

Collect data from your Falcon LogScale Collector

Source data from a Google Cloud Storage bucket

Stream data from your Google Pub/Sub subscriptions

Send content from your Microsoft 365 products
Standard Protocol Listeners
Click to see how to configure each of our Listeners for standard protocols:

Listen for NetFlow packet records

Listen for HTTP requests

Pull JSON data from HTTP endpoints

Process OpenTelemetry metrics, traces and logs

Receive SNMP traps from network devices

Process Syslog messages

Read data from a TCP stream of bytes
Other Listeners

Read data from your databases

Emit synthetic events on a defined schedule
Last updated
Was this helpful?

