GitHub user Jai-76 created a discussion: Add "Test Configuration" & "Send Test
Notification" button to Alerts & Reports UI
### Is your feature request related to a problem? Please describe.
Setting up **Alerts & Reports** is currently one of the most friction-heavy
parts of the Superset experience.
When a user creates a new Alert or Report (e.g., "Send Dashboard PDF every
Monday"), there is no immediate way to verify that the **entire delivery
pipeline** is working.
* **The Problem:** Users often save the alert and "wait and see" if it arrives.
If it fails, the UI simply shows a generic error or "Execution Failed" status.
* **The Debugging Gap:** Diagnosing the failure requires access to backend logs
(Celery worker logs, WebDriver container logs) to distinguish between:
* SMTP/Slack Authentication failures.
* Headless Browser/WebDriver crashes (screenshot generation).
* Celery Beat scheduling issues.
This dependency on server logs disempowers Data Analysts and floods DevOps
teams with support tickets.
### Describe the solution you'd like
I propose adding a **"Test Configuration"** or **"Run Now & Verify"** button
within the Alert/Report creation modal.
**Desired Behavior:**
When clicked, this action should trigger a synchronous (or short-polling) check
that attempts to:
1. **Render the Artifact:** Attempt to generate the screenshot/CSV using the
configured WebDriver.
2. **Send the Notification:** Attempt to send the actual email or Slack
message to the target.
3. **Report Immediate Feedback:**
* *Success:* "Test notification sent to [email/channel]."
* *Failure:* Display the specific error from the backend (e.g.,
`ConnectionRefusedError: SMTP server not responding` or `WebDriverException:
Chrome binary not found`).
### Describe alternatives you've considered
* **Current Workaround:** Setting the schedule to `* * * * *` (every minute) to
test it, then changing it back. This is clumsy and error-prone.
* **Execution Log:** The current "Execution Log" tab provides some info, but it
is reactive (after the failure) and often truncated/generic.
### Additional Context
As Superset moves toward a more mature BI platform (Superset 4.0+), closing the
loop on "observability" for end-users is critical. This feature is standard in
other tools (e.g., Grafana's "Test Contact Point", Metabase's "Send test
email").
GitHub link: https://github.com/apache/superset/discussions/37209
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
