alerting-stack

Define Telegram-based alerting for uptime, VM, LLM spend, and Hetzner cost monitoring.

6|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/Xipher-Labs/walter-os --skill alerting-stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: alerting-stack
Source: https://github.com/Xipher-Labs/walter-os/tree/main/skills/alerting-stack
Command: npx skills add https://github.com/Xipher-Labs/walter-os --skill alerting-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates “set up alerts but don’t get woken up or understand what happened” by providing a lightweight, single-channel alerting stack tailored for a self-hosted Walter-VM environment.

Core Features & Use Cases

  • Telegram-first, single channel notification: routes multiple alert tiers into one pinned chat to keep alert handling cognitively cheap.
  • Four-tier coverage for realistic failure modes: combines uptime checks (Uptime-Kuma), VM resource watchdogs (cron script with debouncing), LLM spend/budget triggers (LiteLLM → n8n → Telegram), and Hetzner cost trend monitoring (hcloud CLI → cron → Telegram).
  • Debounced, transition-based alerts: sends messages on threshold transitions to prevent notification fatigue and alert flapping.
  • Cost and budget awareness: alerts on spend thresholds, unexpected usage spikes, and projected month-end Hetzner cost drift.

Quick Start

Configure your Telegram bot token and chat ID in WALTER_TELEGRAM_BOT_TOKEN and WALTER_TELEGRAM_CHAT_ID, then add the Tier 1 Uptime-Kuma monitors and deploy the watchdog and Hetzner spend scripts using the provided locations and cron examples.

Frequently Asked Questions about alerting-stack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get Telegram alerts for self-hosted services?

You can get Telegram alerts for self-hosted services by configuring a bot token and chat ID, then routing uptime checks, VM watchdogs, and spend thresholds into a single pinned chat.

How do I monitor LiteLLM spend and budget thresholds?

To monitor LiteLLM spend, you can route budget threshold triggers via a webhook to n8n, which then forwards the alert notifications directly to your Telegram chat.

Can I use Uptime-Kuma with Telegram for alerting?

Yes, Uptime-Kuma serves as the Tier 1 uptime monitor in this stack, routing its service status checks into a unified Telegram notification channel.

What is the best way to prevent alert fatigue when monitoring VM resources?

The best way to prevent alert fatigue is using debounced, transition-based alerts that only send messages when thresholds are crossed, stopping notification flapping from VM resource degradation.

How do I track Hetzner cost trends and projected spend?

You can track Hetzner cost trends by running hcloud CLI projections via cron scripts, which alert you on Telegram if unexpected month-end spend drift is detected.

Do I need a Telegram bot to set up this alerting stack?

Yes, a Telegram bot integration is required; you must configure your bot token and chat ID as environment variables to receive the unified service and spend alerts.