HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
rotel-dev
rotel
Rust2025–2026
rotel-dev / rotel

rotel

High Performance, Resource Efficient OpenTelemetry Collection

Observability
Explore on GitHubRead Hacker News discussions
3Distinct people
4Mentions
0Explicit recommenders
414GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

High Performance, Resource Efficient OpenTelemetry Collection

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month4 dated mentions

Observed mentions: 2025-05-14 19:51:18 UTC to 2026-08-22 16:28:32 UTC.

012025-05-01 00:00:00 UTC to 2025-06-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 20252025-06-01 00:00:00 UTC to 2025-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-07-01 00:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-01 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 20252026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
May 20252025-05-01 00:00:00 UTC2025-06-01 00:00:00 UTC101
Jun 20252025-06-01 00:00:00 UTC2025-07-01 00:00:00 UTC101
Jul 20252025-07-01 00:00:00 UTC2025-08-01 00:00:00 UTC000
Aug 20252025-08-01 00:00:00 UTC2025-09-01 00:00:00 UTC110
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC000
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC000
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC000
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC000
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC000
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC000
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC000
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC000
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC000
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC000
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC101

What Hacker News says

4 sources
rjenkins·Aug 5, 2025Submission

Show HN: Rotel – Fast and Efficient OpenTelemetry Collection in Rust

Project Page: https://rotel.dev Github: https://github.com/streamfold/rotel Hi HN, Ray and Mike here! We’re building Rotel, a new high performance, resource efficient approach to OpenTelemetry collection. Rotel is open source (Apache License 2.0) and runs as a standalone process and collects telemetry from external processes or other collection agents. It consumes 75% less memory and 50% less CPU in benchmarks https://streamfold.github.io/rotel-otel-loadtests/benchmarks, so it is particularly well-suited for environments where resource optimization is paramount. Mike and I love working on Observability solutions. We’ve built and optimized telemetry data planes for products such as Librato, Papertrail and AppOptics. As we’ve scaled high volume data processing systems over the years, we’ve often found ourselves under pressure to improve Saa
Read the rest
S margins or the resilience of complex distributed systems. This has led us to the same question again and again: How can we do this more reliably and efficiently? We believe telemetry collection demands high levels of efficiency, and Rotel is our first step toward addressing that need. Rotel’s Lambda extension https://github.com/streamfold/rotel-lambda-extension has already unlocked the promise of OpenTelemetry in production serverless environments, where resource constraints previously made this nearly impossible. With Rotel we’re also rethinking DX for OpenTelemetry collection. Its lightweight footprint allows for packaging directly in runtimes like Python and Node.js, eliminating the need for additional configuration and deployment of sidecars. Rotel’s Python Processor SDK enables you to build telemetry processors right from your favorite IDE with the ease and expressiveness of Python and the performance of Rust. Getting started with Rotel is easy using prebuilt Docker containers, just run… `docker run -ti -p 4317-4318:4317-4318 streamfold/rotel --debug-log traces --exporter blackhole` to start Rotel listening for OTLP traffic on ports 4317 & 4318. Check out the Getting Started guide for more install and config instructions: https://rotel.dev/docs/setup/getting-started. We’re super excited to share Rotel with you and would love to hear what you think!
9 points · Open discussion
mike_heffner·May 14, 2025
Thanks for sharing this — it’s a really promising direction. The advantages of Arrow for OTLP, especially when used end-to-end, are compelling given the protocol overhead of OTLP. We’ve been thinking along similar lines with the use of Rust, particularly for OpenTelemetry collection in environments where high performance and low resource overhead are critical, such as edge and serverless. With that in mind, we’ve open-sourced a lightweight OpenTelemetry collector written in Rust to address these use cases. We’ve also developed a native Lambda extension around it, and have seen encouraging interest from folks aiming to improve cold start times. The project is still fairly early, but we’re optimistic that Rust can open up new opportunities for efficient observability pipelines. Vendors like Datadog are also moving in this direction with the
Read the rest
ir Lambda extension and appear to be adopting Rust more broadly for data-plane components. If this resonates, feel free to take a look here: https://github.com/streamfold/rotel. We’d love to hear your thoughts on how this could be useful.
In OpenTelemetry protocol with Apache Arrow

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.