getredash/redash

Implement test option for alert destinations

Open

#2,628 opened on Jun 26, 2018

View on GitHubContributor guide
 (0 comments) (3 reactions) (0 assignees)Python (4,236 forks)batch import
BackendFrontendenhancementhelp wanted

Repository metrics

Stars
 (24,845 stars)
PR merge metrics
 (Avg merge 9d 5h) (3 merged PRs in 30d)

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

Research direction
Investigate the existing 'Test Connection' implementation for data sources in the Redash codebase to understand the pattern. Then explore the alert destination configuration code to identify where a similar 'Trigger Test' button can be added. Focus on the backend API and frontend components related to alert destinations.
Tech stack
python
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
PythonGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70