From 7f4334c8d5ba248c916487c90a9b853702626632 Mon Sep 17 00:00:00 2001 From: Felix Faerber Date: Fri, 21 Aug 2026 16:16:26 +0300 Subject: [PATCH] stamp-monitor: fullness from chunks stored, not stamps issued The batch tile read 100% above 'fullest bucket 13 of 16'. Bee's utilization saturates and never comes back down once a mutable batch recycles; the bucket map says what is actually held. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01YLYiaPYror1vLKApYKrxTu --- hostinger/prod-stack.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hostinger/prod-stack.yaml b/hostinger/prod-stack.yaml index 95760f7..49ee0ed 100644 --- a/hostinger/prod-stack.yaml +++ b/hostinger/prod-stack.yaml @@ -39,7 +39,7 @@ services: # Bee node that saw them knows how full a batch is. Sitting next to prod_bee # is what makes fullness, the bucket map and batch_full alerts possible. stamp-monitor: - image: ghcr.io/ffaerber/swarm-stamp-monitor@sha256:109883005af7ae411a3aee04d69d94068e761005cd3e5cab372fa10c70ec72ea + image: ghcr.io/ffaerber/swarm-stamp-monitor@sha256:bbe9c46b1f4761e7a8d51567990121ae51ac627b8d108f9979e99668bb90936a networks: [internal, public] volumes: - stamp-monitor-data:/data