https://blog.margrop.net/en/tag/monitoring/ Recent content in Monitoring on Margrop Blog Hugo -- gohugo.io en-US Sun, 24 May 2026 08:10:00 +0800 https://blog.margrop.net/en/post/codex-reset-radar-quota-reset-guide/ Sun, 24 May 2026 08:10:00 +0800 https://blog.margrop.net/en/post/codex-reset-radar-quota-reset-guide/ <blockquote> <p><strong>The short version</strong></p> <p>Codex resets have recently become more important to watch. Sometimes the reset is part of the normal usage cycle. Sometimes it is a compensation reset after an incident. Sometimes it follows a fix for abnormal limit consumption. For heavy Codex users, the painful part is not that the quota resets. The painful part is discovering that you still had useful weekly quota left, but you did not use it before the reset overwrote the old window.</p> <p><code>Codex Reset Radar</code> is a small public dashboard that turns scattered public signals into a practical warning: if a Codex quota reset window is likely or already open, it tells you to use your remaining weekly quota on valuable work before it expires.</p> </blockquote> <p>This article discusses only public pages, public status signals, and public references. It does not include private accounts, tokens, internal systems, private network details, or personal usage data. Any discussion of quota, reset windows, and early warnings is a user-side workflow analysis, not an official statement about OpenAI billing, subscription policy, or service guarantees.</p> https://blog.margrop.net/en/post/proxmoxve-lvm-link-speed-uptime-kuma/ Tue, 05 May 2026 17:20:00 +0800 https://blog.margrop.net/en/post/proxmoxve-lvm-link-speed-uptime-kuma/ <blockquote> <p><strong>Short version</strong></p> <p>Proxmox VE <code>local-lvm</code> is usually an LVM-thin pool, not a normal mounted directory, so <code>df -h</code> is not enough to catch it before it becomes full. Network link speed is another quiet failure mode: services may stay online while a NAS or router uplink falls back to 100 Mb/s and turns large file transfers into a crawl. A practical fix is to feed both checks into the Uptime Kuma you already use: expose a small HTTP health endpoint for <code>local-lvm</code>, and push link-speed status from the Proxmox host with an <code>ethtool</code> script.</p> </blockquote> <p>This article walks through the design, the problems in a naive implementation, improved scripts, systemd units, Uptime Kuma configuration, verification steps, and safety notes. All addresses, tokens, host names, and environment-specific values are placeholders. Replace <code>&lt;PVE_HOST&gt;</code>, <code>&lt;KUMA_URL&gt;</code>, <code>&lt;PUSH_TOKEN&gt;</code>, and <code>&lt;INTERFACE&gt;</code> with values from your own environment.</p>