Metric 0.1.6

Metric 0.1.6

This release makes Telegram alerts easier to configure, adds a Helm chart for
Kubernetes, and introduces automatic database migrations.

What's new

• More flexible Telegram alerts. Use a custom Bot API URL, send notifications
  to a chat or a specific topic, and reuse an already configured bot for multiple
  recipients without entering its token again. Recipients can be removed from
  delivery, and the UI shows bot and chat names when available. Public channel and
  supergroup @usernames are supported; private users connect through a bot link
  or a known chat ID because Telegram does not let bots look them up by username.
  Thanks for #3!
• Helm chart for Kubernetes. Deploy with bundled or external MongoDB, local or
  S3-compatible file storage, and the same Min/Low/Medium/High profiles as Compose.
  Chart version, application version and Docker image tag all match: 0.1.6.
  The chart is published to oci://ghcr.io/biosshot/charts/metric with the release.
  See the Helm guide.
  Thanks for #4!
• Automatic database migrations. Metric applies the required migration chain
  on startup, before accepting events or starting workers. This release includes
  the 19 → 20 transition for existing Telegram destinations. Work is processed
  in bounded batches and can resume after an interruption. There is no separate
  migration command or confirmation step. A maintenance page and logs show progress.
• Manual backup and restore documentation. A Docker-tested guide covers a dump
  of just Metric's MongoDB database, local or S3 blob storage, and restoring both.
  This is documentation for existing tools, not a new backup command or PostgreSQL
  backend. See the backup guide.
  Thanks for #5!

Updating from 0.1.5

Back up the Metric database, BlobStore and installation secrets together before
updating. Keep the existing secrets and follow the
update guide.

Metric 0.1.5 uses schema generation 19. On first startup, 0.1.6 automatically
migrates a complete generation-19 database to generation 20. New installations
start at generation 20. Databases older than generation 19 are not supported by
this migration chain; do not erase them or edit their schema marker.

During migration, normal API/SDK requests receive HTTP 503 and /ready stays
unavailable; /live remains healthy. Behind Kubernetes Ingress, use logs or a direct
pod port-forward to see progress while the pod is not ready.

Migrations are forward-only. Switching the image back to 0.1.5 does not undo the
database migration. Returning to that version requires restoring the pre-upgrade
database and matching blob backup, with the original secrets.

Metric 0.1.5

Full Changelog: v0.1.4...v0.1.5

Metric 0.1.4

Full Changelog: v0.1.3...v0.1.4

Metric 0.1.2

Full Changelog: v0.1.1...v0.1.2

Metric 0.1.1

Full Changelog: v0.1.0...v0.1.1

Metric 0.1.0

Full Changelog: https://github.com/biosshot/metric/commits/v0.1.0