<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ghkdqhrbals on Medium]]></title>
        <description><![CDATA[Stories by Ghkdqhrbals on Medium]]></description>
        <link>https://medium.com/@ghkdqhrbals?source=rss-da47820db042------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*gC7pQAoasFxYsGcb</url>
            <title>Stories by Ghkdqhrbals on Medium</title>
            <link>https://medium.com/@ghkdqhrbals?source=rss-da47820db042------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 00:24:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ghkdqhrbals/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Why I Built a Kafka-Style Operations Console for Redis Streams]]></title>
            <link>https://medium.com/@ghkdqhrbals/why-i-built-a-kafka-style-operations-console-for-redis-streams-5196fafbe8e7?source=rss-da47820db042------2</link>
            <guid isPermaLink="false">https://medium.com/p/5196fafbe8e7</guid>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[observability]]></category>
            <category><![CDATA[redis-stream]]></category>
            <category><![CDATA[message-queue]]></category>
            <category><![CDATA[redis]]></category>
            <dc:creator><![CDATA[Ghkdqhrbals]]></dc:creator>
            <pubDate>Thu, 30 Jul 2026 04:07:42 GMT</pubDate>
            <atom:updated>2026-07-30T04:12:10.238Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FeqWPzicOtDZi_FT.png" /></figure><p>Redis Streams provides durable messages, consumer groups, pending-entry tracking, and explicit acknowledgement. The primitives are powerful, but operating them day to day still often means combining CLI commands, application logs, and unrelated monitoring dashboards.</p><p>Kafka users have mature consoles for browsing records and understanding consumer state. I wanted a similarly focused workflow for Redis Streams, without deploying a heavy monitoring stack.</p><p>That became <strong>StreamScope.</strong></p><h3>The operational gap</h3><p>When a Redis Streams consumer slows down, I usually want to answer a small set of questions quickly:</p><ul><li>Which streams are active?</li><li>How many entries and consumer groups exist?</li><li>Which group is accumulating lag?</li><li>Which consumers are active or inactive?</li><li>What is currently in the pending-entry list?</li><li>When was the last message published and consumed?</li><li>Is the delay coming from Redis or from the consumer?</li><li>What changed during the last few minutes?</li></ul><p>The Redis CLI can answer these questions, but not as one continuous workflow.</p><h3>What StreamScope provides</h3><p>StreamScope combines the following in one UI:</p><ul><li>Stream and message browsing</li><li>Payload inspection for JSON and non-JSON values</li><li>Live tail</li><li>Cursor-based message pagination</li><li>Consumer groups, consumers, lag, and pending entries</li><li>One-second time-series metrics</li><li>Published and consumed message rates</li><li>Consume delay and Redis response latency</li><li>Standalone, Sentinel, and Cluster connections</li><li>Redis ACL, passwords, TLS, and mTLS</li><li>Users, roles, permissions, and access logs</li></ul><h3>Keeping deployment small</h3><p>I wanted the application to be easy to add beside an existing Redis deployment. The backend is written in Go, the frontend uses React and TypeScript, and embedded SQLite stores application configuration and access data.</p><p>The application ships as one multi-architecture container. Its compressed layers are approximately 6 MB for amd64 and slightly smaller for arm64.</p><h3>How to Run it</h3><pre>docker run -d \<br>  --name streamscope \<br>  -p 8080:8080 \<br>  -v streamscope-data:/data \<br>  ghcr.io/ghkdqhrbals/streamscope:latest</pre><h3>Feedback</h3><p>The public repository is available here!<br><a href="https://github.com/ghkdqhrbals/streamscope">https://github.com/ghkdqhrbals/streamscope</a></p><p>I am especially interested in feedback about consumer-group troubleshooting, metric definitions, and the first-run connection experience.</p><p><em>Originally published at </em><a href="https://dev.to/_none_fd15e5c17db24/why-i-built-a-kafka-style-operations-console-for-redis-streams-iko"><em>https://dev.to</em></a><em> on July 30, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5196fafbe8e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>