监控与告警
structured-logging-migration
更新于 2026-10-08
Structured Logging · 迁移规则
Migration rules for Structured Logging: expand/contract phases, idempotent steps and rehearsed rollback.
- 技术栈
- Structured Logging
- 主题
- 迁移
- 条目
- 9 条
- 版本
- v0.2.0
✓ 应当这么做
- ✓ Split every breaking change into expand, migrate and contract phases
- ✓ Make the migration idempotent so a re-run is a no-op
- ✓ Rehearse on a production-shaped copy and record the rollback path
✕ 常见反模式
- ✕ Irreversible destructive steps in the same release as code removal
- ✕ Big-bang cutovers with no parallel running period
- ✕ Migrations that depend on manual console steps
◎ 交付前验证
- ◎ 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