API Monitoring x SRE (Site Reliability Engineering)
summary
Apex runs a government API gateway and Stack Ops runs an elastic monitoring stack that together capture API traffic, platform events and infra metrics and surface the four golden signals. They rearchitect logs so ingestion drops from hours to reduced logging latency to seconds to under three minutes during peak, build event dashboards that link to deep‑dive panels, and create custom JWT error codes for self‑serve auth troubleshooting so 401/403 investigations no longer require log spelunking and mean time to resolution falls.
AI-written summary · about
chapters (13)
- 0:00API monitoring with SRE
- 1:10Apex API management platform
- 2:36Stack Ops in SRE
- 3:59Three-layer API monitoring
- 5:44SRE principles for API monitoring
- 6:31Dashboard design for interfaces
- 7:36Unified tooling for stakeholders
- 8:19Monitoring data speed and freshness
- 9:44Critical user journey modeling
- 11:53Dashboards for major events
- 13:18API authentication dashboards
- 16:59Engineering out monitoring toil
- 17:21Q&A
related talks
33mBad API Observability
14mWeb Apps, through the Lens of SRE (Site Reliability Engineering)
39mSRE or Devops - I am an Architect - Why Do I Care?
56mFull-stack observability and application monitoring with
38mApplication Performances Monitoring with Elastic APM and the ELK Stack
32mYet Another Monitoring Solution? Why APImon is Different
47mSecure and observe your APIs no matter where they run
24mAPI Security in DevSecOps: Built-In, Not Bolted On