OpenTelemetry

Edge Delta supports OpenTelemetry (OTel) as a protocol for ingesting and exporting logs, metrics, and traces. You can send OTLP data into Edge Delta pipelines from instrumented applications, OTel Collectors, or any OTLP-compatible source, and route processed data to downstream OTLP receivers.

OTel is not a requirement for using Edge Delta. The Edge Delta agent collects telemetry from Kubernetes, files, APIs, and other sources without OTel instrumentation. However, if your environment already uses OTel or you need OTLP-compatible data flow, Edge Delta integrates at every stage of the pipeline.

Choose your path

Select the approach that matches your use case:

I want to instrument my application code

Add OpenTelemetry SDKs to your application to emit structured logs, metrics, and traces. Edge Delta supports both code-based and zero-code instrumentation for Java, Python, Node.js, Go, and .NET.

See Instrument Your Code.

I have an OTel Collector and want to send data to Edge Delta

Point your existing OTel Collector’s OTLP exporter at an Edge Delta pipeline. This works with both edge pipelines (Kubernetes, VM) and cloud pipelines.

See OTel Collector Setup.

I want to ingest OTLP data into a pipeline

Configure an OTLP source node in your pipeline to receive data from any OTLP-compatible source.

See OTLP Source Node for the full configuration reference.

I want to transform or strip OTel metadata

Use the Deotel processor to remove OTLP wrapper metadata before sending data to legacy systems, or use OTTL Transform to selectively modify OTel-formatted data.

See Transform OTel Data.

I want to export data via OTLP to a downstream system

Configure an OTLP destination node to send processed telemetry to any OTLP-compatible receiver using gRPC or HTTP.

See OTLP Destination.

I need help troubleshooting OTel

Find solutions for common issues with OTLP ingestion, export, data transformation, and instrumentation.

See OTel Troubleshooting.

How Edge Delta works with OpenTelemetry

Edge Delta integrates with OpenTelemetry at three points in the data pipeline:

Ingestion: The OTLP source node accepts data over gRPC or HTTP from OTel SDKs, OTel Collectors, or any OTLP-compatible source. You configure the source node with a port and protocol, and it handles the rest.

Processing: Once inside the pipeline, OTel-formatted data flows through processors like any other telemetry. You can use OTTL Transform to modify attributes, Deotel to strip OTLP metadata, or any other processor to filter, enrich, or aggregate the data.

Export: The OTLP destination node sends processed data to downstream OTLP receivers such as Datadog, Grafana, Dynatrace, or Sumo Logic. It supports both gRPC and HTTP with TLS, custom headers, and persistent queuing.

In this section