Skip to content

Service level objective monitoring#96

Merged
elizabetheonoja-art merged 2 commits into
Utility-Protocol:mainfrom
gloskull:Service-Level-Objective-Monitoring
Jul 18, 2026
Merged

Service level objective monitoring#96
elizabetheonoja-art merged 2 commits into
Utility-Protocol:mainfrom
gloskull:Service-Level-Objective-Monitoring

Conversation

@gloskull

Copy link
Copy Markdown
Contributor

Motivation
Provide a small, dependency-free SLO evaluation component that services can use to detect availability and latency regressions via burn-rate windows and to power alerting/dashboard labels.
Encode the shared objectives of 99.99% availability and <100 ms P99 latency and make canary/blue-green analysis simpler and auditable.
Description
Add meter-simulator/src/slo-monitor.js, a compact SLOMonitor implementation with DEFAULT_CONFIG (availabilityTarget 0.9999, latencyP99TargetMs 100) and multi-window burn-rate evaluation (fast and slow) plus evaluate, evaluateWindow, and buildAlert helpers.
Add unit tests in meter-simulator/tests/slo-monitor.test.js covering healthy windows, fast-window page alerts, latency SLO violations, and custom canary windows.
Add documentation docs/SLO_MONITORING.md describing objectives, architecture, burn-rate policy, blue-green/canary rollout guidance, and a security review checklist.
Testing
Ran the meter-simulator test suite with cd meter-simulator && npm test -- --runInBand slo-monitor.test.js, which passed: 1 test suite, 4 tests all succeeded.
The new module is exercised by the Jest tests SLOMonitor unit tests and the test run completed without failures.
Closes #88

@elizabetheonoja-art
elizabetheonoja-art merged commit 392b893 into Utility-Protocol:main Jul 18, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Service Level Objective Monitoring and Burn Rate Alerts

2 participants