Rotel

---

About

Rotel provides an efficient, high-performance solution for collecting, processing, and exporting telemetry data. Rotel is ideal for resource-constrained environments and applications where minimizing overhead is critical.

Features:

• Supports metrics, logs, and traces
• OTLP receiver supporting gRPC, HTTP/Protobuf, and HTTP/JSON
• OTLP exporter supporting gRPC and HTTP/Protobuf
• Built-in batching and retry mechanisms
• Additional exporters: ClickHouse, Datadog, AWS X-RAY, AWS EMF, and Kafka
• Additional receivers: File, Fluent, Kafka, and Ksmsg (Linux kernel messages)
• Python and Rust processor SDKs

Rotel can be easily bundled with popular runtimes as packages. Its Rust implementation ensures minimal resource usage and a compact binary size, simplifying deployment without the need for a sidecar container.

Runtime integrations:

• Python: streamfold/pyrotel
• Node.js: streamfold/rotel-nodejs

Rotel provides a unified data plane framework for high-performance OpenTelemetry processing. It can be used as a library and deployed in many different form factors:

• Lambda Extension: AWS Lambda Extension for OpenTelemetry collection with minimal coldstart latency
• Lambda Forwarder: Convert and forward CloudWatch and S3-stored stored logs to OpenTelemetry compatible backends
• AWS Firelens: AWS Firelens log router for easy Amazon ECS container logging

Rotel is fully open-sourced and licensed under the Apache 2.0 license.

Getting Started

Running Rotel

docker run -ti -p 4317-4318:4317-4318 public.ecr.aws/rotel-dev/rotel --debug-log traces --exporter blackhole

Rotel is now listening on localhost:4317 (gRPC) and localhost:4318 (HTTP).

We use the prebuilt Docker image for this example, but you can also download a binary from the releases page.

Verify

Send OTLP traces to Rotel and verify that it is receiving data:

go install github.com/open-telemetry/opentelemetry-collector-contrib/cmd/telemetrygen@latest

telemetrygen traces --otlp-insecure --duration 5s

Check the output from Rotel and you should see several "Received traces" log lines.

# Generate and send traces directly to Rotel
cargo run --bin generate-otlp -- traces --http-endpoint localhost:4318

# Or generate a trace file for testing
cargo run --bin generate-otlp -- traces --file trace.pb

# Then send it with curl
curl -X POST http://localhost:4318/v1/traces \
  -H "Content-Type: application/x-protobuf" \
  --data-binary @trace.pb

Configuration

• Base options
• OTLP exporter
  • Cloudwatch OTLP Export
  • Basic Authentication
• Datadog exporter
• ClickHouse exporter
• AWS X-Ray exporter
• AWS EMF exporter
• Kafka exporter
  • Acknowledgement Modes
  • Producer Performance Tuning
  • Message Partitioning Control
  • Advanced Configuration
  • Testing the Kafka Exporter
• File exporter
• Kafka Receiver
  • Offset Tracking and Data Reliability
  • Consumer Configuration

Base options

Rotel is configured on the command line with multiple flags. See the table below for the full list of options. Rotel will also output the full argument list:

rotel start --help

All CLI arguments can also be passed as environment variable by prefixing with ROTEL_ and switching hyphens to underscores. For example, --otlp-grpc-endpoint localhost:5317 can also be specified by setting the environment variable ROTEL_OTLP_GRPC_ENDPOINT=localhost:5317.

Any option above that does not contain a default is considered false or unset by default.

以上为 README 的开头部分。其余内容请阅读原文。 查看完整 README ↗