Feature Request: Support for individual metadata fields in notification templates #218

New Issue

MrUnknownDE · 2026-04-05T16:16:00+02:00

MrUnknownDE commented

2026-04-05 16:16:00 +02:00

Originally created by @acesyde on 1/17/2026

Description

Hi there! 👋

First of all, thank you for building Databasus. It’s a great tool that makes database management much easier!

Currently, the notification system allows us to send a heading and a message. I would like to suggest an improvement to make these notifications even more powerful by allowing us to send specific data points as separate variables in the templates.

Proposed Feature

It would be amazing if we could access and send the following information individually within the notification templates:

Database Name: The name of the database being processed.
Date: The timestamp of the operation.
Size: The size of the database or backup file.
Status: The outcome of the operation (e.g., success or failed).

Why is this useful?

Having these as separate fields (instead of just being part of a single message block) would allow users to:

Improve Readability: Create cleaner, structured alerts on platforms like Slack, Discord, or Telegram.
Better Automation: Easily parse these fields if notifications are sent to logging or monitoring tools.
Custom Styling: Change the look of the notification based on the specific status or size.

Additional Context

This would add a lot of flexibility for anyone looking to integrate Databasus into a more complex monitoring workflow.

I'm happy to discuss this further or provide more examples of how this could look in the configuration!

*Originally created by @acesyde on 1/17/2026* ### Description Hi there! 👋 First of all, thank you for building Databasus. It’s a great tool that makes database management much easier! Currently, the notification system allows us to send a `heading` and a `message`. I would like to suggest an improvement to make these notifications even more powerful by allowing us to send specific data points as separate variables in the templates. ### Proposed Feature It would be amazing if we could access and send the following information individually within the notification templates: * **Database Name**: The name of the database being processed. * **Date**: The timestamp of the operation. * **Size**: The size of the database or backup file. * **Status**: The outcome of the operation (e.g., `success` or `failed`). ### Why is this useful? Having these as separate fields (instead of just being part of a single message block) would allow users to: 1. **Improve Readability**: Create cleaner, structured alerts on platforms like Slack, Discord, or Telegram. 2. **Better Automation**: Easily parse these fields if notifications are sent to logging or monitoring tools. 3. **Custom Styling**: Change the look of the notification based on the specific status or size. ### Additional Context This would add a lot of flexibility for anyone looking to integrate Databasus into a more complex monitoring workflow. I'm happy to discuss this further or provide more examples of how this could look in the configuration!

MrUnknownDE closed this issue

2026-04-05 16:16:00 +02:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/databasus#218