These articles contain information on functionalities across the entire platform.

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.

How it works

Deployment types

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.

Delivery methods

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.

Overview

The exponential growth of data ingestion volumes can lead to reduced performance, slow response times, and increased costs. With this comes the need to implement optimization strategies & volume reduction control. We help you cut the noise of large data streams and reduce infrastructure by up to 80%.

Gain deep insights from any type of data, using any format, from any source.

All of this...

@ the Edge

By collecting and observing that data at the edge, as close as possible to where it’s being generated, gain real-time observations and take decisive action to prevent network downtime, payment system failures, malware infections, and more.

Unlike most tools that provide data observation and orchestration, Onum is not a data analytics space, which is already served well by security information and event management (SIEM) vendors and other analytics tools. Instead, Onum sits as close as possible to where the data is generated, and well in front of your analytics platforms, to collect and observe data across every aspect of your hybrid network.

Start with the basics

Quick Links

Most popular

Welcome to Onum! This guide will help you start working with Onum, a powerful tool designed to enhance your data analysis and processing capabilities.

Accessing Onum

A Tenant is a domain that contains a set of data in your organization. You can use one or various Tenants and grant access to as many as required.

Navigating the Interface

You can access the rest of the areas in Onum using the left panel.

Create Your First Listener

Onum receives any data through Listeners.

These are logical entities created within a Distributor, acting as the gateway to the Onum system. Configuring a Listener involves defining an IP address, a listening port, and a transport layer protocol, along with additional settings depending on the type of Listener specialized in the data it will receive.

Create Your First Data Sink

Onum outputs data via Data sinks. Use them to define where and how to forward the results of your streamlined data.

Build Your First Pipeline

Use Pipelines to start transforming your data and build a data flow. Pipelines are made of the following components:

Use cases

Do you want to check the essential steps in Onum through specific Pipelines? Explore the most common use cases in this section.

Overview

This article outlines the more complex calculations that go on behind the graphs you see.

The line graph represents the events in/out, and the bar graph represents bytes in/on. Hover over a point on the chart to show a tooltip containing the events and bytes in for the selected time, as well as a percentage of how much increase/decrease has occurred since the previous lapse of time since the one currently selected.

Events

The values on the left-hand side represent the events in/out for the selected period.

Bytes

The values on the right-hand side represent the bytes in/out for the selected period.

Overview

In both views, you can:

• Click the magnifying glass icon to look for specific elements in the list. You can search by name, status, or tag.

• Display all the elements individually in a list or grouped by Status or Type. These grouping options vary depending on the area you are.

Table View

In the Table view, you can click the cog icon to begin customizing the table settings. You can reorder the columns in the table, hide or display the required ones or pin them.

Changes will be automatically applied. Click the Reset button to recover the original configuration.

• Use the buttons at the top right part of the table to expand or collapse each row in the table. This will change the level of detail of each element.

• Click the ellipsis button on each row to edit the element, copy its ID, or remove it.

Cards View

In this view, each element is displayed as a card that shows details about it.

• Click the ellipsis button on each card to edit the element, copy its ID, or remove it.

• Click the Add tag button and add the required tags to an element. For each tag you enter in the box, hit the Enter key. Click Save to add the tags.

Overview

Throughout the entire Onum platform, you can set a period to either narrow down or extend the data shown. You can either select a predefined period or apply a custom time range.

The related graph and resources will be automatically updated to display data from the chosen period. To remove a selected period, simply click the bin icon that appears next to the period to go back to the default time range (1 hour ago).

Predefined and Custom time ranges

As well as predefined time intervals, you can also define a custom time range. To do it, simply select the required starting and ending dates in the calendar.

Comparisons

The interesting thing about Onum is that you can directly see how much volume you have saved compared to past ingestions, telling you what is going well and what requires further streamlining.

The comparison is direct/equivalent, meaning all data shown is analyzed compared to the previously selected equivalent time range.

For example, if the time range is 1 hour, the calculation of differences will be carried out using the previous one hour before the current selection =

• Range selected: 10:00-11:00

• Comparison: 09:00-10:00

Again, let´s say you now wish to view data over the last 7 days. The percentages will be calculated by measuring the volume retrospectively two weeks ago with the previous week.

Since Onum can process any data type, you may be wondering how to identify which is which. See the color legend below:

Overview

If your Onum installation is deployed in our Cloud, the configuration settings of a Listener would be slightly different from Listeners defined in an On-Premise deployment:

• Cloud Listeners do not have the TLS configuration settings in their creation form, as the connection is already secured.

• Cloud Listeners have an additional step in their creation process: Network configuration. Use these details to configure your data source to communicate with Onum. Click Download certificate to get the required certificate for the connection. You can also download it from the Listener details once it is created.

Important Considerations

You must consider the following indications before using Cloud Listeners:

• Cloud Listener endpoints are created in Onum's DNS. This process is usually fast and Listeners are normally available immediately. However, note that this may last up to 24-48 hours depending on your organization's DNS configuration.

• Cloud Listener endpoints require Mutual TLS (mTLS) authentication, which means that your data input must be able to process a TLS connection and be authorized with a certificate.

• Your data input must use the Server Name Indication (SNI) method, which means it must send its hostname in the TLS authentication process. If SNI is not used, the certificate routing will fail and data will not be received, even if the given certificate is valid.

If your organization software cannot meet points 2 and 3, you can use an intermediate piece of software to ensure the client-Onum connection, such as Stunnel.

In order to use Onum, there are certain system requirements.

The installation process creates the Distributor and all Workers for each data source in the cluster.

System requirements

Onum supports the following browsers:

• Google Chrome

Once you have acquired an Onum account, there are a few steps required for Onum Installation:

Cloud

Onum’s Operations team will prepare the infrastructure on Onum’s SaaS based on the estimated volumetrics.

On-Premise

• The infrastructure requirements are shared with the Operations team of the client. Further steps cannot be conducted without the required infrastructure.

• Access to the infrastructure is granted to Onum’s team with the right permissions for conducting the installation.

• A validation script is run by Onum in order to assess if all requirements described in the Annex are met and all connectivities are opened.

• If the above point is successful, an installation slot is scheduled and agreed.

• Installation is conducted by Onum engineers using a Docker and a post-installation validation script is run.

You can now access its tenant, ingest data, invite users and use all of the Onum capabilities.

Hardware requirements

Hardware (per Virtual Machine):

• Distribution: Linux (Debian or Red Hat)

• Server Hardware: 16GB RAM and 8 CPU

• Disk Storage: 500GB

Access

In case of upcoming system maintenance, we kindly seek permission to access customer infrastructure. Our aim is to ensure seamless operations and address any potential issues promptly.

Overview

Onum supports integration with AWS S3. Select Amazon S3 from the list of Listener types and click Configuration to start.

Minimum requirements

Before configuring and starting to send data with the Amazon S3 Listener, you need to take into consideration the following requirements:

• Your Amazon user needs at least permission to use the GetObject operation (S3) and the ReceiveMessage and DeleteMessageBatch operations (SQS Bucket) to make this Listener work.

• You need to configure your Amazon S3 bucket to send notifications to an Amazon Simple Queue Service (SQS) queue when new files are added. Learn how to do it below:

  ```json
  {
    "Version": "2012-10-17",
    "Id": "S3ToSQSPolicy",
    "Statement": [
      {
        "Sid": "AllowS3Bucket",
        "Effect": "Allow",
        "Principal": {
          "Service": "s3.amazonaws.com"
        },
        "Action": "SQS:SendMessage",
        "Resource": "arn:aws:sqs:<region>:<account-id>:<queue-name>",
        "Condition": {
          "ArnLike": {
            "aws:SourceArn": "arn:aws:s3:::<bucket-name>"
          },
          "StringEquals": {
            "aws:SourceAccount": "<account-id>"
          }
        }
      }
    ]
  }
  ```

Configuration

Now you need to specify how and where to collect the data, and how to establish a connection with AWS S3.

Metadata

Enter the basic information for the new Listener.

Configuration

Objects

Bucket

Bucket Advanced

Queue

Queue Advanced

General Advanced

Overview

A Push type of Listener passively sources data without explicitly requesting, whereas a Pull type is where the user actively requests data from an external source.

Click the Listeners tab on the left menu for a general overview of the Listeners configured in your Tenant and the events generated.

Narrow Down Your Data

There are various ways to narrow down what you see in this view:

Add Filters

Add filters to narrow down the Listeners you see in the list. Click the + Add filter button and select the required filter type(s). You can filter by:

• Name: Select a Condition (Contains, Equals, or Matches) and a Value to filter Listeners by their names.

• Type: Choose the Listener type(s) you want to see in the list.

• Version: Filter Listeners by their version.

• Created by: Selecting this option opens a User drop-down where you can filter by creator.

• Updated by: Selecting this option opens a User drop-down where you can filter by the last user to update a pipeline.

The filters applied will appear as tags at the top of the view.

Select a Time Range

Select Tags

You can choose to view only those Listeners that have been assigned the desired tags. You can create these tags in the Listener settings or from the cards view. Press the Enter key to confirm the tag, then Save.

To filter by tags, click the + Tags button, select the required tag(s) and click Save.

Create a Listener

Depending on your permissions, you can create a new Listener from this view. To do it, simply click the New listener button at the top right corner.

This will open the Listener configuration.

Configure a Listener

Configuring your Listener involves various steps. You can open the configuration pane by creating a new Listener or by clicking a Listener in the Listener tab or the Pipeline view and selecting Edit Listener in the pane that opens.

Alternatively, click the ellipses in the card or table view and select Edit.

Type

The first step is to define the Listener Type. Select the desired type in this window and select Configuration.

Configuration

Labels

Click a Listener to see how to configure it.

Overview

The Azure Event Hubs Listener lets you receive messages from an Azure Event Hub for real-time data streaming, providing support for message batching, retries, and secure connection options.

Select Azure Event Hubs from the list of Listener types and click Configuration to start.

Configuration

Now you need to specify how and where to collect the data, and how to establish a connection with Microsoft Azure Event Hubs.

Metadata

Enter the basic information for the new Listener.

Configuration

Now add the configuration to establish the connection.

Overview

Onum supports integration with Cisco NetFlow.

Select Cisco NetFlow from the list of Listener types and click Configuration to start.

Configuration

Now you need to specify how and where to collect the data, and how to establish a connection with Cisco NetFlow.

Metadata

Enter the basic information for the new Listener.

Configuration

Now add the configuration to establish the connection.

Socket

Flow

Access control