What's new

A human summary of each release — what changed and why. The full technical list lives in the CHANGELOG, announcements in the Telegram channel.

0.4.12 · August 12, 2026 — operator tier for teams

A cumulative release (includes the docs-only 0.4.11). The full story is in the blog.

• Operator tier. Project team members run day-to-day monitoring without org-admin rights: monitors, the heartbeat ping token, maintenance windows, status-page content, issue alert rules and metric alerts. Alert channels stay owner/admin: a channel’s recipient and secret are credentials, not an operational setting; the team sees the channel list and delivery log with recipients masked.
• Security. Monitor headers (e.g. an Authorization header on an HTTP check) are encrypted at rest, the same way channel secrets are. A status page’s public address is an opaque /status/p_... key instead of a slug: names can no longer be probed or squatted; old links keep working via 301.
• Reliability. Ingest: memory protection while ClickHouse is idle, honest queue/quota accounting, per-org attribution of dropped data. A corrupted channel secret is no longer treated as live — alerts are not lost on that path. Fixes for uptime check consensus, maintenance windows and OAuth invitations.
• UX. A Copy button on event pages — the event context on the clipboard in one click, as Markdown or plain text.
• Docs. The SDK section covers the CMS extension family (WordPress, Joomla, 1C-Bitrix, Drupal, OpenCart, MODX, Tilda); an AlmaLinux/RHEL installation guide.

0.4.10 · August 5, 2026 — stabilization of the 0.4.x line

The outcome of two full product audits (operations, security, accessibility, i18n) and the 0.4.5–0.4.10 patch train:

• Operations. Compose stack with memory ceilings and healthchecks; a hardened app container (read-only FS, no-new-privileges). Liveness and readiness are separate: /healthz and /readyz. --migrate-force recovers an interrupted migration; the schema carries a backward-compatibility marker — rolling back a release no longer requires restoring from a backup. Retention is configurable per data kind: metrics, profiles, incidents.
• Restricted networks. GOTCHA_TELEGRAM_API_BASE points Telegram delivery at your own Bot API server; GOTCHA_NET_MTU sets the container network MTU for tunnel setups.
• Correctness. Transaction quota is charged for what is stored, not what arrived; regression durations fixed (µs were read as ms); alerts, retries and throttling are computed by the database clock.
• Security. Removing a member from an organization revokes their teams' project access too; invite-mode registration requires the token from the link; deeply nested OTLP/JSON is rejected; the redirect guard is hardened (CodeQL report).
• Notifications & UX. One operator-chosen notification language (GOTCHA_LOCALE); “inside the perimeter” channels with full event details; keyboard navigation, contrast and screen-reader support across the UI.

0.4.0 · July 27, 2026 — time windows and explainable perf issues

• One time-range control (1h / 24h / 7d / 30d / custom) on every chart page.
• A perf-issue page explains “what’s happening / how to fix” for its kind (N+1, slow query, HTTP flood) — with the full SQL and the code location.
• Full request details on issue pages: method, URL, params, body, headers (PII-scrubbed).
• Tooltips for every metric: p50–p99, failure rate, Apdex, Web Vitals.

0.3.x · July 24–25, 2026 — reliable uptime and small servers

• Per-check retries for uptime monitors — transient blips no longer raise false incidents.
• Latency chart with DNS → TCP → TLS → TTFB phases; a distinct “partial” availability state.
• A docker-compose.small.yml overlay for minimal servers (2 vCPU / 2 GB).

0.1.0 · July 22, 2026 — first public release

The initial set: errors (Sentry SDK protocol), distributed traces and Web Vitals, OTLP metrics, CPU profiles (flamegraphs), uptime monitoring with status pages, alerts via email/webhook/Telegram, organizations and RBAC, SSO (OIDC, Yandex ID, VK ID), PII scrubbing and SSRF protection on by default — one Go binary with PostgreSQL and ClickHouse.