Monitoring: Adjust health-check thresholds

未关闭
#1,111 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
fastapi, python
领域
backend, devops, observability-sre

调研方向

首先定位 production 健康检查阈值，并将其与使用阈值 3 的 staging 配置进行比较。使用服务器日志和 Sentry 检查下一个告警窗口，同时检查已知端点和实际请求状态。当 production 阈值设置为 3、误报按所述方式处理，并且 staging Sentry cron 的行为已完成调查时，即表示完成。

由索引模型根据 Issue 内容生成。

描述

Is your feature request related to a problem?
Prod emits recurring "downtime detected" alerts due to misconfigured thresholds. This causes alert noise and misinterpretation of server status, which can lead to unnecessary troubleshooting efforts.

Describe the solution you'd like

  • Set prod health-check threshold to 3.
  • Suppress alarms after confirming ~5–6 known endpoints return 200.
  • Verify server logs and status during downtime windows for accurate root cause analysis.
  • Investigate Sentry cron monitor behavior on staging.
Original issue

Context

Prod emits recurring "downtime detected" alerts. Alert noise traced to threshold config: staging (backend, guardrails, frontend) uses threshold 3 and produces no false alerts; prod is on a different value. Request timeout is 15s, exponential backoff ~3–4s then ~8s, health check every 1 min.

Decisions

  • Set prod health-check threshold to 3. Caveat: if the health endpoint genuinely isn't responding (prod is intermittently loaded), the threshold change only silences the symptom — write the real hypothesis (FastAPI thread saturation at ~40 threads / ~50–100 concurrent requests) into the issue so a green dashboard isn't misread as solved.
  • When a downtime alarm fires, first hit ~5–6 known endpoints; if they return 200, treat as a false alarm and suppress.

Verification (before assuming bot-flood root cause)

  • For each downtime window, check logs + Sentry: was the server actually down, did real LLM calls come through and with what status, did bot call volume spike? Confirm against Prajna's root cause.
  • Pull logs for the next alert window and confirm actual server behavior.

Related

  • A Sentry cron monitor is also firing on staging while staging is green — determine whether Sentry is misbehaving, it's the dev-env uptime check, or the notification setup is wrong.
主要语言
Python
星标
18
派生
10
平均合并
2 天 20 小时
30 天内合并 PR
14

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

ProjectTech4DevAI/kaapi-backend 的其他 Issue

查看 ProjectTech4DevAI/kaapi-backend 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。