Essential API Metrics for Optimized APIOps Management
summary
Starts from the API spec as the single source of truth, adds an overlay carrying computed metrics, and treats the spec and mock definition as Kubernetes CRDs so a controller pulls telemetry, conformance and security scores and writes them back into the spec and the developer portal. Uses OpenTelemetry for latency/throughput, Spectral for spec rules, and third‑party scanners for OWASP/API risk. Shows an implementation that enriches mocks with measured latencies and surfaces per‑API scores in the portal.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 2:05API Metrics
- 10:01Benefits of API Metrics
- 11:52API Specific Spec
- 14:16Metrics Computed
- 19:04Conclusion
related talks
33mBad API Observability
24mObservability in the MLOps Lifecycle with Prometheus
11mKubernetes Observability
32mUnderstanding Observability in Kubernetes
53mOpenTelemetry Metrics: observability’s holy grail
41mMetrics Applied
25mBetter understand your APIs through traffic
56mFull-stack observability and application monitoring with