<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: dohelper</title>
    <description>The latest articles on DEV Community by dohelper (@dohelper_0f75b617be84c9bf).</description>
    <link>https://dev.to/dohelper_0f75b617be84c9bf</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3799931%2F4eb2304b-9e7f-49ca-a956-2de53bd97fe7.png</url>
      <title>DEV Community: dohelper</title>
      <link>https://dev.to/dohelper_0f75b617be84c9bf</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/dohelper_0f75b617be84c9bf"/>
    <language>en</language>
    <item>
      <title>DockProbe: Lightweight Docker Monitoring with Anomaly Detection &amp; Telegram Alerts</title>
      <dc:creator>dohelper</dc:creator>
      <pubDate>Mon, 02 Mar 2026 00:16:55 +0000</pubDate>
      <link>https://dev.to/dohelper_0f75b617be84c9bf/dockwatch-lightweight-docker-monitoring-with-anomaly-detection-telegram-alerts-a10</link>
      <guid>https://dev.to/dohelper_0f75b617be84c9bf/dockwatch-lightweight-docker-monitoring-with-anomaly-detection-telegram-alerts-a10</guid>
      <description>&lt;p&gt;Are you flying blind with your Docker containers? One command changes that.&lt;/p&gt;

&lt;p&gt;

  &lt;iframe src="https://www.youtube.com/embed/SqKSEtiyYzM"&gt;
  &lt;/iframe&gt;


&lt;/p&gt;

&lt;p&gt;I built &lt;strong&gt;DockProbe&lt;/strong&gt; — a lightweight, self-hosted Docker monitoring dashboard that gives you full visibility into your containers with zero configuration.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is DockProbe?
&lt;/h2&gt;

&lt;p&gt;DockProbe runs as a single Docker container and collects real-time CPU, memory, network, and disk metrics from all your containers and the host machine. Everything is displayed in a clean, dark-themed web UI that auto-refreshes every 10 seconds.&lt;/p&gt;

&lt;p&gt;No agents to install. No external database. No complex setup. Just mount the Docker socket, run one command, and you're done.&lt;/p&gt;

&lt;h2&gt;
  
  
  Key Features
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;📊 &lt;strong&gt;Real-time Dashboard&lt;/strong&gt; — Dark-themed UI with sortable tables and Chart.js charts&lt;/li&gt;
&lt;li&gt;🔍 &lt;strong&gt;Container Monitoring&lt;/strong&gt; — CPU %, memory %, network I/O, block I/O, restart count&lt;/li&gt;
&lt;li&gt;🌡️ &lt;strong&gt;Host Monitoring&lt;/strong&gt; — CPU/GPU temperature, disk usage, load average&lt;/li&gt;
&lt;li&gt;🚨 &lt;strong&gt;Anomaly Detection&lt;/strong&gt; — 6 built-in rules: CPU spike, memory overflow, high temp, disk full, unexpected restart, network surge&lt;/li&gt;
&lt;li&gt;📱 &lt;strong&gt;Telegram Alerts&lt;/strong&gt; — Instant notifications with 30-minute cooldown per alert type&lt;/li&gt;
&lt;li&gt;🔒 &lt;strong&gt;Security&lt;/strong&gt; — Basic Auth, rate limiting, HTTPS (self-signed or Cloudflare Tunnel)&lt;/li&gt;
&lt;li&gt;⚡ &lt;strong&gt;Lightweight&lt;/strong&gt; — Only 4 Python packages, SQLite with 7-day retention&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Quick Start
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git clone https://github.com/deep-on/dockprobe.git &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="nb"&gt;cd &lt;/span&gt;dockprobe &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; bash install.sh
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That's it. The interactive installer sets up authentication, Telegram alerts, and HTTPS in under a minute.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Requirements:&lt;/strong&gt; Docker (with Compose v2), Git, OpenSSL&lt;/p&gt;

&lt;h2&gt;
  
  
  Anomaly Detection
&lt;/h2&gt;

&lt;p&gt;DockProbe watches your containers 24/7 and alerts you before users notice:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Rule&lt;/th&gt;
&lt;th&gt;Condition&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Container CPU&lt;/td&gt;
&lt;td&gt;&amp;gt;80% for 3 consecutive checks&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Container Memory&lt;/td&gt;
&lt;td&gt;&amp;gt;90% of limit&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Host CPU Temp&lt;/td&gt;
&lt;td&gt;&amp;gt;85°C&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Host Disk&lt;/td&gt;
&lt;td&gt;&amp;gt;90% usage&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Container Restart&lt;/td&gt;
&lt;td&gt;restart_count increased&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Network Spike&lt;/td&gt;
&lt;td&gt;RX 10x surge + &amp;gt;100MB&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;All thresholds are configurable via environment variables.&lt;/p&gt;

&lt;h2&gt;
  
  
  Access Modes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Local Network&lt;/strong&gt; — Self-signed SSL, access via &lt;code&gt;https://localhost:9090&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Remote Access&lt;/strong&gt; — Port forwarding option&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cloudflare Tunnel&lt;/strong&gt; — Recommended for remote access, no port-forwarding needed, proper TLS certificate&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why I Built This
&lt;/h2&gt;

&lt;p&gt;Existing Docker monitoring solutions are either too heavy (Prometheus + Grafana stack) or too simple (just showing container status). I wanted something in between — lightweight enough to run on a home server, but smart enough to catch problems automatically and ping me on Telegram.&lt;/p&gt;

&lt;p&gt;DockProbe is the result: 4 Python dependencies, a single HTML file for the UI, and SQLite for storage. It stays out of your way until something goes wrong.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try It Out
&lt;/h2&gt;

&lt;p&gt;🔗 &lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/deep-on/dockprobe" rel="noopener noreferrer"&gt;https://github.com/deep-on/dockprobe&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Feedback, issues, and PRs are welcome! If you find it useful, a ⭐ on GitHub goes a long way.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Built by &lt;a href="https://deep-on.com" rel="noopener noreferrer"&gt;DeepOn Inc.&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>docker</category>
      <category>devops</category>
    </item>
    <item>
      <title>How I Built a Docker Monitoring Dashboard in a Single Container</title>
      <dc:creator>dohelper</dc:creator>
      <pubDate>Sun, 01 Mar 2026 13:28:03 +0000</pubDate>
      <link>https://dev.to/dohelper_0f75b617be84c9bf/how-i-built-a-docker-monitoring-dashboard-in-a-single-container-j74</link>
      <guid>https://dev.to/dohelper_0f75b617be84c9bf/how-i-built-a-docker-monitoring-dashboard-in-a-single-container-j74</guid>
      <description>&lt;h2&gt;
  
  
  The Problem
&lt;/h2&gt;

&lt;p&gt;

  &lt;iframe src="https://www.youtube.com/embed/SqKSEtiyYzM"&gt;
  &lt;/iframe&gt;


&lt;/p&gt;

&lt;p&gt;I run about 10 Docker containers on a home server. Nothing crazy — nginx, postgres, redis, a few web apps. I wanted a simple way to check if everything was healthy.&lt;/p&gt;

&lt;p&gt;The obvious answer was Prometheus + Grafana. But for my use case, it felt like bringing a firetruck to blow out a candle:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Prometheus: separate container, config files, scrape targets, retention policies&lt;/li&gt;
&lt;li&gt;Grafana: another container, dashboards to build, data sources to configure&lt;/li&gt;
&lt;li&gt;Node Exporter: yet another container for host metrics&lt;/li&gt;
&lt;li&gt;cAdvisor: and another one for container metrics&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That's 4 extra containers just to monitor 10 containers. Something felt wrong.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Idea
&lt;/h2&gt;

&lt;p&gt;What if monitoring was just... one container? Mount the Docker socket, open a browser, done.&lt;/p&gt;

&lt;p&gt;That's what I built. It's called &lt;strong&gt;DockProbe&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F1a86h717p42ruxap6220.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F1a86h717p42ruxap6220.png" alt="DockProbe Dashboard"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Architecture Decisions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Why FastAPI?
&lt;/h3&gt;

&lt;p&gt;I needed async because Docker stats streaming is inherently async. FastAPI with uvicorn gave me:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Async Docker API calls via aiodocker&lt;/li&gt;
&lt;li&gt;Built-in OpenAPI docs (useful during development)&lt;/li&gt;
&lt;li&gt;Single-process, low memory footprint&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Why SQLite?
&lt;/h3&gt;

&lt;p&gt;For a monitoring tool with 7-day retention, SQLite in WAL mode is perfect:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;No separate database container&lt;/li&gt;
&lt;li&gt;Handles the write pattern well (one insert every 10 seconds)&lt;/li&gt;
&lt;li&gt;Named volume for persistence across container restarts&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Why a Single HTML File?
&lt;/h3&gt;

&lt;p&gt;Zero build step. No npm, no webpack, no node_modules. The entire dashboard is one HTML file with inline CSS and JavaScript. Chart.js is loaded from CDN. This means:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;docker compose up -d&lt;/code&gt; and you're done&lt;/li&gt;
&lt;li&gt;No frontend build pipeline to maintain&lt;/li&gt;
&lt;li&gt;Easy to customize — it's just one file&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Anomaly Detection
&lt;/h2&gt;

&lt;p&gt;Instead of just showing numbers, DockProbe watches for problems. Six rules run on every collection cycle (10 seconds):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="c1"&gt;# CPU: must be high for 3 consecutive checks (30 seconds)
# This avoids false alarms from brief spikes
&lt;/span&gt;&lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;cpu_pct&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="n"&gt;CPU_THRESHOLD&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;cpu_counts&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;container&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;+=&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;cpu_counts&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;container&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;=&lt;/span&gt; &lt;span class="mi"&gt;3&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="nf"&gt;trigger_alert&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;cpu_high&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;container&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;cpu_pct&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;else&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;cpu_counts&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;container&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Each alert type has a 30-minute cooldown per target, so you won't get spammed if a container is consistently misbehaving. Alerts go to Telegram via a simple httpx POST — no email server, no Slack webhook setup.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Result
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;4 Python packages:&lt;/strong&gt; fastapi, uvicorn, aiodocker, httpx&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;~50MB memory&lt;/strong&gt; usage&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;10-second&lt;/strong&gt; collection interval&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;7-day&lt;/strong&gt; data retention&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;One command&lt;/strong&gt; to install
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git clone https://github.com/deep-on/dockprobe.git &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="nb"&gt;cd &lt;/span&gt;dockprobe &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; bash install.sh
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  What I Learned
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;aiodocker's stats API&lt;/strong&gt; returns different formats depending on &lt;code&gt;stream=True&lt;/code&gt; vs &lt;code&gt;stream=False&lt;/code&gt;. Cost me hours of debugging.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Self-signed HTTPS&lt;/strong&gt; is important even for local tools — browsers increasingly block HTTP features.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Single-file dashboards&lt;/strong&gt; are underrated. No build step means no build breakage.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What's Next
&lt;/h2&gt;

&lt;p&gt;I'm considering:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Container log viewer&lt;/li&gt;
&lt;li&gt;Custom alert thresholds per container&lt;/li&gt;
&lt;li&gt;Multi-host support&lt;/li&gt;
&lt;li&gt;Webhook integrations beyond Telegram&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/deep-on/dockprobe" rel="noopener noreferrer"&gt;https://github.com/deep-on/dockprobe&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you're running Docker containers and want simple monitoring without the Prometheus/Grafana overhead, give it a try. Feedback and stars are very welcome!&lt;/p&gt;

</description>
      <category>monitoring</category>
    </item>
  </channel>
</rss>
