Flagsmith/flagsmith

Track integration health

Open

#4,324 opened on 2024年7月10日

GitHub で見る
 (0 comments) (0 reactions) (0 assignees)Python (3,475 stars) (264 forks)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
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
3-5 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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'.