Skip to content

History / Overview

Revisions

  • Document per-service escalation policies, manual alert-to-incident linking, setup wizard, notification preferences - Concepts-Escalation-Policies.md: remove the "single global policy" limitation notice — each Service now has its own optional escalation policy, with a warning when none is assigned. - Concepts-Services.md: document the escalationPolicyId field. - New Concepts-Alerts.md, Concepts-Incidents.md, Concepts-Maintenances.md: dedicated pages for these concepts, including the manual (never automatic) alert-to-incident linking flow. - New Notification-Preferences.md: personal channels (Email, Telegram, Twilio SMS, Ntfy) vs. team-level Integrations, verification-code flow, priority ordering. - New Setup-Wizard.md: the 3-step wizard (General → Account → Email), why email verification is now mandatory, and the one-time post-setup feature showcase. - Overview.md, Home.md, Triggers.md: correct supported trigger/channel list — Webhook, Slack, Discord, Google Chat, and Microsoft Teams are registered in the schema but were never wired up to actually dispatch anything; only Email, Telegram, Twilio SMS, Opsgenie, Pushover, and Ntfy work today. - Development-Setup.md, Hosting-Overview.md, Self-Hosting.md: fix stale architecture references (.NET 9 → .NET 10, npm → pnpm, single SvelteKit frontend → apps/web (Next.js) + apps/admin (Vite) + PostgreSQL). - Environment-Variables.md: note that email config is now mandatory during initial setup. - _Sidebar.md: add links for all new pages.

    @cl8dep cl8dep committed Jul 13, 2026
  • docs: add Overview page explaining Piro concepts and architecture

    @cl8dep cl8dep committed Jul 1, 2026