DevSecOps · 03 of 5
SRE & observability
Telemetry into one view, SLOs and error budgets, the incident loop and reference response times.
01
Telemetry, SLOs and the incident loop
Open-standard telemetry into one view; SLOs decide what pages; every incident ends in a fix shipped as code.
SRE & Observability Stack
Point at a component to light its links; select it for what it does here and the practice that makes it right.
02
The reliability loop
SRE turns "keep it running" into targets the business agrees to. We set them with you and run the loop.
SLOsagreed with the business
Step 1 of 6
Define
SLIs and SLOs per user journey, with an error budget.
Always onError budgetsInfrastructure as codeRunbooks
03
What we measure
Three standard methods, used together.
| Method | Use it for | Signals |
|---|---|---|
| Four Golden Signals | User-facing systems | Latency · traffic · errors · saturation |
| RED | Microservices | Rate · errors · duration |
| USE | Infrastructure resources | Utilisation · saturation · errors |
04
Reference response times
From NGT's service-based model. Each contract sets its own; this is where the conversation starts.
| Severity | Example | Response | Resolution |
|---|---|---|---|
| P1 · Critical | Production down, no workaround | 30 minutes | 4 hours |
| P2 · High | Production degraded, workaround exists | 4 working hours | 1 working day |
| P3 · Medium | One non-critical function failing | 1 business day | 3 business days |
| P4 · Low | Minimal impact | 3 business days | 5 business days |
05
What you receive
SourcesNGT Service Offering v2.0 (Mar 2025)NGT Service Offering v3.2 (Jul 2026)NGT DevSecOps & Cloud Security Service Offering v0.4 (Jan 2025)NGT Cloud Operations Service Offering v0.2 (Jan 2025)NGT Cloud/DevOps/SRE Service Offering (Sep 2026)NGT DevOps-AI Service Offering (Oct 2026)