Skip to content

Telemetry Tracker v1.22.0

Choose a tag to compare

View all tags
@unjica unjica released this 12 Oct 12:11
· 89 commits to develop since this release
v1.22.0
b86aeba
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Highlights

  • Cron and background-job check-ins (#783) — create a monitor (interval or cron schedule with timezone, grace period, optional max runtime), ping it from your job (success / start / fail, run IDs, exit codes), see history, and get missed / timeout / failure alerts plus recovery notices on your existing alert destinations. Rotate, pause and delete from the dashboard. Node helper included. Docs: https://telemetry-tracker.com/docs/checkins
  • Secret in a header (recommended): curl -fsS -X POST -H "X-TT-Checkin-Token: $TT_CHECKIN_TOKEN" https://api.telemetry-tracker.com/checkin. Path URLs (/checkin/<token>) still work but appear in proxy/CDN logs.
  • Plan caps: monitors per project: Free 5, Pro 50, Business 500. Ping limits: 12/min per monitor, 600/min per project.

Upgrade notes (self-hosters)

  • Migration: 20261012133000_checkin_monitors (additive: new enums and tables, two new AlertRuleType values). Run pnpm --filter api exec prisma migrate deploy.
  • New env vars: CHECKIN_ENCRYPTION_KEY on the API (required for check-ins: 32 random bytes as 64 hex chars, e.g. openssl rand -hex 32). Back it up with your database backups: losing it makes stored check-in secrets unreadable. CHECKIN_PUBLIC_BASE_URL on the dashboard if API_URL is internal.
  • Missed-run detection needs the alert-rules evaluator cron (node dist/jobs/run-alert-rules-evaluator.js, every 5 minutes); webhook/chat delivery needs the webhook worker.

Full details: CHANGELOG

Assets 2
Loading