Back to Details

delivery-manager

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Delivery Manager

交付经理

Expert-level delivery management for continuous software delivery.
面向软件持续交付的专业级交付管理。

Core Competencies

核心能力

  • Release management
  • Deployment coordination
  • Continuous delivery
  • Service operations
  • Incident management
  • Change management
  • Capacity planning
  • SLA management
  • 发布管理
  • 部署协调
  • 持续交付
  • 服务运维
  • 事件管理
  • 变更管理
  • 容量规划
  • SLA管理

Delivery Framework

交付框架

Delivery Pipeline

交付流水线

CODE → BUILD → TEST → STAGE → DEPLOY → MONITOR
  │       │       │       │        │        │
  ▼       ▼       ▼       ▼        ▼        ▼
Commit  Compile  Unit   Integr   Prod    Observe
Review  Package  Integr  UAT     Canary   Alert
Lint    Artifact Perf   Approval Blue/Grn Respond
CODE → BUILD → TEST → STAGE → DEPLOY → MONITOR
  │       │       │       │        │        │
  ▼       ▼       ▼       ▼        ▼        ▼
Commit  Compile  Unit   Integr   Prod    Observe
Review  Package  Integr  UAT     Canary   Alert
Lint    Artifact Perf   Approval Blue/Grn Respond

Delivery Maturity Model

交付成熟度模型

LEVEL 1: Manual Delivery
├── Manual builds
├── Manual testing
├── Manual deployments
└── Reactive monitoring

LEVEL 2: Automated Build/Test
├── CI pipeline
├── Automated unit tests
├── Manual deployments
└── Basic monitoring

LEVEL 3: Continuous Delivery
├── Full CI/CD pipeline
├── Automated testing
├── Push-button deployments
└── Comprehensive monitoring

LEVEL 4: Continuous Deployment
├── Automated deployments
├── Feature flags
├── Canary releases
└── Self-healing systems

LEVEL 5: DevOps Excellence
├── Zero-downtime deployments
├── Automated rollbacks
├── Chaos engineering
└── Full observability
LEVEL 1: Manual Delivery
├── Manual builds
├── Manual testing
├── Manual deployments
└── Reactive monitoring

LEVEL 2: Automated Build/Test
├── CI pipeline
├── Automated unit tests
├── Manual deployments
└── Basic monitoring

LEVEL 3: Continuous Delivery
├── Full CI/CD pipeline
├── Automated testing
├── Push-button deployments
└── Comprehensive monitoring

LEVEL 4: Continuous Deployment
├── Automated deployments
├── Feature flags
├── Canary releases
└── Self-healing systems

LEVEL 5: DevOps Excellence
├── Zero-downtime deployments
├── Automated rollbacks
├── Chaos engineering
└── Full observability

Release Management

发布管理

Release Planning

发布计划

markdown
undefined
markdown
undefined

Release Plan: v2.5.0

发布计划：v2.5.0

Release Overview

发布概述

  • Version: 2.5.0
  • Type: Minor Release (new features)
  • Target Date: January 25, 2024
  • Release Manager: [Name]
  • 版本：2.5.0
  • 类型：次要版本发布（新增功能）
  • 目标日期：2024年1月25日
  • 发布经理：[姓名]

Scope

范围

Features

功能

IDFeatureOwnerStatus
F-101New checkout flowTeam AReady
F-102Performance improvementsTeam BReady
F-103Admin dashboard updatesTeam CIn Testing
ID功能负责人状态
F-101新结账流程Team A已就绪
F-102性能优化Team B已就绪
F-103管理控制台更新Team C测试中

Bug Fixes

Bug修复

IDDescriptionPriorityStatus
B-201Cart total calculationHighFixed
B-202Login timeout issueMediumFixed
ID描述优先级状态
B-201购物车总额计算问题高已修复
B-202登录超时问题中已修复

Dependencies

依赖项

  • Database migration required
  • API version update
  • Third-party SDK update
  • 需要数据库迁移
  • API版本更新
  • 第三方SDK更新

Release Criteria

发布标准

Exit Criteria

退出标准

  • All P1/P2 bugs resolved
  • Performance benchmarks met
  • Security scan passed
  • Load testing complete
  • UAT sign-off received
  • Documentation updated
  • Runbook reviewed
  • 所有P1/P2级Bug已解决
  • 达到性能基准要求
  • 安全扫描通过
  • 负载测试完成
  • 收到UAT验收确认
  • 文档已更新
  • 运行手册已审核

Go/No-Go Decision

上线/不上线决策

  • Decision date: January 24, 2024
  • Decision maker: Release Manager + Product Owner
  • Criteria: All exit criteria met
  • 决策日期：2024年1月24日
  • 决策人：发布经理 + 产品负责人
  • 标准：满足所有退出标准

Rollout Strategy

发布策略

  • Deployment window: January 25, 10:00-14:00 UTC
  • Method: Blue-green deployment
  • Rollback plan: Immediate switch to blue environment
  • 部署窗口：2024年1月25日 10:00-14:00 UTC
  • 方式：蓝绿部署
  • 回滚计划：立即切换至Blue环境

Communication Plan

沟通计划

WhenWhoWhat
T-7 daysInternal teamsRelease scope finalized
T-1 dayAll stakeholdersGo/No-Go decision
T-0Customer successRelease notes
T+1 dayCustomersChangelog email
时间受众内容
提前7天内部团队发布范围最终确定
提前1天所有利益相关方上线/不上线决策结果
发布当日客户成功团队发布说明
发布后1天客户更新日志邮件

Post-Release

发布后

  • Monitoring period: 24 hours
  • Success metrics: Error rate <0.1%, latency P99 <500ms
  • Retrospective: January 26, 2024
undefined
  • 监控周期：24小时
  • 成功指标：错误率<0.1%，P99延迟<500ms
  • 回顾会议：2024年1月26日
undefined

Release Calendar

发布日历

RELEASE CALENDAR - Q1 2024

January
  Week 1    Week 2    Week 3    Week 4
  ─────────────────────────────────────
  Code      Testing   UAT       Release
  Freeze    Phase     Phase     v2.5.0
  v2.5                          ◆

February
  Week 1    Week 2    Week 3    Week 4
  ─────────────────────────────────────
  Dev       Code      Testing   Release
  Sprint    Freeze    Phase     v2.6.0
            v2.6                ◆

RELEASE TYPES
◆ Major Release (quarterly)
● Minor Release (monthly)
○ Patch Release (as needed)
RELEASE CALENDAR - Q1 2024

January
  Week 1    Week 2    Week 3    Week 4
  ─────────────────────────────────────
  Code      Testing   UAT       Release
  Freeze    Phase     Phase     v2.5.0
  v2.5                          ◆

February
  Week 1    Week 2    Week 3    Week 4
  ─────────────────────────────────────
  Dev       Code      Testing   Release
  Sprint    Freeze    Phase     v2.6.0
            v2.6                ◆

RELEASE TYPES
◆ Major Release (quarterly)
● Minor Release (monthly)
○ Patch Release (as needed)

Version Management

版本管理

SEMANTIC VERSIONING: MAJOR.MINOR.PATCH

MAJOR (X.0.0)
├── Breaking changes
├── Major features
└── Quarterly cadence

MINOR (x.X.0)
├── New features
├── Backward compatible
└── Monthly cadence

PATCH (x.x.X)
├── Bug fixes
├── Security patches
└── As needed
语义化版本：MAJOR.MINOR.PATCH

MAJOR (X.0.0)
├── 破坏性变更
├── 重大功能
└── 季度周期

MINOR (x.X.0)
├── 新增功能
├── 向后兼容
└── 月度周期

PATCH (x.x.X)
├── Bug修复
├── 安全补丁
└── 按需发布

Deployment Strategies

部署策略

Deployment Patterns

部署模式

Blue-Green Deployment:
┌─────────────────────────────────────────────────┐
│                  LOAD BALANCER                   │
└─────────────────────┬───────────────────────────┘
                      │
        ┌─────────────┴─────────────┐
        │                           │
        ▼                           ▼
┌───────────────┐           ┌───────────────┐
│  BLUE (v2.4)  │           │ GREEN (v2.5)  │
│   [Active]    │           │  [Staging]    │
│               │           │               │
│ ● ● ● ● ●     │           │ ● ● ● ● ●     │
│  5 instances  │           │  5 instances  │
└───────────────┘           └───────────────┘

SWITCH: Route traffic from Blue → Green
ROLLBACK: Route traffic from Green → Blue
Canary Deployment:
┌─────────────────────────────────────────────────┐
│               TRAFFIC DISTRIBUTION               │
├─────────────────────────────────────────────────┤
│                                                  │
│  Stage 1:  [█████████████████████████░] 95%/5%  │
│  Stage 2:  [████████████████████░░░░░░] 75%/25% │
│  Stage 3:  [██████████░░░░░░░░░░░░░░░░] 50%/50% │
│  Stage 4:  [░░░░░░░░░░░░░░░░░░░░░░░░░█] 0%/100% │
│                                                  │
│  ████ = Old Version    ░░░░ = New Version       │
└─────────────────────────────────────────────────┘
Rolling Deployment:
TIME →
────────────────────────────────────────────────────
t0:  [v1][v1][v1][v1][v1]  All instances v1
t1:  [v2][v1][v1][v1][v1]  1 instance updated
t2:  [v2][v2][v1][v1][v1]  2 instances updated
t3:  [v2][v2][v2][v1][v1]  3 instances updated
t4:  [v2][v2][v2][v2][v1]  4 instances updated
t5:  [v2][v2][v2][v2][v2]  All instances v2
蓝绿部署：
┌─────────────────────────────────────────────────┐
│                  LOAD BALANCER                   │
└─────────────────────┬───────────────────────────┘
                      │
        ┌─────────────┴─────────────┐
        │                           │
        ▼                           ▼
┌───────────────┐           ┌───────────────┐
│  BLUE (v2.4)  │           │ GREEN (v2.5)  │
│   [Active]    │           │  [Staging]    │
│               │           │               │
│ ● ● ● ● ●     │           │ ● ● ● ● ●     │
│  5 instances  │           │  5 instances  │
└───────────────┘           └───────────────┘

SWITCH: Route traffic from Blue → Green
ROLLBACK: Route traffic from Green → Blue
金丝雀部署：
┌─────────────────────────────────────────────────┐
│               TRAFFIC DISTRIBUTION               │
├─────────────────────────────────────────────────┤
│                                                  │
│  Stage 1:  [█████████████████████████░] 95%/5%  │
│  Stage 2:  [████████████████████░░░░░░] 75%/25% │
│  Stage 3:  [██████████░░░░░░░░░░░░░░░░] 50%/50% │
│  Stage 4:  [░░░░░░░░░░░░░░░░░░░░░░░░░█] 0%/100% │
│                                                  │
│  ████ = Old Version    ░░░░ = New Version       │
└─────────────────────────────────────────────────┘
滚动部署：
TIME →
────────────────────────────────────────────────────
t0:  [v1][v1][v1][v1][v1]  All instances v1
t1:  [v2][v1][v1][v1][v1]  1 instance updated
t2:  [v2][v2][v1][v1][v1]  2 instances updated
t3:  [v2][v2][v2][v1][v1]  3 instances updated
t4:  [v2][v2][v2][v2][v1]  4 instances updated
t5:  [v2][v2][v2][v2][v2]  All instances v2

Deployment Checklist

部署检查清单

markdown
undefined
markdown
undefined

Deployment Checklist

部署检查清单

Pre-Deployment

部署前

  • All tests passing
  • Security scan complete
  • Change request approved
  • Runbook reviewed
  • Rollback plan documented
  • Communication sent
  • On-call team notified
  • Maintenance window confirmed
  • 所有测试通过
  • 安全扫描完成
  • 变更请求已批准
  • 运行手册已审核
  • 回滚计划已文档化
  • 已发送沟通通知
  • 值班团队已收到通知
  • 维护窗口已确认

Deployment

部署中

  • Database backup complete
  • Configuration verified
  • Health checks configured
  • Deployment initiated
  • Progress monitored
  • Health checks passing
  • Smoke tests passing
  • 数据库备份完成
  • 配置已验证
  • 健康检查已配置
  • 已启动部署
  • 正在监控部署进度
  • 健康检查通过
  • 冒烟测试通过

Post-Deployment

部署后

  • All services healthy
  • Metrics within thresholds
  • No increase in errors
  • User acceptance verified
  • Documentation updated
  • Stakeholders notified
  • Change request closed
  • 所有服务运行正常
  • 指标在阈值范围内
  • 错误率未上升
  • 用户验收已验证
  • 文档已更新
  • 已通知利益相关方
  • 变更请求已关闭

Rollback Triggers

回滚触发条件

  • Error rate > 1%
  • Latency P99 > 2s
  • Health check failures
  • Critical bug discovered
undefined
  • 错误率>1%
  • P99延迟>2s
  • 健康检查失败
  • 发现严重Bug
undefined

Incident Management

事件管理

Incident Response

事件响应

INCIDENT SEVERITY LEVELS

SEV-1: Critical
├── Complete service outage
├── Data loss or security breach
├── Response: Immediate (15 min)
└── Resolution target: 4 hours

SEV-2: High
├── Major feature unavailable
├── Significant performance degradation
├── Response: 30 minutes
└── Resolution target: 8 hours

SEV-3: Medium
├── Minor feature impact
├── Workaround available
├── Response: 2 hours
└── Resolution target: 24 hours

SEV-4: Low
├── Cosmetic issues
├── No customer impact
├── Response: 8 hours
└── Resolution target: 5 days
事件严重等级

SEV-1：关键
├── 服务完全中断
├── 数据丢失或安全漏洞
├── 响应要求：立即响应（15分钟内）
└── 解决目标：4小时内

SEV-2：高
├── 主要功能不可用
├── 性能严重下降
├── 响应要求：30分钟内
└── 解决目标：8小时内

SEV-3：中
├── 次要功能受影响
├── 存在可行的替代方案
├── 响应要求：2小时内
└── 解决目标：24小时内

SEV-4：低
├── 界面显示问题
├── 无客户影响
├── 响应要求：8小时内
└── 解决目标：5天内

Incident Process

事件处理流程

DETECT → TRIAGE → RESPOND → RESOLVE → REVIEW
   │        │         │         │         │
   ▼        ▼         ▼         ▼         ▼
Alert    Assess    Incident   Fix &    Post-
Fire     Severity  Commander  Verify   mortem
Monitor  Assign    Coordinate Deploy   Action
Page     Notify    Communicate Test    Items
检测 → 分类 → 响应 → 解决 → 回顾
   │        │         │         │         │
   ▼        ▼         ▼         ▼         ▼
告警    评估    事件指挥    修复并    事后
监控    严重等级    协调    验证部署    复盘
通知    分配责任人    沟通    测试    行动项

Incident Template

事件报告模板

markdown
undefined
markdown
undefined

Incident Report: INC-2024-0125

事件报告：INC-2024-0125

Summary

摘要

[One sentence description of the incident]
[事件的一句话描述]

Timeline

时间线

Time (UTC)Event
10:15Alert triggered
10:18On-call paged
10:25Incident declared
10:45Root cause identified
11:00Fix deployed
11:15Service restored
时间（UTC）事件
10:15触发告警
10:18通知值班人员
10:25宣布事件发生
10:45确定根本原因
11:00部署修复方案
11:15服务恢复正常

Impact

影响

  • Duration: 1 hour
  • Affected services: [List]
  • Customer impact: [Description]
  • SLA impact: [Yes/No, details]
  • 持续时间：1小时
  • 受影响服务：[列表]
  • 客户影响：[描述]
  • SLA影响：[是/否，详情]

Root Cause

根本原因

[Description of what caused the incident]
[事件原因描述]

Resolution

解决方案

[What was done to resolve the incident]
[解决事件的措施]

Action Items

行动项

ActionOwnerDue DateStatus
[Action 1][Name][Date]Open
[Action 2][Name][Date]Open
行动负责人截止日期状态
[行动1][姓名][日期]未开始
[行动2][姓名][日期]未开始

Lessons Learned

经验总结

  • What went well: [List]
  • What could improve: [List]
  • Follow-up items: [List]
undefined
  • 做得好的地方：[列表]
  • 需要改进的地方：[列表]
  • 后续跟进项：[列表]
undefined

Change Management

变更管理

Change Types

变更类型

TypeDescriptionApprovalLead Time
StandardPre-approved, low riskNone0
NormalRegular changeCAB5 days
ExpeditedUrgent business needManager24 hours
EmergencyCritical fixOn-call0
类型描述审批要求前置时间
标准变更预批准、低风险无0
常规变更常规变更CAB审批5天
加急变更紧急业务需求经理审批24小时
应急变更关键修复值班人员审批0

Change Request

变更请求

markdown
undefined
markdown
undefined

Change Request: CHG-2024-0150

变更请求：CHG-2024-0150

Change Details

变更详情

  • Title: Database schema migration
  • Type: Normal
  • Risk: Medium
  • Environment: Production
  • 标题：数据库 schema 迁移
  • 类型：常规变更
  • 风险：中等
  • 环境：生产环境

Requestor

请求人

  • Name: [Name]
  • Team: [Team]
  • Date: January 20, 2024
  • 姓名：[姓名]
  • 团队：[团队]
  • 日期：2024年1月20日

Description

描述

[Detailed description of the change]
[变更的详细说明]

Justification

理由

[Business reason for the change]
[变更的业务原因]

Impact Analysis

影响分析

  • Systems affected: [List]
  • Services affected: [List]
  • Users affected: [Number]
  • Downtime required: [Duration]
  • 受影响系统：[列表]
  • 受影响服务：[列表]
  • 受影响用户数：[数量]
  • 所需停机时间：[时长]

Implementation Plan

实施计划

  1. [Step 1]
  2. [Step 2]
  3. [Step 3]
  1. [步骤1]
  2. [步骤2]
  3. [步骤3]

Rollback Plan

回滚计划

  1. [Rollback step 1]
  2. [Rollback step 2]
  1. [回滚步骤1]
  2. [回滚步骤2]

Testing Plan

测试计划

  • Unit tests
  • Integration tests
  • UAT sign-off
  • 单元测试
  • 集成测试
  • UAT验收

Schedule

时间表

  • Proposed date: January 25, 2024
  • Start time: 02:00 UTC
  • Duration: 2 hours
  • Change freeze exception: No
  • 拟议日期：2024年1月25日
  • 开始时间：02:00 UTC
  • 持续时间：2小时
  • 是否为变更冻结例外：否

Approvals

审批

RoleNameStatusDate
Technical LeadPending
Product OwnerPending
CABPending
undefined
角色姓名状态日期
技术负责人待审批
产品负责人待审批
CAB待审批
undefined

SLA Management

SLA管理

SLA Framework

SLA框架

┌─────────────────────────────────────────────────────────────────┐
│                        SLA DASHBOARD                             │
├─────────────────────────────────────────────────────────────────┤
│  Service: Customer Portal     Period: January 2024              │
├─────────────────────────────────────────────────────────────────┤
│  AVAILABILITY                                                    │
│  Target: 99.9%    Actual: 99.95%    Status: ✓ Met              │
│  Downtime allowed: 43.8 min    Used: 21.6 min    Remaining: ✓  │
├─────────────────────────────────────────────────────────────────┤
│  PERFORMANCE                                                     │
│  Latency P99 Target: <500ms    Actual: 320ms    Status: ✓ Met  │
│  Error Rate Target: <0.1%      Actual: 0.05%    Status: ✓ Met  │
├─────────────────────────────────────────────────────────────────┤
│  SUPPORT                                                         │
│  SEV-1 Response Target: 15 min    Avg: 12 min    Status: ✓ Met │
│  SEV-2 Response Target: 30 min    Avg: 25 min    Status: ✓ Met │
└─────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────┐
│                        SLA DASHBOARD                             │
├─────────────────────────────────────────────────────────────────┤
│  Service: Customer Portal     Period: January 2024              │
├─────────────────────────────────────────────────────────────────┤
│  可用性                                                         │
│  目标：99.9%    实际：99.95%    状态：✓ 达成              │
│  允许停机时间：43.8分钟    已使用：21.6分钟    剩余：✓  │
├─────────────────────────────────────────────────────────────────┤
│  性能                                                           │
│  P99延迟目标：<500ms    实际：320ms    状态：✓ 达成  │
│  错误率目标：<0.1%      实际：0.05%    状态：✓ 达成  │
├─────────────────────────────────────────────────────────────────┤
│  支持                                                           │
│  SEV-1响应目标：15分钟    平均：12分钟    状态：✓ 达成 │
│  SEV-2响应目标：30分钟    平均：25分钟    状态：✓ 达成 │
└─────────────────────────────────────────────────────────────────┘

Error Budget

错误预算

ERROR BUDGET CALCULATION

SLA: 99.9% availability
Error Budget: 0.1% = 43.8 minutes/month

BUDGET CONSUMPTION
├── Incident 1: 15 min
├── Incident 2: 5 min
├── Maintenance: 0 min (scheduled)
└── Total used: 20 min

REMAINING BUDGET
└── 23.8 min (54% remaining)

BURN RATE
└── Current: 0.8x (on track)
错误预算计算

SLA：99.9%可用性
错误预算：0.1% = 每月43.8分钟

预算消耗
├── 事件1：15分钟
├── 事件2：5分钟
├── 维护：0分钟（已计划）
└── 总消耗：20分钟

剩余预算
└── 23.8分钟（剩余54%）

消耗速率
└── 当前：0.8x（符合预期）

Metrics & Reporting

指标与报告

Delivery Metrics

交付指标

MetricDefinitionTarget
Deployment FrequencyDeploys per day/week10+/week
Lead TimeCommit to production<1 day
Change Failure RateFailed deployments<5%
MTTRMean time to recovery<1 hour
AvailabilityUptime percentage99.9%
指标定义目标
部署频率每日/每周部署次数每周10+次
前置时间代码提交到生产环境的时间<1天
变更失败率部署失败的比例<5%
MTTR（平均恢复时间）平均故障恢复时间<1小时
可用性在线时间占比99.9%

Delivery Dashboard

交付仪表盘

┌─────────────────────────────────────────────────────────────────┐
│              DELIVERY PERFORMANCE - [Month]                      │
├─────────────────────────────────────────────────────────────────┤
│  Deployments     Lead Time      Failure Rate      MTTR          │
│  48              4.2 hours      2.1%              45 min        │
│  +20% MoM        -30% MoM       -1% MoM           -15 min MoM   │
├─────────────────────────────────────────────────────────────────┤
│  DEPLOYMENT TREND                                                │
│  [Line chart showing deployments over time]                     │
├─────────────────────────────────────────────────────────────────┤
│  INCIDENT SUMMARY                                                │
│  Total: 5    SEV-1: 0    SEV-2: 2    SEV-3: 3                  │
│  MTTR: 45 min    MTTD: 5 min                                    │
├─────────────────────────────────────────────────────────────────┤
│  UPCOMING RELEASES                                               │
│  v2.6.0: Feb 28    v2.7.0: Mar 28    v3.0.0: Apr 30            │
└─────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────┐
│              DELIVERY PERFORMANCE - [Month]                      │
├─────────────────────────────────────────────────────────────────┤
│  Deployments     Lead Time      Failure Rate      MTTR          │
│  48              4.2 hours      2.1%              45 min        │
│  +20% MoM        -30% MoM       -1% MoM           -15 min MoM   │
├─────────────────────────────────────────────────────────────────┤
│  部署趋势                                                │
│  [折线图展示部署随时间的变化]                     │
├─────────────────────────────────────────────────────────────────┤
│  事件汇总                                                │
│  总计：5    SEV-1：0    SEV-2：2    SEV-3：3                  │
│  MTTR：45分钟    MTTD（平均检测时间）：5分钟                                    │
├─────────────────────────────────────────────────────────────────┤
│  即将发布版本                                               │
│  v2.6.0: Feb 28    v2.7.0: Mar 28    v3.0.0: Apr 30            │
└─────────────────────────────────────────────────────────────────┘

Reference Materials

参考资料

  • references/release_process.md
    - Release management guide
  • references/deployment_patterns.md
    - Deployment strategies
  • references/incident_management.md
    - Incident response
  • references/sla_management.md
    - SLA framework
  • references/release_process.md
    - 发布管理指南
  • references/deployment_patterns.md
    - 部署策略
  • references/incident_management.md
    - 事件响应
  • references/sla_management.md
    - SLA框架

Scripts

脚本

bash
undefined
bash
undefined

Release readiness checker

Release readiness checker

python scripts/release_checker.py --version v2.5.0
python scripts/release_checker.py --version v2.5.0

Deployment coordinator

Deployment coordinator

python scripts/deploy.py --env production --strategy canary
python scripts/deploy.py --env production --strategy canary

SLA calculator

SLA calculator

python scripts/sla_calculator.py --service portal --period month
python scripts/sla_calculator.py --service portal --period month

Incident reporter

Incident reporter

python scripts/incident_report.py --id INC-2024-0125
undefined
python scripts/incident_report.py --id INC-2024-0125
undefined