Flagsmith/flagsmith

Track integration health

Open

#4,324 建立於 2024年7月10日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)Python (3,475 star) (264 fork)batch import
apifront-endgood first issue

描述

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

貢獻者指南

技術棧
python
領域
full stackapi
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Understanding of Flagsmith's integration systemBasic Python backend knowledge
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
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'.