监控与告警
structured-logging-debugging
更新于 2026-09-22
Structured Logging · 调试规则
Debugging rules for Structured Logging: minimal reproduction, one hypothesis per step and a regression test before the fix.
- 技术栈
- Structured Logging
- 主题
- 调试
- 条目
- 9 条
- 版本
- v0.2.0
✓ 应当这么做
- ✓ Reproduce with the smallest input that still fails
- ✓ Bisect by evidence: logs, traces, and a single hypothesis per step
- ✓ Write the regression test before fixing the cause
✕ 常见反模式
- ✕ Changing several things at once to "see if it helps"
- ✕ Closing an issue on a flaky repro without a test
- ✕ Silencing the symptom instead of removing the cause
◎ 交付前验证
- ◎ The new code path is visible in logs end-to-end
- ◎ Dashboard panel added or updated to match the new metric
- ◎ Alert routing tested once end-to-end
同分类条目
9 篇监控与告警
Monitoring & Alerts 工程规则
Alerting rules: symptom-based signals with an owner and a runbook
监控与告警
Structured Logging 工程规则
Logging rules: correlation ids, bounded fields and no personal payloads
监控与告警
Distributed Tracing 工程规则
Tracing rules: propagator consistency and cardinality-safe span names
监控与告警
Incident Runbook 工程规则
Runbook rules: detection, mitigation and evidence capture per incident class