Flagsmith/flagsmith

Track integration health

Open

Aperta il 10 lug 2024

Vedi su GitHub
 (0 commenti) (0 reazioni) (0 assegnatari)Python (3475 star) (264 fork)batch import
apifront-endgood first issue

Descrizione

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

Guida contributor

Tech stack
python
Dominio
full stackapi
Tipo issue
feature
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
3-5 days
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
stale
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
mostly clear
Prerequisiti
Understanding of Flagsmith's integration systemBasic Python backend knowledge
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
40
Direzione di ricerca
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'.