Dzaki Yaumal Console← Portfolio

Operations / Reliability

How well it runs.

Range
Live · 30s
Uptime target 99.9%99.82%86,296 checks over 30 days
Error budget used176%0s left
Mean time to recovery1m79 faults
Mean time between faults8h 32mlongest 49m

Response time by hour

PingLab LMS · 30 days
00061218SunMonTueWedThuFriSat
FasterSlower53–126 ms

Response time distribution

PingLab LMS
  • 0–50 ms28.4K
  • 50–100 ms52.7K
  • 100–200 ms4,844
  • 200–500 ms223
  • 500–1000 ms16
  • 1000–2000 ms74
  • 2000+ ms11

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.2%43811%154m
SIMAKSI56.2%43764%324m
Baringan Inventory56.2%43751%321m
PingLab LMS99.82%176%791m
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.