Send data using OpenTelemetry
Most recent version: v0.0.1
Overview
Onum supports integration with OpenTelemetry.
OpenTelemetry (OTel) is an open-source observability framework that provides a standardized way to collect and manage telemetry data (logs, metrics, and traces) from applications and infrastructure.
Open Telemetry Setup
The prerequisites for sending data to OpenTelemetry generally fall into three categories: Instrumentation, Collector Setup, and Configuration. You need these pieces in place to capture, process, and export observability data (traces, metrics, and logs).
Use the OTel API to manually or automatically instrument the code.
Traces: Define spans around operations you want to measure (e.g., database calls, function execution).
Metrics: Record counter, gauge, or histogram values for system health (e.g., CPU usage, request latency).
Logs: Configure your logging frameworks (like Log4j or Logrus) to use the OTel format and include trace context (known as contextual logging).
While you can send data directly from Onum to a backend, the recommended and best practice method is to use the OpenTelemetry Collector.
You must have the OTel Collector deployed in a location accessible to Onum (e.g., as a sidecar, a daemon set on Kubernetes, or a standalone service).
The collector needs a
YAMLconfiguration file that defines three things:Receivers: How it receives data from your application (usually using the OTLP protocol).
Processors: How it manipulates the data (e.g., filtering, batching, adding resource attributes).
Exporters: How it sends the final data to the backend (e.g., to Jaeger, Prometheus, or a cloud provider).
Both Onum and the collector must be configured to use the OpenTelemetry Protocol (OTLP).
Set the environment variable
OTEL_EXPORTER_OTLP_ENDPOINTin Onum to point to the collector's address and port (e.g.,http://otel-collector:4318).Establish a network connection to the OTLP receiver endpoint (often using gRPC on port 4317 or HTTP on port 4318).
Onum Setup
Log in to your Onum tenant and click Data Sinks > New Sink.
Double-click the Open Telemetry Sink.
Enter a Name for the new Sink. Optionally, add a Description and some Tags to identify the Sink.
Choose the desired protocol to send your data (gRPC or HTTP).
Configure your OTLP/gRPC or OTLP/HTTP endpoint (e.g. otel-collector.mycompany.com:4317-
Set the HTTP Port* to establish the connection with the protocol.
Set the Use gzip Compression option to true if you want to compress your data in gzip format.
Set the milliseconds to wait for data to be successfully transmitted before terminating the attempt. The minimum value is 1.
Choose how to export the three distinct types of telemetry data:
Send Traces*
Set this option to true if you want to send Traces to your OpenTelemetry account. If you select the HTTP sending protocol, you'll be prompted to optionally include your HTTP Traces Path e.g. http://collector:port/v1/traces
Send Metrics*
Set this option to true if you want to send Metrics to your OpenTelemetry account. If you select the HTTP sending protocol, you'll be prompted to optionally include your HTTP Metrics Path e.g. http://collector:port/v1/metrics
Send Logs*
Set this option to true if you want to send Logs to your OpenTelemetry account. If you select the HTTP sending protocol, you'll be prompted to optionally include your HTTP Logs Path e.g. http://collector:port/v1/logs
Depending on the type(s) of data you're sending (Traces, Metrics, and/or Logs), your events must have a specific set of information in OpenTelemetry format. Check an example for every data type below:
Set the Allow batch configuration option to true and fill in the following options to establish batch configuration:
Sizer* - Decide whether to set the batches in bytes or items.
Minimum size of the batch - Set the minimum capacity of the batch. The default value is
8192and the minimum value is0.Max size of the batch - Set the maximum capacity of the batch. It must be higher than the minimum set above. The default value is
8192and the minimum value is0.Time in milliseconds (ms) to send the batch - Enter the timeout to send the batch in milliseconds. The default value is
200and the minimum value is0.
Set Allow TLS configuration as true if you decide to include TLS authentication in this Listener:
The credentials are saved in Onum as Secrets. In the authentication form, click New secret to create a new one:
Give the token a Name.
Turn off the Expiration date option.
Click Add new value.
Click Save.


You can now select the secret you just created in the Token/Password fields.
Authentication Configuration
This option will only appear if you choose HTTP in the Protocol option, or you choose gRPC as Protocol and set TLS Configuration.
Choose the authentication configuration for your request:
Authentication Type*
Choose your required authentication type:
Test Configuration
Select Wait for result as true to test the connection to the destination by waiting for a response from the server.
Click Finish when complete. Your new Data sink will appear in the Data sinks area list.
Pipeline configuration
When it comes to using this Data sink in a Pipeline, you must configure the following output parameters. To do it, simply click the Data sink on the canvas and select Configuration.
Output configuration
Event field to be sent*
Choose the field that contains the data to be sent.
Click Save to save your configuration.
Last updated
Was this helpful?

