质量与评审
legacy-modernisation-observability
更新于 2026-11-09
Legacy Modernisation · 可观测性规则
Observability rules for Legacy Modernisation: intent-level traces, symptom-based alerts and owned dashboards.
- 技术栈
- Legacy Modernisation
- 主题
- 可观测性
- 条目
- 9 条
- 版本
- v0.2.0
✓ 应当这么做
- ✓ Emit one trace per user intent and one span per external call
- ✓ Alert on symptoms that pages a human, not on causes that do
- ✓ Keep dashboards owned, dated and tied to a decision
✕ 常见反模式
- ✕ High-cardinality labels (user id, raw path) in metrics
- ✕ Dashboards with no owner that nobody opens
- ✕ Alerts that fire on expected batch jobs
◎ 交付前验证
- ◎ Typecheck (`tsc --noEmit` or equivalent) passes with zero errors
- ◎ Lint passes and no rule was disabled inline
- ◎ Node/browser runtime compatibility checked against the project engines field
同分类条目
11 篇质量与评审
Static Analysis 工程规则
Static analysis rules: treat warnings as errors for new code and justify exceptions
质量与评审
Code Review 工程规则
Review rules: risk-first reading, bounded diffs and reproducible verification
质量与评审
Refactoring 工程规则
Refactoring rules: characterisation tests before structural change
质量与评审
Legacy Modernisation 工程规则
Legacy rules: strangler-fig slices with a measurable seam
质量与评审
Error Budget 工程规则
Reliability rules: error budgets gate feature work, not opinions