Architecture
Designed for the Edge, created in the Cloud
Last updated
Was this helpful?
Designed for the Edge, created in the Cloud
Last updated
Was this helpful?
Easy, flexible deployment in any environment while keeping them as close as possible to where the data is produced delivers unparalleled speed and efficiency, enabling you to cut the infrastructure you have dedicated to orchestration by up to 80%.
The Onum infrastructure consists of:
Distributor: this is the service that hosts the Listener before forwarding it to Workers.
Worker: this is the service that runs the Pipelines, receiving data from its Distributor and contained within a Cluster.
Cluster: a container grouping Distributors and Workers. You can have as many clusters as required per Tenant.
Listeners are hosted within Distributors and are placed as close as possible to where data is generated. The Distributor pulls tasks from the data queue passing through the pipeline and distributes it to the next available worker in a Cluster. As soon as a Worker completes a task it becomes available again, and the Distributor in turn will assign it the next task from the queue.
The installation process creates the Distributor and all Workers for each data source in the cluster.
The Onum Platform supports any deployment type ― including on-premises
, the Onum public cloud, or your own private cloud
.
In a typical SaaS-based deployment, most processing activities are conducted in the Cloud.
Client-side components can be deployed on a Linux machine or on a Kubernetes cluster for easy, flexible deployment in any environment. Onum supports all major cloud environments, including Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure.
Learn more about Deployment requirements here.
Onum supports all major standards such as Netflow, Syslog, and Kafka to orchestrate data streams to any desired destination, including popular data analytics tools such as Splunk and Devo, as well as storage environments such as S3.
Any format. Any source.
Collect data from anywhere it’s generated, across every aspect of the network.
All data is aggregated, observed, and seamlessly routed to any destination.
Edge observability
Listeners are placed right on the edge to collect all data as close as possible to where it’s generated.
Centralized management
Onum receives data from Listeners and observes and optimizes the data from all nodes. All data is then sent to the proper data sink.