feat(tenant): E2 租户 blast radius——DLQ 配额 + 队列/事件指标
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python, redis
- Domain
- backend, observability
Research direction
Start with tenant_context.py and tenant_quota.py to understand the shared queue and current quota coverage, then review dependency #316 for its scanner. Define per-tenant DLQ quota and queue/DLQ metrics, including the suggested alert above 50%. Done means the 10k-message blast-radius check shows other tenants’ p99 degradation at or below 20%; the issue names no test or metric entry point.
Written by the indexing model from the issue text.
Description
优先级 P2 · 依赖：depends-on: #316
基线 HEAD = 658a912f
Summary
队列/DLQ/event bus 是共享的（tenant_context.py 平台机制键不分区）；
DLQ 单 Stream、上限 1000 条全租户共享；配额只覆盖 start（tenant_quota.py），
不覆盖队列深度/DLQ/订阅。
建议
- per-tenant DLQ 配额（>50% 告警）；
tenant_queue_depth/tenant_dlq_entries/ 其他租户 p99 劣化指标；- 复用 #316 的扫描器，不新增进程；
- blast-radius 验收：单租户灌 10k 消息，其他租户 p99 劣化 ≤20%。
边界
- T0；不做独立 Stream/Redis（T1/T2 再立项）。
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 2h 33m
- Merged PRs (30d)
- 9
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from jeffkit/plaita
-
enhancement
Difficulty 4/5 1-2 days Newbie friendliness 43/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
jeffkit/plaita#305 · 4 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Arekkazu/sgpmp-backend#744 ·
Maintainers usually reply within 1 day
-
agent/reviewer
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
projectbluefin/utah-packages#634 ·
Maintainers usually reply within 1 day
-
enhancement good first issue help wanted
Difficulty 2/5 1-2 days Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
home-assistant/core#188613 ·
Maintainers usually reply within 1 day
-
WebsiteOpengood first issue
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
TanbirRamim/open-source-radar#314 ·
Maintainers usually reply within 1 day