Flagsmith/flagsmith

Track integration health

Open

#4324 opened on Jul 10, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (3,475 stars) (264 forks)batch import
apifront-endgood first issue

Description

Is your feature request related to a problem? Please describe.

Right now for SaaS customers it's hard to tell whether an integration they configured actually works.

Describe the solution you'd like.

For each configured integration, display its health status based on latest request attempt.

Describe alternatives you've considered

Ping Flagsmith support in Crisp/Discord manually. :/

Additional context

No response

Contributor guide

Tech stack
python
Domain
full stackapi
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.
3-5 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.
mostly clear
Prerequisites
Understanding of Flagsmith's integration systemBasic Python backend knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
To implement this feature, first investigate how integrations are currently configured and stored in the Flagsmith backend (likely in the Python/Django codebase). Look for existing models and endpoints related to integrations. Then, determine how to perform a health check for each integration type (e.g., by making a test request). On the frontend, add a health status indicator component. Refer to the issue #4324 for any further discussion. Since the issue has no comments, it may be valuable to ask maintainers for clarification on which integrations are prioritized and what defines 'health status'.