Using Telemetry in Cloud Native Applications
summary
A cloud‑native transaction banking platform implements event‑driven microservices across AWS “micro accounts” and promises end‑to‑end traceability by emitting milestone events correlated by reference IDs so ops can answer “where is my payment”; it uses Kafka event template for async messaging, centralizes metrics in DataDog + PagerDuty for alerts, routes logs: CloudWatch → S3 → Lambda sanitizer → Elasticsearch/Kibana (logs retained ~1 month, prod ~3), and experiments with Zipkin to X‑Ray tracing; readiness checks and GPI for SWIFT ensure SLAs on latency and volume.
AI-written summary · about
chapters (8)
- 0:00Introduction to project
- 3:59Deployment architecture evolution
- 8:58Telemetry requirements overview
- 14:13Types of telemetry data
- 16:01Business event monitoring
- 21:37Engineering telemetry setup
- 27:43Monitoring workflow for engineers
- 30:37Q&A and closing
related talks
37mThrough the looking glass: Effective observability for cloud native applications
01h 02mAdding Observability to Distributed Systems
55mCloud-Native Observability with OpenTelemetry
49mAdding OpenTelemetry to Production Apps Lessons Learned
16mBuilding Observability into Cloud-Native Applications
27mEnd-to-end visibility in the cloud w/OpenTelemetry
13mNext-Gen Observability: reduce MTTR
01h 01mBetter reliability and uptime with analytics and observability