Skip to content

v0.6.0

Choose a tag to compare

View all tags
@zigazajc007 zigazajc007 released this 09 Mar 20:04
· 1 commit to main since this release
v0.6.0
2531be3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

⚠️ Breaking Changes

Incidents moved from ClickHouse to SQL database

Incidents and maintenances are now stored in a SQL database instead of ClickHouse. SQLite is used by default (no external dependency required), but PostgreSQL and MySQL/MariaDB are also supported.

Note: Since the project is still in beta, there is no auto-migration of incidents from ClickHouse. Existing incidents will remain in ClickHouse but will no longer be displayed. New incidents and maintenances will be stored in the SQL database going forward.

Docker Compose: New volume required for SQLite persistence

If you're using Docker Compose with the default SQLite database, you must add a volume to persist your data. Without this, your incidents and maintenances will be lost on container restart.

Add uptime_monitor_db to your docker-compose.yml:

services:
  uptimemonitor:
    volumes:
      - ./config.toml:/app/config/config.toml
      - uptime_monitor_db:/app/databases  # <-- ADD THIS

volumes:
  uptime_monitor_db:  # <-- ADD THIS
    driver: local

Database configuration

The default database.url is already set correctly for Docker Compose, so no changes to config.toml are required. However, it's recommended to explicitly set it:

[database]
url = "sqlite://./databases/uptime_monitor.db"

Supported connection URLs:

  • SQLite (default): sqlite://./databases/uptime_monitor.db
  • PostgreSQL: postgres://user:password@localhost:5432/uptime_monitor
  • MySQL/MariaDB: mysql://user:password@localhost:3306/uptime_monitor

Tables are created automatically on startup.

New Features

  • Maintenances - Full maintenance management with scheduling, timeline updates, affected monitors/groups, and automatic status transitions (scheduled --> in_progress --> completed)
  • Notification suppression - Both incidents and maintenances now include suppress_notifications (enabled by default). When active, down/still-down notifications are suppressed for affected monitors and groups during the incident or maintenance window.
Assets 3
Loading