Use the Observability, Luke!
summary
Walks through concrete steps to instrument AWS Lambda: enable X‑Ray, Lambda Insights and API Gateway custom logs with a Trace ID; use AWS Lambda Powertools to add traces, metrics and structured JSON logs; measure cold starts via initDuration and link traces to API requests to see per-invocation impact; convert logs to metrics and ship to CloudWatch, Athena, OpenSearch or Grafana for alerts and automation. The delivered SAM template adds 67 lines to enable the stack.
AI-written summary · about
chapters (38)
- 0:00intro
- 0:21preface
- 0:51how good is your monitoring?
- 1:13about pawel
- 1:38less visibility
- 3:20why?
- 5:08iaas, paas, saas (faas)
- 5:55cultural shift
- 6:20structured logs
- 7:26standard log line - example
- 7:37structurized message - example
- 8:24log line - example
- 8:48it is a good start
- 9:31elements
- 10:19logs
- 11:26metrics
- 13:21traces
- 13:56context!
- 14:53context in observability
- 15:35meal - intelligent monitoring foundation
- 16:34tech stack - aws lambda
- 16:45issues?
- 18:06aws sam
- 18:21standard template
- 20:58improve! enable x-ray (lambda)
- 21:40the effect
- 23:13enable lambda insights
- 23:56enable api gateway logs
- 24:17custom log format
- 25:07logged request
- 25:36aws lambda powertools
- 26:19instrument with traces
- 26:38instrument with metrics
- 27:01instrument with logging
- 27:50implement it by yourself (qr code)
- 28:00where to go now?
- 28:30tools
- 29:47let's discuss, stay in touch!
related talks
43mObservability for Serverless
34mObservability in Serverless Application
24mObservability with AWS
41mLive Coding on Observability for Serverless
35mServerless observability with OpenTelemetry
30mUsing Open Source Observability with Lambda
24mObservability across serverless asynchronous managed services
01h 01mBetter reliability and uptime with analytics and observability