Payments/Bets-de SLO-burn alertleri

Amal ýol kartasy

1) Bu näme üçin zerur?

Operasiýa ýol kartasy (Ops Roadmap) SRE/platforma/goldaw we domen buýruklarynyň bölünen meselelerini aç-açan meýilnama öwürýär: SLO/bahasy/hadysalara her çärýekde nähili täsir ederis we haýsy bahadan (adamlar, wagt, býudjet). Bu bolsa bulam-bujarlygy peseldýär, tehniki borjuny tertipleşdirýär we işewürlige gymmatlygyň berilmegini çaltlaşdyrýar.

• Ölçülip bilinýän netijeleriň töwereginde başlangyçlary birleşdirmek (SLO, MTTR, Cost/RPS, Risk).
• Platforma, domenler we daşarky üpjün edijiler arasynda ileri tutulýan ugurlary utgaşdyrmak.
• Resurslary býudjet etmek we "näme etmeýändigimizi" düzetmek (aç-açan söwda-off).
• Ýerine ýetirilişi we töwekgelçilikleri barada ýeke-täk hakykaty saklamak.

2) Ýol kartasynyň ýörelgeleri

1. Outcome-first: Her başlangyç netijäniň metrikasyna baglydyr ("X-ni girizmek" däl-de, "MTTR-ni 20% azaltmak").
2. SLO-aware: Möhüm ýollaryň SLO-syna täsir edýän başlangyçlar (depozit/stawka/oýun/KUS) ileri tutulýar.
3. Data-driven: hadysalara, postmortemlere, aladalara, Capacity/FinOps panellerine bil baglaýarys.
4. Wagt-boxed & reversible: kiçijik inkrementler, gipotezalary barlamak, çalt yza gaýdyp gelmek.
5. Single source of truth: ýekeje artefakt, yzygiderli gykylyk we köpçülige açyk statuslar.
6. No hidden work: kartadan daşary - diňe düzgünnama laýyklykda "ýangynlar".

3) Roadmap çarçuwasy: derejeler we artefaktlar

Görüş (12-18 aý): 3-5 operasiýa temasy (Reliability, Scale, Cost, Security, Automation).
Sütünler (6-12 aý): mowzuklar boýunça başlangyçlar bloklary (mysal üçin "SLO-100% kritiki ýollary ýapmak", "2 sebitde Active-Active").
Çärýek meýilnamasy (Q): metrikler, eýeler, garaşlylyk, býudjet bilen anyk başlangyçlar.
Yterasiýalar (2-3 hepde): meseleler/epikler we hakyky ösüş.

ID: OPS-23

4) Prioritization: How to compare the incomparable

4. 1 RICE (Reach, Impact, Confidence, Effort)

Reach: affected users/transactions/geo.
Impact: expected contribution to SLO/MTTR/Cost.
Confidence: Confidence in estimates (data/pilots).
Effort: man-weeks/calendar window/dependencies.

4. 2 WSJF (Scaled)

Cost of Delay = (SLO Risk + Revenue Impact + Compliance + Incident Rate)
/ Job Size = duration/force.
Suitable for mixed initiatives (technical debt, security, platform features).

The rule: initiatives with high SLO risk and high cost of delay come first, even if the effect is "invisible" on UI.

5) Relationship with OKR, SLO and incidents

Platform-level OKR:
KR1: "Reduce Change Failure Rate from 18% to 12% by the end of Q2."
KR2: "Increase Pre-Incident Detect Rate from 35% to 60%."
SLO-matrix: for each domain - target p95/p99/Success Rate/Availability.
Incident analytics: the top 3 reasons for the last quarter should have counteraction initiatives in the current one.

6) Resource and budget planning

FTE-matrix: by squads and competencies (SRE, Observability, Data, Integrations).
Provider calendar: maintenance/quota windows (impact on dates).
CapEx/OpEx: licenses/cluster extensions vs command hours.
Buffer: ~ 15-20% for unplanned "fires" and regulatory tasks.
What-don't-do policy: A list of rescheduled/postponed initiatives with reasons.

7) Managing dependencies and risks

Dependency map: who blocks whom (service/provider/data/command).
Risk register: risk, probability/impact, owner, mitigation plan/plan B.
Change freeze: periods of prohibition of major changes (prime time events/tournaments).
Ficheflags/canaries: Mandatory for initiatives affecting traffic.

8) Quarterly cycle (rhythms)

Q-0 (preparation, 2 weeks): data collection (SLO, incidents, costs), revision of topics, preliminary prioritization.
Q planning: protection of initiatives by owners, reconciliation of resources/risks, fixing the Q plan and "not doing" the list.
Weekly sync: status, blockers, adjustments; maximum 30 minutes.
Monthly review: checking effects on metrics, possible re-scope.
Q retro: compare plan/fact, update principles/patterns.

9) Roadmap view formats

Outcome View: grouped by purpose (SLO, Cost, Risk).
Domain View: Payments/Bets/Games/KYC/Platform.
Timeline View: quarterly, with dependency and frieze markers.
Budget View: FTE/CapEx/OpEx by Initiative and Topic.

Example of a quarterly slice (summary):
Initiative     Outcome              Metrics     Term     Owner     Risk
--------------------      -----------------------      --------------------      -----      -------------      -------
Active-Active Games     RTO≤5 min     Availability 99. 95%      Q1–Q2      platform-sre      High
SLO-burn на Payments     − 30% of late incidents     Pre-Incident↑, MTTR↓      Q1       observability      Average
Kafka Lag Guardrails     − 50% of lag storms     Lag p95↓, DLQ↑         Q1       streaming        Average
FinOps Right-sizing      −15% cost/RPS           Cost/RPS↓           Q2       finops         Low

10) Roadmap Success Metrics (KPIs)

Delivery Predictability: percentage of initiatives completed on time (target ≥ 80%).
SLO Coverage:% of critical paths with active SLOs/alerts.
Incident Trend: − X% of P1/P2 QoQ incidents
Change Failure Rate: Target decline by quarter.
Cost Efficiency: Cost/RPS, Cost/transaction - downward trend.
Risk Burn-down: the number of "red" risks and their total weight.
Stakeholder NPS: satisfaction of domain teams with the quality of the Roadmap.

11) Roadmap launch checklist

[] Defined themes/pillars and 3-5 target outcomes per year.
[] Catalog of initiatives linked to metrics and owners.
[] Prioritization methodology (RICE/WSJF) and scales adopted.
[] Checked resources: FTE, provider windows, budgets.
[] Fixed Q-plan + "not doing."
[] Set up Outcome/Domain/Budget panels, alerts by shifts.
[] Review Schedule: weekly/monthly/quarterly.

12) Anti-patterns

List of tasks without outcomes: "make X" instead of "achieve Y by metric."
Hidden initiatives and private arrangements outside of a single artifact.
Eternal epics: no time-box, no verifiable milestones.
Priority "in terms of volume": resources are spent on the "loudest" request, and not on the most valuable one.
No "what not to do": expectations are unmanageable, trust is falling.
Lack of a link with incidents/SLO: "cosmetic" improvements instead of real ones.

13) Templates (fragments)

Initiative Template (YAML):

yaml id: OPS-42 title: "Kanaryalar üçin Guardrails"

theme: "Reliability"

quarter: "2025-Q1"

owner: "platform-release"

stakeholders: ["payments", "bets", "games"]

outcome: "Çykarylandan soň regressiýalary 40% azaltmak"

• name: change_failure_rate target: "<= 12%"
• name: post_deploy_regression_rate target: "-40% QoQ"
• slo_impact: ["api_p99 <= 300ms@99. 9", "availability >= 99. 95%"]

• reach: 5000000 # geleşikler/kw impact: 3. 0 confidence: 0. 7 effort: 6 dependencies: ["observability-baseline", "feature-flags-core"]

• name: "geýtleriň ýalan açylmagy"
• mitigation: "baseline/tuning, traffigiň 10% piloty"

• name: design eta: "2025-01-20"
• name: pilot-10%
• eta: "2025-02-10"
• name: rollout-100%
• eta: "2025-03-05"

Quarterly report template (Markdown):

Q1 Ops Roadmap - Hasabat

Netijeleriň jemleri: SLO Coverage 92% (+ 7 p.p.), MTTR − 18%, Cost/RPS − 9%

Ýerine ýetirildi: 8/10 başlangyç (80%)

Süýşmeler: OPS-31 → Q2 (PSP-X üpjün edijisine garaşlylyk)

Hadysalar: P1 = 2 (1 kw/kw −), esasy sebäpler: üpjün edijiniň wagtyndaky retralar

Follow-ups: breýkerleri sazlamak, PSP-Y ätiýaçlyk kwotalary

14) Prosesler bilen integrasiýa

Waka-dolandyryş: her postmortem → Roadmap-da inisiatiwa/gowulaşma bileti.
Üýtgeşmeler/goýberişler: iri başlangyçlar diňe baýdaklar/kanareýkalar bilen amala aşyrylýar.
Capacity/FinOps: aýda bir gezek headroom we cost-tendensiýalar boýunça sinhronizasiýa.
Howpsuzlyk/utgaşma: talaplar we barlaglar boýunça çärýekleýin gözegçilik nokatlary.

15) 30/60/90 (çalt başlamak)

30 gün: waka/metrik bazany ýygnamak, mowzuklary döretmek, YAML görnüşinde 10-15 başlangyçlary beýan etmek, RICE/WSJF saýlamak, Q-meýilnamasyny düzetmek.
60 gün: Outcome/Domain/Budget panellerini işe girizmek, ilkinji daşary çärýek synyny geçirmek, maglumatlar boýunça ileri tutulýan ugurlary düzmek.
90 gün: Q-jemleri jemlemek, ýörelgeleri we masştablary täzelemek, ýyllyk sütünleri gaýtadan bellemek.

16) Aragatnaşyk we aç-açanlyk

Steýkholderler üçin aýlyk syn: 30 minut, netijelere we töwekgelçiliklere üns.
Asinxron täzelenmeler: "öň/soň" metrikleri bilen gysga ýazgylar.
Roadmap bitewi kanaly: statuslar, üýtgeşmeler, ileri tutulýan ugurlar boýunça çözgütler.
"Gyzyl kartoçka" düzgüni: islendik topar maglumatlary (SLO/waka/bahasy) goşmak bilen ileri tutulýan ugruň täzeden gözden geçirilmegine başlap biler.

17) FAQ

Q: Hemme zat "ýakylsa" we Roadmap üçin wagt ýok bolsa näme etmeli?
A: Wakalaryň esasy sebäplerini ýapýan "ýangyn-bufer" 15-20% we iň az 3 başlangyçdan ybarat Q-meýilnamany goşuň. Islendik täze "gyzgyn" iş diňe ileri tutulýan ugurlary gaýtadan saýlamak arkaly amala aşyrylýar.

Q: "Görünmeýän" başlangyçlaryň (synlamak, awtogeýtler) gymmatyny nädip subut etmeli?
A: Change Failure Rate, MTTR, Pre-Incident Detect Rate, rebounds we "gijeki page" hasaplaň. Dinamikany öň/soň görkeziň.

Q: Tehniki bergi bilen näme etmeli?
A: Karz hem "− X% N synp hadysalary", "− Y% cost/RPS", "Z pp. SLO Coverage». Ölçülip bilinjek netije bolmasa, karz meýilnama girmeýär.