Quality Center

No recent CI run Last probe 11:06 UTC No recent security scan
All Runs
100 Health ?
Operational Health: Excellent
DORA: ELITE
Operational factors only — CI, DORA, probes, security, certificates. How is this calculated?
OK
Release Gate
Architecture
experimental
N/A
CI Success Rate
0/25
N/A
Change Failure Rate
0/20
N/A
Endpoint Uptime
0/20
N/A
Security (Critical/High)
0/15
N/A
Test Stability
0/10
0
Certificate Health
10/10
Show score breakdown (1/6 factors active, 5 N/A)
Factor Norm Weighted
CI Success Rate (N/A) 0 0/25
Change Failure Rate (N/A) 0 0/20
Endpoint Uptime (N/A) 0 0/20
Security (Critical/High) (N/A) 0 0/15
Test Stability (N/A) 0 0/10
Certificate Health 1 10/10
Total 10/10 = 100
final = (sum(weighted_scores) / active_weight_total) * 100
Release Allowed — all blocking gates passed
4 advisory notices remain (non-blocking).
✓ Verified (Confidence: 100%) - Click to expand
✓ VERIFIED & ALLOWED
No telemetry signals available yet. Policy allows release (bootstrap/greenfield). Confidence: 0 (no data).
Release Allowed
Yes (policy)
Snapshot Verified
Yes (cryptographic)
Release ID: b603c352e8064c3f | Signals: 0/4
100
CONFIDENCE
Predictive: +5
ci
○ Absent
slo
○ Absent
probes
○ Absent
budget
○ Absent
Confidence 100/100 because . Signals: [PROD mode (baseline 100 - ship-without-review tier)] Predictive adjustment: +5-0
Snapshot Hashes (Evidence Binding)
ci: 09a948841aababc2...
slo: 0d489e9186646c64...
probes: e7994a18311ef2d4...
budget: 16a9cf6c46749678...
✓ Error Budget (100%)
✓ Burn Rate
? Security (no data)
✓ CI
? Probes (none)
Top Risky Services 0
All services healthy
Incidents (24h) 0 active
0
Total 24h
0
Critical
Avg MTTR
Service Health Cards 0 services
No services registered. Services appear automatically when SLOs are configured.
Service Coverage
Loading services...
CI Quality Gates
🔍
No CI runs found
Connect GitHub Workflow
DORA Metrics
0
Deploy/Day
No data
-
Lead Time
No data
-
Failure Rate
No data
-
MTTR
No data
No deployments recorded in the last 30 days
Predictive Risk Signals FORWARD-LOOKING
Budget Exhaustion ETA
>90d
Current burn: 0%/day
Capacity Saturation
Low Risk
CPU trend: stable | Latency: healthy
Highest Blast Radius
API Gateway
8 dependent services | MEDIUM risk
📈 Forward-Looking Risk Timeline
7-day: ✓ OK
30-day: ✓ OK
Projection: Linear trend (current burn rate)
Nightly Regression NON-GATING
🌙
No nightly runs found
Run First Nightly
Security Posture
Details All clear
0
Critical
0
High
0
Medium
0
Low
0
Fixed 7d
Release Gate Input: 0 crit / 0 high (unexempted only)
Synthetic Probes
Monitoring 0 targets No Data
📡
No synthetic probes configured
Add Synthetic Targets
SLO Compliance & Error Budget
Manage 0 SLOs
🎯
No SLOs defined yet

Define Service Level Objectives to track reliability and error budgets

Define SLOs
Recent Runs (10)
Type Branch Commit Status Duration Started Owner
PROVIDER_WORKFLOW_EVENT_COMPLIANCE Pass - Apr 15, 01:46 - Details
PROVIDER_USECASE_BOUNDARY Warning - Apr 15, 01:46 - Details
PROVIDER_UNIT_SYSTEM_COMPLIANCE Pass - Apr 15, 01:46 - Details
PROVIDER_SQL_EXTRACTION_GATE Pass - Apr 15, 01:46 - Details
PROVIDER_SECURITY_POSTURE Pass - Apr 15, 01:46 - Details
PROVIDER_SEARCH_HEALTH Pass - Apr 15, 01:46 - Details
PROVIDER_SCHEDULED_EVENT_ARCHITECTURE Pass - Apr 15, 01:46 - Details
PROVIDER_REPOSITORY_BOUNDARY Warning - Apr 15, 01:46 - Details
PROVIDER_RELATION_COMPLIANCE Pass - Apr 15, 01:46 - Details
PROVIDER_PROFILE_SYSTEM Pass - Apr 15, 01:46 - Details
Strategic Views (Executive, Debt, Impact)
Executive View Loading...
-
Health Score
-
Capabilities
-
Healthy
-
Attention
Quality Debt Loading...
-
Total Items
-
Critical
-
Overdue
-
Interest
Change Impact Loading...
-
Recent Changes
-
Avg Risk
-
Services
-
Suspects
📊 Monitoring ← Dashboard
⚙️ Quality Center Settings

📍 Source Monitoring Environment

Import services from this monitoring environment to auto-generate probes and SLOs.

Find Environment UUID in Monitoring Dashboard →

🚀 Import Services

Import all services from the source environment and auto-generate probe targets and default SLOs.

📈 Current Coverage

-
Services
-
Probes
-
SLOs
-
Score

🔧 Other Settings

Loading settings...
How Operational Health Score is Calculated

Score Components

FactorWeightNormalized ScoreDescription
CI Success Rate25success_rate / 100Percentage of CI runs that pass
Change Failure Rate20max(0, (50 - rate) / 50)DORA: % of deployments causing incidents (N/A if no deploys)
Endpoint Uptime20effective_uptime / 100Synthetic probe success rate adjusted for data freshness
Security Posture15max(0, (15 - issues*1.5) / 15)Penalty for critical/high vulnerabilities
Test Stability10(10 - flaky_count) / 10Penalty per flaky/unstable test
Certificate Health10(10 - expiring*5) / 10Penalty for expiring SSL certificates

Formula: weighted_score = clamp(normalized_score, 0, 1) × weight.
Final = (sum of weighted scores / sum of active weights) × 100.
Factors without data (N/A) are excluded from both numerator and denominator.

DORA Performance Levels

LevelDeploy FreqLead TimeFailure RateMTTR
EliteMultiple/day<1 hour<15%<1 hour
HighDaily-Weekly<1 week<30%<1 day
MediumWeekly-Monthly1-6 months30-45%<1 week
Low<Monthly>6 months>45%>1 week

Score Hierarchy

MetricDefinitionRange
Operational HealthWeighted composite of 6 operational factors: CI success, DORA CFR, probe uptime, security, test stability, and certificate health. Does NOT include architecture-advisory or compliance providers.0-100
Architecture AdvisoryAverage score of providers tagged 'architecture-advisory' (experimental maturity). Measures structural DDD/naming compliance via static analysis.0-100 or N/A
Release GateBinary pass/fail. Blocked if any provider with affectsReleaseGate=true has FAIL status.OK / BLOCKED / WARN
Global ScoreArithmetic mean of all active provider scores (quality section providers only)0-100
System HealthGlobal Score, but hard-capped at 70 if any critical-severity provider has FAIL status0-100 (max 70 if critical fail)

References

DORA Research - DevOps Research and Assessment
Google SRE - Service Level Objectives
OWASP DevSecOps - Security integration

Add Synthetic Probe Target
Define Service Level Objective (SLO)
Trigger Nightly Test Run
🌙
About Nightly Runs
Executes PHPUnit, Playwright E2E, PHPStan, and coverage reports.
⚠️ This action will be logged for audit purposes. Rate limit: 5 triggers per 5 minutes.
View all runs →
Enable Security Scanning
🔒
Security Integration
Detect vulnerabilities in code and dependencies.
Track Deployment