QuantumNous / QuantumNous/new-api
失败时自动禁用通道和成功时自动启用通道加入阈值配置
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 48.5k
- Forks
- 11.6k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 58
Description
提交前必读（请勿删除本节）
- 文档：https://docs.newapi.ai/
- 使用问题先看或先问：https://deepwiki.com/QuantumNous/new-api
- 警告：删除本模板、删除小节标题或随意清空内容的 issue，可能会被直接关闭；重复恶意提交者可能会被 block。
您当前的 newapi 版本
v0.11.9-alpha.3
提交确认
- 我已确认目前没有类似 issue
- 我已完整查看过文档 https://docs.newapi.ai/ 和项目 README，已确定现有版本无法满足需求
- 我未删除此模板中的任何引导内容或小节标题，并会按要求完整填写
- 我理解项目维护者精力有限，不遵循模板要求的 issue 可能会被无视或直接关闭
功能描述
希望在运营设置-》监控设置-》失败时自动禁用通道和成功时自动启用通道的功能中，加入两个次数阈值
只有达到失败次数和成功次数的阈值的通道才会自动禁用或启用，在中途出现相反的结果会重置计数
应用场景
在接入多个渠道时，可能会偶发产生一些小问题，目前是直接就禁用了，希望加入一个阈值来进行缓冲
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the Operations Settings > Monitoring Settings area and trace the existing automatic channel disable and enable behavior. Add configurable success and failure count thresholds, reset the relevant counter when the opposite result occurs, and verify that channels change state only after reaching the configured threshold.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100