![get-restaurants
global.CONTEXT
global.CONTEXT
x-correlation-id = …
x-correlation-xxx = …
get-index
headers[“User-Agent”]
headers[“Debug-Log-Enabled”]
headers[“User-Agent”]
headers[“Debug-Log-Enabled”]
headers[“x-correlation-id”]
capture
forward
function
event
log.info(…)](https://image.slidesharecdn.com/howtobuildobservabilityintoaserverlessapplication-190724185025/75/how-to-build-observability-into-a-serverless-application-120-2048.jpg?cb=1669874090)
How to build observability into a serverless application
•2 likes•669 views
Report
Share
Download to read offline
Serverless introduces a number of challenges to existing tools for observability, we need to adapt our practices to fit this new paradigm. In this talk, we will discuss how we can build observability into a serverless application. We will see how you can implement log aggregation, distributed tracing and correlation IDs through both synchronous as well as asynchronous events.
More Related Content
What's hot
What's hot(20)
Similar to How to build observability into a serverless application
Similar to How to build observability into a serverless application(20)
More from Yan Cui
More from Yan Cui(20)
Recently uploaded
Recently uploaded(20)
How to build observability into a serverless application
- 1. how to build Serverless OBSERVABILITY into a application
- 2. What do I mean by “observability”?
- 3. Monitoring watching out for known failure modes in the system, e.g. network I/O, CPU, memory usage, …
- 4. Observability being able to debug the system, and gain insights into the system’s behaviour
- 5. In control theory, observability is a measure of how well internal states of a system can be inferred from knowledge of its external outputs. https://en.wikipedia.org/wiki/Observability
- 6. In control theory, observability is a measure of how well internal states of a system can be inferred from knowledge of its external outputs. https://en.wikipedia.org/wiki/Observability including non- functional outputs
- 7. These are the four pillars of the Observability Engineering team’s charter: • Monitoring • Alerting/Visualization • Distributed systems tracing infrastructure • Log aggregation/analytics “ ” http://bit.ly/2DnjyuW- Observability Engineering at Twitter
- 8. microservices death stars circa 2015
- 9. microservices death stars circa 2015 mm… I wonder what’s going on here…
- 14. microservices death stars circa 2015 I got this!
- 19. Yan Cui http://theburningmonk.com @theburningmonk AWS user since 2009
- 20. Yan Cui http://theburningmonk.com @theburningmonk AWS user since 2009
- 21. new challenges
- 22. NO ACCESS to underlying OS
- 24. •nowhere to install agents/daemons new challenges
- 25. user request user request user request user request user request user request user request critical paths: minimise user-facing latency handler handler handler handler handler handler handler
- 26. user request user request user request user request user request user request user request critical paths: minimise user-facing latency StatsD handler handler handler handler handler handler handler rsyslog background processing: batched, asynchronous, low overhead
- 27. user request user request user request user request user request user request user request critical paths: minimise user-facing latency StatsD handler handler handler handler handler handler handler rsyslog background processing: batched, asynchronous, low overhead NO background processing except what platform provides
- 28. •no background processing •nowhere to install agents/daemons new challenges
- 29. EC2 concurrency used to be handled by your code
- 30. EC2 Lambda Lambda Lambda Lambda Lambda now, it’s handled by the AWS Lambda platform
- 31. EC2 logs & metrics used to be batched here
- 32. EC2 Lambda Lambda Lambda Lambda Lambda now, they are batched in each concurrent execution, at best…
- 35. HIGHER concurrency to log aggregation/telemetry system
- 36. •higher concurrency to telemetry system •nowhere to install agents/daemons •no background processing new challenges
- 38. Lambda data is batched between invocations
- 39. Lambda idle data is batched between invocations
- 40. Lambda idle garbage collectiondata is batched between invocations
- 41. Lambda idle garbage collectiondata is batched between invocations HIGH chance of data loss
- 42. •high chance of data loss (if batching) •nowhere to install agents/daemons •no background processing •higher concurrency to telemetry system new challenges
- 43. Lambda
- 46. my code send metrics internet internet press button something happens
- 49. ? functions are often chained together via asynchronous invocations
- 51. ? SNS Kinesis CloudWatch Events CloudWatch LogsIoT DynamoDB S3 SES tracing ASYNCHRONOUS invocations through so many different event sources is difficult
- 52. •asynchronous invocations •nowhere to install agents/daemons •no background processing •higher concurrency to telemetry system •high chance of data loss (if batching) new challenges
- 53. These are the four pillars of the Observability Engineering team’s charter: • Monitoring • Alerting/Visualization • Distributed systems tracing infrastructure • Log aggregation/analytics “ ” http://bit.ly/2DnjyuW- Observability Engineering at Twitter
- 55. LOGGING
- 57. 2016-07-12T12:24:37.571Z 994f18f9-482b-11e6-8668-53e4eab441ae GOT is off air, what do I do now?
- 58. 2016-07-12T12:24:37.571Z 994f18f9-482b-11e6-8668-53e4eab441ae GOT is off air, what do I do now? UTC Timestamp Request Id your log message
- 60. one log group per function one log stream for each concurrent invocation
- 61. logs are not easily searchable in CloudWatch Logs me
- 62. CloudWatch Logs
- 64. CloudWatch Logs is an async event source for Lambda
- 65. Concurrent Executions Time regional max concurrency functions that are delivering business value
- 66. Concurrent Executions Time regional max concurrency functions that are delivering business value ship logs
- 67. either set concurrency limit on the log shipping function (and potentially lose logs due to throttling) or…
- 69. 1 shard = 1 concurrent execution i.e. control the no. of concurrent executions with no. of shards
- 70. …
- 71. CloudWatch Logs
- 77. use structured logging with JSON
- 81. traditional loggers are too heavy for Lambda
- 88. Writing lots more data to CloudWatch Logs
- 89. CloudWatch Logs $0.50 per GB ingested $0.03 per GB archived per month
- 90. CloudWatch Logs $0.50 per GB ingested $0.03 per GB archived per month 1M invocation of a 128MB function = $0.000000208 * 1M + $0.20 = $0.408
- 91. DON’T leave debug logging ON in production
- 93. have to redeploy ALL the functions along the call path to collect all relevant debug logs
- 98. EC2 Lambda Lambda Lambda Lambda Lambda Concurrency is handled by the AWS Lambda platform
- 105. sampling decision has to be followed by an entire call chain
- 106. Initial Request ID User ID Session ID User-Agent Order ID …
- 107. EC2 Lambda Lambda Lambda Lambda Lambda Concurrency is handled by the AWS Lambda platform
- 108. store correlation IDs in global variable
- 111. use middleware to auto-capture incoming correlation IDs
- 112. extract correlation IDs from invocation event, and store them in the correlation-ids module reset
- 114. logger to always include captured correlation IDs
- 115. HTTP and AWS SDK clients to auto-forward correlation IDs on
- 119. { “body”: null, “resource”: “/restaurants”, “headers”: { “x-correlation-id”: “…” }, … } get-index get-restaurants
- 120. get-restaurants global.CONTEXT global.CONTEXT x-correlation-id = … x-correlation-xxx = … get-index headers[“User-Agent”] headers[“Debug-Log-Enabled”] headers[“User-Agent”] headers[“Debug-Log-Enabled”] headers[“x-correlation-id”] capture forward function event log.info(…)
- 124. MONITORING
- 126. •no background processing •nowhere to install agents/daemons new challenges
- 127. my code send metrics internet internet press button something happens
- 128. those extra 10-20ms for sending custom metrics would compound when you have microservices and multiple APIs are called within one slice of user event
- 129. Amazon found every 100ms of latency cost them 1% in sales. http://bit.ly/2EXPfbA
- 130. console.log(“hydrating yubls from db…”); console.log(“fetching user info from user-api”); console.log(“MONITORING|1489795335|27.4|latency|user-api-latency”); console.log(“MONITORING|1489795335|8|count|yubls-served”); timestamp metric value metric type metric namemetrics logs
- 131. CloudWatch Logs AWS Lambda ELK stack logs m etrics CloudWatch
- 135. API Gateway send custom metrics asynchronously
- 136. SNS KinesisS3API Gateway … send custom metrics asynchronously send custom metrics as part of function invocation
- 138. TRACING
- 139. X-Ray
- 143. don’t span over async invocations good for identifying dependencies of a function, but not good enough for tracing the entire call chain as user request/data flows through the system via async event sources.
- 144. don’t span over non-AWS services
- 148. instrument your code
- 149. make it easy to do the right thing