Skip to content

Issue #5 - [FEATURE] Include database name in backup notifications #9

@zenocross

Description

@zenocross

Description

When database backups complete, the notification sent to users only indicates "Database backup completed" without specifying which database was backed up. This makes it difficult to track backups when managing multiple databases.

Current Behavior

  • Database backup process completes
  • Generic notification sent: "Database backup completed"
  • No database identifier in notification
  • Users cannot determine which database was backed up
  • Confusing when multiple databases are configured

Expected Behavior

  • Backup completes for specific database
  • Notification includes database name: "Database backup completed: production-db"
  • Clear identification of backed up database
  • Separate notifications for each database backup
  • Better audit trail for backup operations

Use Cases

  • Multiple databases: Users managing several databases need to track each backup
  • Troubleshooting: Verify correct database was backed up
  • Compliance: Clear audit trail of which databases are being backed up
  • Monitoring: Easy identification of backup operations

Steps to Reproduce

  1. Configure multiple databases in Omi backend
  2. Set up automatic backups for at least one database
  3. Trigger or wait for backup to complete
  4. Observe notification received
  5. Notice notification lacks database name/identifier

Proposed Solution

Modify backup notification system to:

  • Pass database name/identifier to notification function
  • Update notification message template to include database name
  • Format: "Database backup completed: {database_name}"
  • Ensure database context is available throughout backup process
  • Test with different database types and names

Technical Context

  • Component: Backend backup notification system
  • Type: Feature enhancement
  • Language: Python
  • Involves: Backup service, notification service
  • Files: Backup logic and notification templating
  • Data flow: Database context → Backup service → Notification service

Download https://cap.so/ to record your screen (use Studio mode). Export as an mp4, and drag and drop into an issue comment below.

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureAuto-created label

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions