Auto-sync: 2026-04-24 04:02
This commit is contained in:
61
wiki/concepts/Early-Live-Support.md
Normal file
61
wiki/concepts/Early-Live-Support.md
Normal file
@@ -0,0 +1,61 @@
|
||||
---
|
||||
title: "Early Live Support"
|
||||
type: concept
|
||||
tags: [SRE, Cloud-Transformation, Go-Live, Support-Model]
|
||||
last_updated: 2026-04-14
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
Early Live Support(早期上线支持)是 Build(构建)与 BAU(日常运维)之间的过渡阶段。在这个阶段,SRE 团队与产品团队紧密协作,确保新服务平稳上线并建立持续运营的支持模式。
|
||||
|
||||
## Phase Overview
|
||||
|
||||
```
|
||||
Build ──────→ Early Live Support ──────→ BAU
|
||||
↑ ↑ ↑
|
||||
产品团队主导 ↑ SRE 主导
|
||||
SRE + 产品团队协作
|
||||
```
|
||||
|
||||
## Key Activities
|
||||
|
||||
### 1. Go-Live Checklist
|
||||
|
||||
Early Live Support 阶段需要完成以下检查清单:
|
||||
|
||||
| Item | Description |
|
||||
|------|-------------|
|
||||
| 监控覆盖 | 所有关键服务和基础设施都得到充分监控 |
|
||||
| 支持模型 | 明确 On-call Schedule 和升级路径 |
|
||||
| 事件响应流程 | 建立清晰的事件响应和升级流程 |
|
||||
| SLO/SLI 定义 | 定义服务等级目标和指标 |
|
||||
| 文档交接 | 完成技术文档和运维手册 |
|
||||
|
||||
### 2. SRE Collaboration
|
||||
|
||||
SRE 团队在此阶段:
|
||||
- 提供技术支持,协助解决上线问题
|
||||
- 验证监控和告警的有效性
|
||||
- 建立与产品团队的沟通渠道
|
||||
- 收集 BAU 阶段的运维需求
|
||||
|
||||
### 3. Handoff Criteria
|
||||
|
||||
从 Early Live Support 过渡到 BAU 的标准:
|
||||
- 所有监控面板正常运行
|
||||
- 事件响应流程经过演练
|
||||
- On-call Schedule 与 Service Desk 集成
|
||||
- 产品团队完成运维培训
|
||||
|
||||
## Relationship with SRE
|
||||
|
||||
Early Live Support 是 SRE 三阶段支持模型的关键环节:
|
||||
|
||||
1. **Build**:SRE 参与架构评审,定义 SLO/SLI
|
||||
2. **Early Live Support**:SRE 提供上线支持,确保平稳过渡
|
||||
3. **BAU**:SRE 提供持续监控和可靠性保障
|
||||
|
||||
## Sources
|
||||
|
||||
- [[ctp-topic-30-managing-change]]
|
||||
Reference in New Issue
Block a user