bearcove

bearcove / peeps

Public

Instrument tokio tasks, OS threads, tokio/parking_lot locks, roam RPC

20
1
100% credibility
Found Feb 18, 2026 at 19 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
Rust
AI Summary

Peeps adds gentle monitoring to Rust apps to visualize live activity like tasks, locks, channels, and network waits in an interactive dashboard.

How It Works

1
📰 Discover peeps

You hear about peeps, a friendly tool that peeks inside running apps to show what's busy or stuck, without slowing anything down.

2
📦 Add to your app

Sprinkle peeps into your Rust project with a simple line – it blends right in like magic.

3
🚀 Run your app

Start your app as usual, and peeps quietly starts watching tasks, waits, and connections in the background.

4
🖥️ Open dashboard

Launch the peeps viewer on your screen to see a live picture of your app's world.

5
📡 Apps connect

Your running apps link up automatically, sharing snapshots of their inner activity.

6
📸 Capture now

Click to grab a real-time map of everything happening inside your apps.

7
🔍 Explore the map

Zoom around the colorful graph of tasks, channels, locks, and waits to spot slow spots.

🎉 Fix and fly

Pinpoint the jam, tweak your app, and watch it speed up happily ever after.

Sign up to see the full architecture

6 more

Sign Up Free

Star Growth

See how this repo grew from 19 to 20 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is peeps?

Peeps is a low-overhead instrumentation toolkit for Rust apps using Tokio, letting you track tasks, OS threads, parking_lot locks, sync primitives like channels and semaphores, and even Roam RPC connections. Drop in simple wrappers around `spawn`, channels, and mutexes, initialize with `peeps::init_named("my-service")`, set `PEEPS_DASHBOARD=127.0.0.1:9119`, and it pushes live JSON graph snapshots over TCP to a web dashboard at `127.0.0.1:9120`. Open peeps github to peep into dainty movement for disease fighter services—peep into meaning in real-time graphs of stalls and contention.

Why is it gaining traction?

Unlike heavy profilers, peeps compiles to zero-cost passthroughs when the `diagnostics` feature is off, yet delivers a canonical resource graph with edges showing needs/touches/spawned relations. Developers love the push-only live UI for spotting backpressure in bounded channels or lock waiters without SIGUSR1 dumps or file parsing. The `peep!` macro and tracked futures make async debugging feel native, no boilerplate.

Who should use this?

Rust backend engineers running Tokio services who chase production stalls, like full mpsc queues or mutex contention in high-throughput APIs. Ideal for teams debugging distributed systems with Roam RPC, needing live visibility into task polls, thread samples, and sync primitives without pausing prod.

Verdict

Grab it for Tokio apps if you need runtime graphs—early at 18 stars and 1.0% credibility score, but solid docs, examples, and tests make it worth a spin over generic tracers. Maturity lags behind battle-tested tools, so test in staging first.

(198 words)

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.