getredash/redash

Implement test option for alert destinations

Open

#2628 opened on Jun 26, 2018

View on GitHub
 (0 comments) (3 reactions) (0 assignees)Python (24,845 stars) (4,236 forks)batch import
BackendFrontendenhancementhelp wanted

Description

Just like we have a "Test Connection" for data sources, we should have a "Trigger Test" for alert destinations to make sure they are properly configured.

Contributor guide

Tech stack
pythonjavascript
Domain
backendtesting
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Redash alert system understandingExisting 'Test Connection' patternPython and JavaScript development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Examine the existing 'Test Connection' for data sources (likely in models/data sources.py and static/js/pages/DataSourcesList.jsx). For alert destinations, look at models/alerts.py and static/js/pages/AlertsList.js or similar. The feature requires a new API endpoint to trigger a test alert and handle the response, then add a 'Trigger Test' button on the alert destination settings page. Check any existing test helpers for notifications.