forked from Dokploy/dokploy
-
Notifications
You must be signed in to change notification settings - Fork 161
Open
Labels
featureAuto-created labelAuto-created label
Description
Description
Database backup notifications don't include the specific database name, making it difficult for users to identify which database was backed up when managing multiple databases.
Current Behavior
- Backup completes successfully
- Notification sent: "Database backup completed"
- User cannot identify which specific database
- Confusing when managing multiple databases
Expected Behavior
- Backup completes successfully
- Notification includes database name: "Database backup completed: production-db"
- Clear identification of backed up database
- Better management of multiple databases
Use Cases
- Multiple databases: Users with several databases need to track which were backed up
- Troubleshooting: Easier to verify correct database was backed up
- Audit trail: Better logging and tracking of backup operations
Steps to Reproduce
- Set up multiple databases in Dokploy
- Configure automatic backups for one database
- Wait for backup to complete or trigger manual backup
- Check notification
- Observe lack of database name in notification
Proposed Solution
Modify the backup notification system to:
- Pass database name/identifier to notification function
- Include database name in notification message template
- Ensure consistent formatting across different notification channels
Technical Context
- Component: Backup notification system
- Type: Feature enhancement
- Involves: Backend notification logic, message templating
- Database context needs to be passed to notification layer
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
Labels
featureAuto-created labelAuto-created label