ProjectTech4DevAI / ProjectTech4DevAI/kaapi-backend

Monitoring: Automate alerts and dashboards

オープン
#1,144 コメント 0 件 リアクション 0 件 担当者 1 名 GitHub で見る

@vprashrex がすでに取り組んでいます。

2026年9月4日 から。

主要言語
Python
スター
18
フォーク
10
平均マージ
2日 20時間
マージ済み PR(30日)
14

説明

Is your feature request related to a problem?
We lack an ongoing monitoring and observability structure for Kaapi, leading to manual checks that can be inefficient and error-prone.

Describe the solution you'd like

  • Automate breach notifications (memory, CloudWatch alarms) to Discord.
  • Implement eval-run load monitoring in two stages:
    • Stage 1: Sentry HTTP endpoint graphs on eval-run endpoints for run density.
    • Stage 2: Live Celery queue backlog alerts.
  • Establish app-level monitoring: endpoint hit counts, slow requests, waterfall dig-ins; create a custom Sentry dashboard.
  • Create two dashboards: one for AWS (infra) and one for Sentry (app-level), to be reviewed in the weekly call.
  • Weekly reporting should focus on red flags/odd numbers, skipping consistently green metrics.

Actions

  • Propose feature-wise/app-level metrics (latency, etc.) for the Sentry dashboard.
  • Set up Discord breach notifications.
  • Verify staging Container Insights and configure staging alerts.

Related: ProjectTech4DevAI/kaapi-backend#1052, ProjectTech4DevAI/kaapi-backend#1005, ProjectTech4DevAI/kaapi-backend#825

Original issue

Context

Establishing the ongoing monitoring/observability structure for Kaapi. Akhilesh's health-check doc is taken as the infra baseline checklist. Direction is to automate rather than manually check.

Scope

  • Push breach notifications (memory, CloudWatch alarms) to Discord instead of manual checks.
  • Eval-run load monitoring:
    stage 1 = Sentry HTTP endpoint graphs on eval-run endpoints as a proxy for run density;
    stage 2 = live Celery queue backlog alerts. No LLM-call rate limits yet — deliberately deferred until scale demands it.
  • App-level monitoring: endpoint hit counts, slow requests, waterfall dig-ins; build a custom Sentry dashboard.
  • Target: two dashboards — one AWS (infra), one Sentry (app-level) — reviewed in the weekly call.
  • Weekly reporting convention: share only red flags / odd numbers; skip steadily-green metrics.

Actions

  • Team to propose feature-wise / app-level metrics (latency etc.) for the Sentry dashboard.
  • Set up Discord breach notifications.
  • Verify staging Container Insights and configure staging alerts.

Related: ProjectTech4DevAI/kaapi-backend#1052, ProjectTech4DevAI/kaapi-backend#1005, ProjectTech4DevAI/kaapi-backend#825

コントリビューションガイド

コントリビューションガイドを開く

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

評価

この issue はまだ評価されていません。

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。