rtcollector - A modular, RedisTimeSeries-native observability agent
I’m a long-time time series nerd, I’ve worked with InfluxDB, TimescaleDB, ClickHouse, and more, across everything from monitoring fleets to tracking medical devices. But recently, I started exploring RedisTimeSeries again… and I was surprised by how much the Redis Stack has evolved. Between RedisTimeSeries, RedisJSON, RediSearch, and Streams, I realized: this could actually be the backbone for a full observability stack. So I built rtcollector, a modular, Redis-native observability agent. It’s written in Python, configured with YAML, and designed to push system, container, and database…
In plain words
rtcollector is a Python-based observability agent that collects system, container, and database metrics and stores them in RedisTimeSeries. Configured via YAML, it functions as a Redis-native alternative to Telegraf, offering input plugins for Linux and macOS system metrics, Docker container statistics, and databases like Redis, MySQL, and PostgreSQL. It's designed for users who want to build monitoring solutions using Redis Stack's time series, JSON, and search capabilities as a unified backend.
written from the facts on this page · September 2026
From the sources
In the maker’s words, at launch
I’m a long-time time series nerd, I’ve worked with InfluxDB, TimescaleDB, ClickHouse, and more, across everything from monitoring fleets to tracking medical devices. But recently, I started exploring RedisTimeSeries again… and I was surprised by how much the Redis Stack has evolved. Between RedisTimeSeries, RedisJSON, RediSearch, and Streams, I realized: this could actually be the backbone for a full observability stack. So I built rtcollector, a modular, Redis-native observability agent. It’s written in Python, configured with YAML, and designed to push system, container, and database metrics into RedisTimeSeries with labels and retention. Think of it as a Telegraf alternative, but for Redis. Right now, I’ve implemented input plugins for: • Linux: CPU, memory, disk, I/O, network • macOS: CPU, memory, disk, I/O, network • Docker: container stats via API • Redis, MySQL, PostgreSQL The idea is to keep it simple, extensible, and Redis-first. Next steps: • Native logs via RedisJSON + RediSearch (already prototyped!) • Support for Redis Streams (for traces/events) • Dashboards in Grafana using the Redis data source If you’re into observability, Redis, or just like building small purposeful tools, I’d love your thoughts or contributions. It’s early, but already useful for homelabs, edge boxes, and anyone tired of deploying 10 containers just to get CPU metrics. Repo: https://github.com/xe-nvdk/rtcollector
More ai this month
the category →
I trained a 125M-parameter transformer to autocomplete piano performances in real time (~108 notes/sec on an iPhone 15). The idea is basically GitHub Copilot or Tabnine, except instead of prompting it with code, you prompt it by playing a few notes on a MIDI piano. The model then continues what you played, entirely on-device. The app is free if anyone wants to try it. Happy to answer questions about the model, training, Core ML, or the many things that didn't work.
AI · 17d ago · simedw.com
Astute▲585Automate your B2B brand going viral, with new media creators
AI · 18d ago · company-app.joinastute.com
Hey HN, Henry from Cactus here! We previously released Cactus Needle, a 14MB agentic LLM for tool call, device use, and structured extraction for phones, wearables, smart homes, small robots and microcontrollers. We got really great feedback here, and have now incorporated the suggestions to release Needle 2. The whole model is a single 14MB binary that runs a full session in 28MB of RAM; 45m parameters at 2bit compression. Needle hits 500 tokens/sec decode speed on a Raspberry Pi 5, sits between 400-1,500 tokens/sec on VR devices like Meta Quest 3S and Apple Vision Pro, and ranges…
AI · 26d ago · cactuscompute.com
Launched alongside, May 2025
the whole month →
- C9
Life & fun · 2025 · felixrieseberg.github.io
