Dzaki Yaumal Console← Portfolio

Operations / Reliability

How well it runs.

Range
Live · 30s
Uptime target 99.9%99.986%86,295 checks over 30 days
Error budget used14%37m left
Mean time to recovery24m2 faults
Mean time between faults10d 7hlongest 48m

Response time by hour

Hot Work Permit · 30 days
00061218SunMonTueWedThuFriSat
FasterSlower30–155 ms

Response time distribution

Hot Work Permit
  • 0–50 ms65.4K
  • 50–100 ms19.3K
  • 100–200 ms1,375
  • 200–500 ms120
  • 500–1000 ms11
  • 1000–2000 ms98
  • 2000+ ms16

Certificates

checked each day
HostIssuerDays left
yaumalatsal.comLet's Encrypt43
pinglab.yaumalatsal.comLet's Encrypt43
baringan.yaumalatsal.comLet's Encrypt43
hotwork.yaumalatsal.comLet's Encrypt43
bisa.yaumalatsal.comLet's Encrypt43
simaksi.yaumalatsal.comLet's Encrypt44

All applications

worst budget first
ApplicationUptimeBudget usedFaultsMTTR
BISa LMS56.3%43684%154m
SIMAKSI56.4%43638%324m
Baringan Inventory56.4%43624%321m
PingLab LMS99.82%181%821m
Hot Work Permit99.986%14%224m
Portfolio & Console99.988%12%59m

The console measures the downtime across the period it watched, not across the whole window. A new application has a short history, so the page says how much of the window each figure covers. The console calculates the downtime from the health checks, not from the fault records. The checks are evenly spaced, so the ratio of bad checks is a fair estimate of the ratio of bad time. A fault record starts and ends on a check, so it would round each fault up to the check interval.